What is Telegraph
Autonomous agents need intelligence they can trust and pay for programmatically — without API key management, without centralized gatekeepers, and without a human in the loop. Telegraph is the protocol that makes this possible.
At its core, Telegraph is a marketplace for verifiable AI inference. Agents pay in USDC for a question answered. Miners from across the world compete to supply the best answer. A network of validators grades those answers using shared scoring modules, signs the result with an aggregate signature, and delivers a finalized signal. Every USDC paid to get that answer flows back through an open market to buy the protocol's native token, MACHINA, meaning every real use of the network creates direct, permanent demand for the token that secures it.
The Three Forces
Agents are anything that needs intelligence — a human at a terminal, an autonomous trading bot, a smart contract, or another AI system. They express demand by paying USDC.
Miners are AI compute providers who expose their models and APIs through a standardized interface. They compete on quality, earn when they're used, and get paid in MACHINA purchased with the USDC agents spend.
Validators are the neutral guarantors. They run the protocol's scoring engine, grade miner responses against truth sources, sign the result with a quorum signature, and publish finalized results on-chain. They earn MACHINA from protocol emissions, not from payments, which keeps their incentives cleanly separate from miners.
How a Signal Gets Delivered
- An agent sends a request (plain language, or an intent with typed
params) and pays the signal price in USDC via x402 or from escrow. - The protocol routes the request to a miner based on its leaderboard score for that intent.
- The miner returns a response, which the node reads into the intent's own answer shape, the same whichever miner answered.
- Validators grade miners each epoch with a shared WASM scoring module and sign the epoch's state.
- The signal is delivered, either directly to the agent, or as a callback to a smart contract.
- The USDC paid gets dripped into Uniswap to purchase MACHINA, which is sent to the miner.
WebSocket: A Continuous Signal Stream
The flow above is on-demand: you ask a question, you get an answer. Telegraph also runs a background Daemon that autonomously scrapes real-world data, generates its own questions, and produces signals on a fixed cycle whether or not any agent is asking.
You can subscribe to this feed over WebSocket instead of polling for it: authenticate with your wallet, pick the Intents you care about, and each matching signal is pushed to you as the Daemon produces it. Delivery is settled against your on-chain USDC escrow per signal, rather than paid per call like the Engine. See WebSocket Signal Subscriptions.
Where to Go Next
Reading These Docs With an AI
Every page is also available as plain Markdown, which AI assistants read more reliably than a web page:
| What you want | Use |
|---|---|
| Give an AI the whole documentation at once | /llms-full.txt: every page in one file. Paste the link, or download the file and attach it. |
| Let an AI pick the pages it needs | /llms.txt: a list of every page with a one-line summary and a link to its Markdown |
| Share one page | Add .md to the page's address (for example /docs/using/intents.md), click View as Markdown, or click Copy for LLM at the top of the page |
Links inside the Markdown point to the full address of the other pages, so a copied page still works when your AI reads it on its own.