Telegraph Wants to Be the Visa of Machine Intelligence

The AI industry has built extraordinary intelligence, but no infrastructure for machines to safely use it. Every lab has optimized for humans. Chat windows. Dashboards. Developer APIs. Nobody had built the layer for the moment when an AI agent needs to purchase trusted intelligence and use that answer to make a real decision, until now.

Telegraph is a messaging protocol built on Base that transforms raw AI outputs from any open or closed-source model, into verified, tradable answers that machines can use to make decisions and execute tasks autonomously.

The interesting part is that Telegraph does not need to beat the AI labs at building models. Its bet is that the market will need a neutral layer above them, one that can route, verify, and commercialize intelligence from many providers. Every frontier lab, every open-source project, every new model that gets funded becomes a better supplier on the network. The billions being poured into AI infrastructure are, in effect, subsidising the protocol's supply side at no cost.

But for machines to earn, trade, and act on behalf of people, intelligence cannot just be generated. It has to be verified. The moment an AI agent starts buying answers from another piece of software and acting on them without a person reviewing the result first, trust becomes the central problem.

How does anyone know whether the answer is correct? This is what Telegraph is working to resolve.

AI models hallucinate. Industry reports estimate the cost to global business at tens of billions of dollars annually, and while the headline numbers are commercial estimates rather than peer-reviewed research, the underlying problem is well documented. Stanford's legal AI study found purpose-built tools hallucinated on 17 to 34 percent of queries. Columbia Journalism Review found AI search tools gave incorrect answers on more than 60 percent of citation checks. A human reading a wrong answer loses time. An agent acting on one can lose money in milliseconds.

Telegraph's proposed solution has four pillars:

Miners: The people running an AI model and offering to answer specific kinds of questions, e.g. a Bittensor subnet operator, a developer hosting an open-source LLM, a research lab with a proprietary model. They register what they can answer and plug in via a YAML file. When an agent or application requests a signal, they provide the inference. They are paid exclusively from real usage. Every time an answer is bought, the agent's USDC purchases Machina, Telegraph's token, from the open market and sends it to them. The better their model, the more agent traffic and tokens they get.

Agents: Agents are the software clients that need those answers. They are built by developers, run on behalf of users, and pay in USDC for each request.

Validators: A network of 64 institutional node operators that score every answer against verified ground truth using cryptographic proofs, reaching consensus before payment is released. Telegraph itself does not produce intelligence. It is the layer in between, verifying answers and routing payments across the entire inference ecosystem.

Script Authors: They write the scoring logic that determines whose model is the best. Validators run these evaluation scripts to grade miner responses, and the script authors themselves earn the 20% emission pool proportionally to how often their logic is relied upon. The more validators rely on their script, the larger their portion. They never sell the script but they are compensated directly by the protocol for making the network accurate.

What makes Telegraph more than a payment layer is the verification machinery around the answer itself. The protocol does not simply route a request to a model and hope for the best. It scores miner responses through validators, canonical scripts, stake weighted median consensus, and cryptographic ground truth checks before routing future demand.

The design choice that distinguishes Telegraph from a marketplace like Bittensor, where developers pick specific subnets to query, is that agents on Telegraph do not pick models at all. They declare what they want answered, and the protocol routes the request to whichever miner is currently scoring highest for that category of question. The architectural bet is that agents making decisions on behalf of users at machine speed will not have time to evaluate AI vendors, and that the people building those agents will want a layer that does the evaluation for them.

"Intelligence from open and closed-source models is growing exponentially, but it has no unified commercial layer. Agents need a source of truth faster and more reliable than human consensus, yet today they're forced to rely on black-box models. Developers spend hours manually testing which model performs best for their specific use case. Trillions of machines are waking up, and every one of them will need verified answers," says Ahmed Ali, CTO and Co-Founder of Telegraph. "We replace hand-testing with automated, intent-based routing. Developers no longer pick models. They declare their intent, and our engine routes each request to the highest-scoring providers on a live leaderboard."

The Solana Foundation reported in March that the network has processed roughly 15 million on-chain payments initiated by AI agents, primarily for machine-to-machine commerce. Coinbase's x402 payments protocol, an HTTP-based standard that lets software agents pay on behalf of themselves across multiple networks, saw a roughly 10,000 percent surge in transaction volume over a recent period, hitting around 500,000 payments in a single week. In March, Banco Santander and Mastercard completed Europe's first live end-to-end payment executed by an AI agent inside a regulated banking environment, using Mastercard's Agent Pay framework.

