Coinbase’s x402 Passes $42 Million as AI Agents Do 97% of Agent Payments

A payment idea built on a long-dormant piece of web infrastructure is now handling real money at growing scale. Coinbase’s x402 open payment standard, which revives the HTTP 402 Payment Required status code for machine-to-machine payments, has passed 42 million dollars in settled value, according to reporting published on November 4. The milestone is notable not only for the amount, but for who is doing the paying. Increasingly, the payers are not people clicking checkout buttons. They are software agents, application programming interfaces and autonomous programs paying directly for digital services, often in fractions of a second and without human intervention in each transaction.

The story begins with an unused corner of the web. When the HTTP standard was designed, code 402 was reserved for future payment use, but it was never widely implemented. Coinbase’s approach, launched in May 2025, gives that dormant code a concrete job. When a service requires payment, it can return a 402 response telling the requester how much to pay, in what asset, and where to send it. A compatible wallet or agent can then submit the payment and retry the request, completing the transaction without a separate signup, card form or manual approval step for every call. That design suits a world in which an AI assistant needing a data feed, an image model, a search result or a compute job may need to pay a tiny amount for each use, where human approval of every micro-payment would defeat the purpose.

Governance has also moved toward a more neutral footing. The x402 Foundation, launched by the Linux Foundation in April 2026, oversees vendor-neutral governance of the standard, according to the November 4 Basis Desk report. That step matters because a payment standard controlled entirely by one company would face natural resistance from competitors and partners who might otherwise adopt it. A foundation structure, modelled on how other open technology standards are stewarded, is intended to give participants confidence that the rules will not change arbitrarily to favour a single vendor. Whether that model succeeds in practice will depend on who participates, how decisions are made, and whether rival firms feel they have a genuine voice.

How the x402 payment standard works in practice

In practical terms, x402 turns a failed request into a payment instruction. Imagine an AI agent asking an API for premium weather data, a financial feed or a specialised model output. If that resource requires payment, the server responds with a 402 message containing the price and payment details. The agent’s wallet software reads that message, checks it against its spending rules, sends the required stablecoin payment, and then resubmits the original request with proof of payment. The server verifies the payment and returns the data. The whole loop can happen programmatically, without the agent’s human owner opening a browser or entering card details. Facilitators help verify payments and handle interaction with the blockchain.

It is important to be precise about what x402 is and is not. According to the reporting, x402 is not a blockchain and not a cryptocurrency, and it has no official token. That distinction matters for readers who might otherwise assume growth in x402 usage implies a new token to buy or speculate on. There is no x402 token in the model described. The value transferred is the stablecoin payment itself, and the innovation is the protocol for requesting, verifying and settling that payment automatically. Anyone claiming to sell an official x402 token would be misrepresenting the standard as described in the reporting.

What the November 2026 numbers show

By November 2026, the reported scale of x402 activity was substantial. The standard had processed more than 196 million transactions across 12 blockchains, with more than 42 million dollars settled, according to the Basis Desk report. Those two numbers together tell an important story about transaction size. Dividing the settled value by the transaction count implies a very small average payment, consistent with the micro-payment use case the standard was designed for. Many agent transactions may involve fractions of a dollar for a single API call, a single query or a single unit of compute, rather than large purchases.

A second striking figure concerns the share of agent activity. Data from Fireblocks, citing agenteconomy.to, indicated that more than 97 percent of onchain agent transactions in the second quarter of 2026 involved x402. If taken at face value, that share would suggest x402 has become the dominant rail for agent-to-service payments onchain, at least within the measured universe. Launch partners named in the November 4 report included Circle, Anthropic, AWS and NEAR, alongside Coinbase itself. That partner list spans stablecoin issuance, AI model development, cloud infrastructure and blockchain ecosystems, which helps explain how the standard could reach agents operating in very different environments.

These figures should be read with a caveat that was covered on this site yesterday and that remains relevant here. Fireblocks has warned that data on agent transactions, including the 196 million transaction figure, is noisy. Measurement of autonomous agent activity is still new, definitions vary, and automated traffic can be difficult to distinguish from genuine economic activity. This article therefore reports the headline numbers as reported, while flagging that the underlying agent-transaction data should be treated as directional rather than precise. That caveat does not erase the milestone, but it shapes interpretation: x402 has moved from experiment to functioning infrastructure for a growing niche, with measurement methods still catching up.

