All customers of any blockchain infrastructure have been real individuals until recently. People registered themselves, pasted their API key into a configuration file, and began making requests. Quicknode now sells to a second kind of customer: one with a wallet and a job to do, but no inbox to confirm.
On May 6, the company described the flow in a blog post: an AI agent sends a single request, pays from its wallet, and gets back a full account with a platform API key. From there, it can spin up endpoints on its own. In Quicknode’s own words, “no dashboard, no human handoff.”
Why agents, and why now
The timing is far from accidental, since agents are already paying for things onchain, and much of what they buy bears a close resemblance to what Quicknode sells. According to a Chainalysis report published October 2026, agents have made more than 138 million payments over Coinbase’s x402 protocol on Base. Specifically, more than 87% of these payments were worth less than 10 cents.
In the same vein, Allium’s September report noted that there were 29 million agentic x402 transfers in August alone, averaging about 6 cents each. Notably, the report found that 89% of agentic transfers since October 2025 went toward infrastructure, analytics, and data queries.
However, the these numbers come with a caveat. According to a report by Startup Fortune, the raw count of agentic transfers includes a lot of noise, as Visa and Artemis analysis put the actual x402 volume at close to $19 million after excluding wash trading and self-dealing. While this amount is still small, it shows a clear pattern. When software has a wallet, the first things it tends to buy are compute, data and access – and RPC endpoints sit right in that category.
How x402 and MPP let AI agents pay
Two protocols make this work, and Quicknode supports both with stablecoin settlement. x402 is an open standard from Coinbase. MPP, the Machine Payments Protocol, was authored by Tempo Labs and Stripe, launched alongside Tempo’s mainnet on March 18, and is now an IETF Internet-Draft. Both revive HTTP 402, the long-unused “payment required” status code.
The mechanisms for both protocols are pretty straightforward. An agent requests data, the server replies with a 402 and a price, the agent signs a stablecoin payment, and the request goes through. Where the protocols differ is in how they handle volume. x402 offers a simple pay-per-request access, plus a credit model for heavier use. Meanwhile, MPP adds a “session” mode, in which an agent deposits funds into an escrow and signs off-chain vouchers that are settled onchain in batches, Quicknode explains.
On Quicknode, a single paid request costs $0.001 under either protocol, while credit drawdown on x402 and MPP sessions bring that down to about $10 per million requests, according to its x402 and MPP documentation. Further, payment and data are decoupled, meaning that an agent can pay in USDC on Base and query Ethereum or Solana. Each wallet gets 1 million API credits a month for free across both protocols, enough for developers to test what their agents need before spending anything.
One customer, ten agents
Quicknode’s showcase is Supermission, which runs ten agents around the clock. DELPHI executes DeFi trades on Base. ORACLE surfaces prediction-market intelligence. HYPERION manages perpetuals, SECURO audits smart contracts, and six sub-agents handle token due diligence and wallet analysis in the background.
The agents started on free public endpoints, which held up in development but hit rate limits and timeouts under real traffic, stalling multi-step DeFi operations halfway through. When money is in motion, that’s a nasty way to fail. After moving to Quicknode, daily requests rose from about 500 to 17,400 across Base, Polygon, Ethereum, and Arbitrum, at an average latency of 50 to 150 milliseconds according to the case study. The agents pay per request in USDC over x402, and each has an onchain identity registered through ERC-8004. According to Supermission’s team, nobody there has had to handle an API key.
The aforementioned case study is Quicknode’s own, and Supermission is a small team. That said, it shows the full loop working in production. Agents that find infrastructure, pay for it and transact with each other without a human holding the keys.
The tools around it
Payments are one piece of a bigger toolkit. Since June 1, Quicknode has been an official connector in Anthropic’s MCP directory, so a person or an agent can manage infrastructure across 80+ chains in plain language. It also offers a CLI, an Admin API, and an SDK. Blockchain Skills teach coding agents the Quicknode API, and an AI Cookbook collects tested prompts for building onchain tools. For anyone working on agent identity, there’s an ERC-8004 explorer.
The bigger buyers
The agent business sits atop a large existing one. For scale, Quicknode processed 5 trillion requests in 2025, about 14 billion a day, according to its year-end review. Quicknode’s Q1 roundup lists MPP payments going live on Tempo mainnet, renewed SOC 1 and SOC 2 Type 2 attestations, and ISO 27001 certification, the paperwork enterprise buyers ask for first.
The second source of demand is less futuristic and comes with a hard deadline. Google Cloud is shutting down Blockchain Node Engine and Blockchain RPC on December 15, 2026. It stopped creating new nodes on June 15, and has named Quicknode as its recommended RPC provider. Customers can buy through Google Cloud Marketplace and use Google Cloud incentives, or sign up with Quicknode directly.
For teams running production workloads, that date is fixed. The agent builders have no deadline, only a preference for infrastructure that doesn’t ask them to fill in a form.
Will AI agents start choosing their own infrastructure?
Early adopters like Supermission are small. Two things will show whether this goes further: whether x402 and MPP volume reaches teams that don’t build agents for a living, and whether agents end up choosing their own providers the way developers once did. The Google Cloud migration will answer a different question by mid-December: how many enterprises decide to stay on a managed provider instead of running nodes themselves.