"The goal is to create a coordination layer where miners are rewarded for delivering the verified responses machines need to make decisions. Agents are already beginning to spend money, but the market for trusted machine intelligence is very early. We're opening the door to competition, rewarding the evangelists who want to shape this industry," Mark Basa CEO & Co-founder of Telegraph adds.

For Telegraph, the opportunity is not simply that agents are beginning to pay. It is what happens after they pay. When an agent pays for an answer, the USDC does not flow directly to the miner. Instead, the protocol utilizes a pipelined settlement engine: it tracks usage off-chain in raw USDC, then executes a single, batched transaction at the epoch boundary to swap the collected funds for Machina, Telegraph's native token, on the open market. The miner receives Machina, which was just purchased with real dollars on the open market. Every paid request is, mechanically, an open-market buy.

This is a genuinely novel design choice for a 21-million-supply token, taking a different approach to how value flows between users, miners, and the broader market.

Bittensor is the closest reference point. Launched in 2021, it now spans more than 128 active subnets covering inference, training, compute routing, and deepfake detection, and has built a real ecosystem with a market cap that has touched $5 billion. It is, by some distance, the most successful experiment in decentralized AI infrastructure to date, and the protocol that has done the most to prove this category is real.

Producing intelligence is not cheap. Training models, running inference at scale, maintaining specialized infrastructure, all of it carries a real cost. Bittensor solves that problem by subsidizing miner activity through token emissions, which is a sensible choice for a protocol whose core function is to produce intelligence in the first place. Someone has to pay for that work to exist, and emissions are how Bittensor pays for it. Telegraph's situation is structurally different. The protocol does not produce intelligence. It routes it. That means Telegraph cannot reasonably pay miner emissions to subsidize innovation. The economic logic only holds if agents are actually paying for answers, which is why the protocol is designed around USDC demand rather than emission rewards. Machines have to pay first, or at minimum demonstrate real routing demand, before any token flows to a miner.

The team behind Telegraph sees Bittensor as a foundation to build on rather than a network to compete with. The intelligence being produced across Bittensor's subnets is some of the most interesting work happening in open-source AI right now, and Telegraph's design treats it as a first-class supply source. A subnet that has invested years in producing exceptional inference can register on Telegraph and immediately expose that intelligence to a new stream of agent demand, monetized in USDC, without changing anything about how the subnet itself operates. The Telegraph team has cited Bitcoin and Bittensor as the two foundational breakthroughs they draw their architecture from: Bitcoin for securing a ledger through decentralized competition, and Bittensor for creating an open network for decentralized AI production. If both networks scale together, both benefit.

The verification machinery behind it is what makes the rest of the system novel. The network's evaluation layer operates through an automated, performance-based promotion cycle. Independent developers contribute WebAssembly grading logic, which is continuously audited against the network's stake-weighted consensus. Scripts that maintain accuracy within established consensus bounds are automatically promoted, while those that produce volatility or drift are discarded by the mesh. This architecture creates an evolutionary scoring system that autonomously rejects performance anomalies and enforces high-fidelity intelligence as the network standard.

A second piece of the infrastructure handles live miner integration. To answer machine requests, validators must continuously execute real-time queries against third-party models. Telegraph handles this via a distributed threshold encryption scheme where encrypted credentials are rotated across hardware enclaves whenever the validator set changes. Building a permissionless protocol that matches the raw speed of a centralized enterprise API, while securing the execution keys to a global model ecosystem, is one of the most formidable infrastructure challenges in the space today.

There are still big questions ahead. If verified intelligence for AI agents becomes a major category, will it be powered by a new protocol and token, or will the same function eventually be built into companies like Coinbase, Stripe, Visa, or Mastercard?

Basa believes the intelligence layer should be open and permissionless, not controlled by one company, and that the major AI labs are unlikely to build trustless verification themselves, because their current business models do not depend on it. If he's right, the AI labs will also have a choice to make: plug into networks like Telegraph as suppliers, or build their own commercial intelligence layers.

That is what makes the next phase so interesting. Telegraph is not just launching another AI protocol. It is testing whether trusted machine intelligence can become its own open market.

The macro context for the bet they are making is moving quickly. Agent initiated payments are still early, but they are no longer theoretical. Telegraph is building for the moment when autonomous systems need not just the ability to pay, but a reliable way to decide what information is worth paying for.