Why AI agents change the payments problem

Traditional online payments were designed for humans. A person sees a price, enters payment details, confirms, and receives a good or service. That flow breaks down when the buyer is software operating at machine speed. An agent might need to make hundreds or thousands of small purchases in a day, each for a different service, each worth only a few cents. Requiring human confirmation for each one would be unworkable. Requiring a separate account and subscription for each service would be equally impractical. The payments problem for agents is therefore not just about moving money. It is about discovery, pricing, authorisation and settlement happening automatically, under rules set in advance by the human owner.

Requirements, limits and open questions

For users and agents to participate, certain requirements must be met. According to the reporting, users and agents need supported stablecoins, usually USDC, held in a compatible wallet on supported networks such as Base. That requirement is straightforward for crypto-native developers, but it is still a barrier for mainstream users who do not hold stablecoins or use blockchain wallets. An agent operating on behalf of a business may need treasury processes for funding wallets, monitoring balances, setting spending caps and reconciling micro-payments across many services. Those operational details are less glamorous than the protocol itself, but they will determine whether adoption spreads beyond early adopters.

Spending controls are a central open question. An agent that can pay automatically is powerful, but also risky if its permissions are too broad, its price checks are flawed, or it is tricked into paying a malicious service. Guardrails such as per-transaction limits, daily budgets, allowlists of approved services, and requirements for human approval above a threshold are not optional extras. They are the conditions under which automatic payments become acceptable to businesses and consumers. The x402 standard provides the payment mechanism, but responsibility for setting and enforcing those guardrails sits with wallet providers, agent developers and the humans who deploy agents.

What this means for agent commerce

Despite those open questions, the direction of travel is clear. Software agents are becoming economic actors, not just tools that answer questions. They search, compare, book, analyse and now, through standards like x402, pay. The 42 million dollar milestone, even with noisy transaction counts, indicates this shift is no longer purely theoretical. Real services are being bought by real agents, in real stablecoin amounts, through a standard that did not exist in this form before May 2025. That pace of movement, from launch to tens of millions settled in about eighteen months, is rapid by payments industry standards.

FAQ

What is the x402 payment standard?

The x402 payment standard is an open protocol from Coinbase that revives the HTTP 402 Payment Required code to let software, APIs and autonomous agents pay directly for digital services. When a service requires payment, it returns a 402 response with price and payment details, and a compatible wallet can settle the payment and retry the request automatically. It is a payment protocol, not a blockchain or a cryptocurrency.

How much has been settled through x402?

According to reporting published on November 4, more than 42 million dollars had been settled through x402 by November 2026, across more than 196 million transactions on 12 blockchains. The small average value implied by those figures fits the micro-payment use case of paying per API call or per unit of digital service, rather than large one-off purchases.

What does the 97 percent figure mean?

Fireblocks data citing agenteconomy.to indicated that more than 97 percent of onchain agent transactions in the second quarter of 2026 involved x402. That figure suggests a dominant share within the measured universe, but it should be treated as directional rather than exact, because agent-transaction data has been described as noisy and measurement methods are still maturing.

Does x402 have its own token?

No. According to the reporting, x402 is not a blockchain or a cryptocurrency and has no official token. Payments are made in supported stablecoins, usually USDC, on supported networks such as Base. Any claim to sell an official x402 token misrepresents the standard as described.

What do users or agents need to use x402?

Users and agents need supported stablecoins, usually USDC, in a compatible wallet on a supported network such as Base. They also need spending rules set in advance, such as limits and approved services, because agents may make many small payments automatically. Facilitators help handle blockchain interaction, but funding, budgeting and oversight remain the responsibility of the wallet owner and agent developer.

Source: CoinTurk/Basis Desk

Related reading on MM Crypto Analysis Web

• Agent Payments Hit 196 Million Transactions but the Data Is Noisy, Fireblocks Warns
• Virtune Launches AI Crypto Index ETP Tracking 13 Agent-Economy Assets
• Crypto Token Unlocks to Watch in the First Week of November 2026

More in AI Crypto on MM Crypto Analysis Web.