x402 is an open payment standard, started by Coinbase, that uses HTTP's long-dormant 402 Payment Required status code so an agent can pay for an API call, a dataset or an article without an account, a card or a checkout form. Decrypt's explainer is blunt about what it is: not a blockchain, not a coin, just rules for message formats, headers and request-response flows. That matters for builders, because it means the payment step lives inside the same HTTP call your agent is already making.
The take: the protocol is simple and the backing is broad. The open question is whether the traffic is real commerce yet. Both halves are worth knowing before you wire it into a stack.
The four steps
Per Decrypt's walkthrough, one paid request looks like this:
1. Request. The agent asks a server for something: an API call, a dataset, a page. 2. 402 response. The server replies "Payment Required" with machine-readable terms: the price, the accepted tokens and the wallet address to pay. 3. Payment. The client signs a payment authorization with its wallet and resends the request with the signature in a header. 4. Delivery. The server checks the payment, settles it onchain and returns the content.
In practice a facilitator usually handles verification and settlement, so the seller does not need its own crypto infrastructure. On EVM chains the payment uses EIP-3009, which lets the buyer authorize a transfer by signing instead of sending a transaction. The buyer does not need ETH for gas, only the stablecoin.
Settlement is mostly USDC on Base. Decrypt says Base settles in seconds for well under a cent, which is what makes fractional-cent, per-call pricing workable. Solana, Polygon, Arbitrum and others are supported, along with card payments.
How it got here
The timeline in the article, all as reported by Decrypt:
- ▸May 2025: Coinbase launches x402 with partners including AWS, Anthropic, Circle and NEAR.
- ▸December 2025: V2 adds wallet-based identity, so agents don't pay again on every call, plus automatic service discovery and more chains.
- ▸April 2, 2026: The Linux Foundation announces the x402 Foundation, with Coinbase contributing the protocol. Microsoft, Google, Visa and Mastercard express initial support.
- ▸May 2026: V2 gains batch settlement, where agents hand sellers signed vouchers that settle in bulk.
- ▸July 14, 2026: The foundation becomes fully operational under vendor-neutral governance. It had 40 members at launch and reportedly 57 since, including Visa, Mastercard, American Express, PayPal, Google, Shopify, Circle, Stripe and AWS.
Cloudflare and Stripe are named as co-developers of the foundation with Coinbase. Stripe turns x402 payments into PaymentIntents so merchants get familiar reporting. AWS AgentCore handles buyer-side budgets and permissions. CoinGecko sells market-data calls that agents pay for per call. Membership is not the same as shipped integration, so check each one before you assume it.
The numbers, and the caveat
The headline figure: as of November 1, 2026, x402 had processed over 196 million transactions across 12 chains, settling over $42 million, per Fireblocks citing agenteconomy.to. Coinbase separately says over 97% of onchain agent transactions in Q2 2026 used x402.
Now the part a skeptic reads twice. Per the same Fireblocks analysis, more than half of lifetime transactions came from a two-month burst in late 2025, when automated scripts minted and sold a token called PING that was issued through x402. Activity has since dropped: October 2026 shows about 5.1 million transactions worth roughly $274,000.
That is not a verdict on the protocol. It is a reminder that a transaction count measures how many times something happened, not who paid whom for what. Decrypt itself frames the central question as whether the high counts turn into steady, real commerce. Treat any single total, ours included, as a number that names its source and its window.
One more warning from the article: speculative "x402" tokens exist on various chains, and neither Coinbase nor the foundation issues them. Decrypt's advice is to be very wary of any token claiming to be the official x402 coin. The standard has no coin.
Not the only rail
x402 sits among several agent-payment approaches. Decrypt names the Agentic Commerce Protocol (Stripe and OpenAI), Visa's Trusted Agent Protocol, and the Machine Payments Protocol from Stripe and Tempo. MPP also uses HTTP 402 but adds session-based billing, so an agent can pay as it goes instead of settling every request onchain. Stripe and Visa are also x402 Foundation members, so these are overlapping bets, not a clean fight.
What to build with it
If your agent buys data or API calls, you need a wallet holding a supported stablecoin on a supported network, usually USDC on Base, with spending limits so a loop bug cannot drain it. Decrypt mentions Coinbase Developer Platform wallets and Circle Wallets for that job. The prompt is the cute part. The wallet controls and the payment rail are the stack.
Sato maps those pieces, wallets, payment rails, MCPs and skills, so you can describe the agent and see what builds it: satohub.ai/build.
What to watch
- ▸Repeat payers. Steady buyers paying for real services would say more than another burst of volume.
- ▸Foundation members shipping. Which of the 57 reported members move from support statements to live x402 endpoints.
- ▸MPP and x402 overlap. Whether session billing and per-call settlement end up as complements or competitors.
- ▸Numbers with windows. Totals that name the chain, the period and the source. Anything else is decoration.