Mentioned in This Article
1. What is the x402 protocol?
The x402 protocol is an open payment standard, built on the web's own HTTP framework, that lets AI agents and applications pay for online services with stablecoins. Coinbase introduced it in May 2025, and as of November 4, 2026 it counts dozens of major companies, including Visa, Mastercard and Google, among the members of a foundation that governs it. Payments are mostly made in USDC on the Base network.
x402 is neither a blockchain nor a coin. It is a set of rules describing message formats, headers and the order of requests and responses, so that a server can ask for payment and a client can supply it within an ordinary web exchange. Coinbase launched it with partners that included AWS, Anthropic, Circle and NEAR, with the aim of letting interfaces to data and software be sold in tiny increments without sign-ups.
The name comes from the number 402, an HTTP status code reserved in early web specifications under the label "Payment Required". The code was set aside for future use and then sat idle for roughly three decades. Traditional payment systems were too slow, too costly and too dependent on accounts and card details to make it practical, and x402 is described as the first major effort to put it to work.
Stablecoins are the natural fit for this design because their value is pegged to a currency, which spares buyers and sellers from price swings between the moment of request and the moment of settlement. USDC, issued by Circle, is a dollar-backed example, and Base is an Ethereum layer-2 network, meaning a secondary chain that processes transactions more cheaply while relying on Ethereum for security.
2. Why do AI agents need a payment standard?
The web was not designed with payments in mind. Buying something online usually means creating an account, entering card details and passing through intermediaries who can reverse a charge later. That process suits a person buying a pair of shoes. It is ill-suited to software that wants to pay a fraction of a cent for a single piece of data.
AI agents increasingly browse sites, call application programming interfaces and purchase services on behalf of people. They cannot fill in checkout forms or manage subscriptions the way a human customer does. Cloudflare says more than half of internet traffic is now non-human, and it reports roughly a billion HTTP 402 responses a day across its network, a sign of how often automated clients are met with demands for payment.
x402 is an attempt to give the internet a native payment method for that traffic. Instead of an account relationship between buyer and seller, the buyer simply presents a signed authorization at the moment of the request, and the seller delivers the resource once the payment clears.
Microtransactions have been proposed before, and most earlier attempts failed because the cost of processing each payment exceeded its value. Cheap settlement on layer-2 networks changes that arithmetic, and the presence of stablecoins removes the exchange-rate problem that made earlier crypto micropayments awkward.
3. How does x402 work?
An x402 payment takes four steps. First, an agent or application requests a resource, such as an API call, a dataset or an article. Second, the server answers with the 402 status code and machine-readable terms that specify the price, the tokens it accepts and the wallet that should receive payment. Third, the client signs a payment authorization and sends the request again, with the signature included in a header. Fourth, the server verifies the authorization, settles the payment onchain and delivers the resource.
Most of the onchain work is handled by a facilitator, a service that verifies and submits transactions, so sellers do not have to run their own crypto infrastructure. On Ethereum-compatible chains, the protocol relies on a standard known as EIP-3009, which allows a signed permission to authorize a token transfer. This means the buyer does not need to hold ETH to cover transaction fees.
The effect is a flow that resembles a normal web request with an extra round trip. A developer who wants to charge for access adds the payment terms to the server, and a client that understands the standard handles the rest automatically.
Because the buyer signs an authorization instead of creating an account, there is no stored login to steal and no password to manage. The signed message is tied to a specific amount and recipient, so a seller cannot take more than the buyer approved. Developers still have to decide how much an agent may spend, and those limits are usually set in the wallet that funds it.
4. What makes x402 different from card payments?
The central pitch is very small machine-to-machine payments. Settlement on Base takes seconds and costs well under a cent, so charging a fraction of a cent for an API call becomes viable. Card networks, with their fixed fees and chargeback risk, make such amounts uneconomic. No sign-up, API key or subscription is required, which removes much of the friction for software that may only need a resource once.
The protocol has evolved since launch. Version 2 arrived in December 2025 and added wallet-based identity, so agents do not have to pay again on every call, along with automatic service discovery and support for more chains. In May 2026 the protocol gained batch settlement, which lets agents give sellers signed vouchers that are settled in bulk instead of one at a time.
The protocol is not tied to a single network. In addition to Base, it supports Solana, Polygon, Arbitrum and other chains, and it can also accommodate traditional card payments, which makes it easier for sellers to accept whatever method their buyers hold.
For sellers, the appeal is equally practical. A small publisher or data provider can charge per request without negotiating a contract, building a billing system or waiting for monthly invoices to be paid. For buyers, an agent can discover a service, see its price and pay within the same request, with no human required to approve each purchase.
5. How much is x402 actually used?
According to figures from Fireblocks, x402 had processed more than 196 million transactions across 12 chains as of November 1, 2026, settling over $42 million in total. Coinbase says that more than 97% of onchain agent transactions in the second quarter of 2026 used the standard.
Those totals come with an important caveat. More than half of all transactions over the protocol's lifetime came from a two-month burst in late 2025, when traders ran automated scripts that minted and sold a token called PING, issued through x402. Activity has fallen since. In October 2026 the network recorded about 5.1 million transactions worth roughly $274,000.
The gap between the headline totals and the recent monthly figures illustrates a question hanging over the whole sector: whether agent payments will grow into steady commercial activity or remain dominated by speculative bursts. The data so far shows an enormous number of very small payments, which is consistent with the design goal but says little about real purchases.
Measuring adoption in a young market is difficult. Transaction counts reward systems that generate many tiny transfers, while dollar volume rewards a few large ones, and neither captures whether the payments reflect genuine demand for a service. Analysts will likely look at the number of distinct buyers and sellers, repeat usage and the share of payments tied to real goods as better indicators.
6. Who is working with x402?
Several well-known companies have built on the standard. Cloudflare co-developed the foundation with Coinbase and Stripe, supports x402 in its Agents software kit and offers an edge-based gateway for monetizing content. Stripe, also a co-developer and premier member, maps x402 payments to its PaymentIntents product so that merchants can use their familiar reporting and payout tools.
Agentic.Market, launched by Coinbase in April 2026, is a public marketplace for x402 services with live pricing and volume data. CoinGecko offers market data endpoints that agents pay for per call. AWS has built buyer-side controls into its AgentCore service for managing agent payments, budgets and permissions. Google has created an agent-to-agent extension for x402 as part of its Agent Payments Protocol, developed with Coinbase, the Ethereum Foundation and MetaMask, for crypto settlement between agents.
The breadth of this list matters because a payment standard is only useful when both buyers and sellers support it. Having cloud providers, payment processors and data vendors involved makes it easier for a developer to find counterparties.
Government and regulatory attitudes toward stablecoin payments will also shape how fast businesses adopt the model. Companies that must meet compliance obligations will want clear answers about who is responsible for screening payments, and facilitators sit at the center of that question because they handle verification and settlement.
7. Who governs x402, and does it have a token?
On April 2, 2026, the Linux Foundation announced the x402 Foundation, to which Coinbase contributed the protocol. Microsoft, Google, Visa and Mastercard voiced early support. The foundation became fully operational on July 14, 2026, and governs the protocol under vendor-neutral terms. It had 40 members at that point and has since grown to 57, with members that include Visa, Mastercard, American Express, PayPal, Google, Shopify, Circle, Stripe and AWS. Michael Hursta became executive director on October 1, 2026.
The protocol has no official token. It is a standard rather than a cryptocurrency, and payments use existing stablecoins, mostly USDC. Speculative tokens labeled x402 exist on various chains, but Coinbase and the foundation do not issue or back them. Readers should be cautious about any asset claiming to be the official x402 coin.
To use the protocol, a buyer needs a wallet holding a supported stablecoin on a supported network, usually USDC on Base. USDC is available through exchanges such as Coinbase, Kraken and Binance, and Coinbase lets users send it directly to Base. Developers can fund agents and set spending limits with wallets from the Coinbase Developer Platform or Circle.
8. What are the rival standards, and what comes next?
x402 is not the only proposal. The Agentic Commerce Protocol, an open standard from Stripe and OpenAI, and Visa's Trusted Agent Protocol address similar problems, and both Stripe and Visa are also premier members of the x402 Foundation. Stripe additionally co-developed the Machine Payments Protocol with the payments-focused blockchain Tempo. Like x402, it uses the HTTP 402 code, but it adds session-based billing so that agents can pay as they go instead of settling each request onchain.
The next test is whether transaction counts turn into steady commerce. If agents begin paying regularly for data, computing and content, a long-dormant web status code could end up carrying a significant share of AI-related payments. If activity stays concentrated in speculative bursts, the standard will remain a promising piece of infrastructure waiting for demand.