x402: from demo to internet infrastructure
Published . Every claim links to a primary source.
Short answer: x402 is an open standard for paying over HTTP, launched by Coinbase on 6 May 2025 alongside AWS, Anthropic, Circle and NEAR and licensed Apache 2.0. On 15 June 2026, Coinbase and AWS announced that publishers using CloudFront and WAF could charge agents per request through x402, initially settling in USDC on Base. Chainalysis reported more than 100 million cumulative transactions on Base through Q1 2026, but also flagged meme-coin farming, so the count is not evidence of production-agent commerce. The specification now sits under the x402 Foundation.
What x402 actually standardises
HTTP has carried a status code for payment since the beginning: 402 Payment Required. It was reserved and never specified. x402 gives it a meaning. A server answering 402 returns the payment terms in headers; the client pays and retries; the request succeeds. That is the whole protocol surface, and its smallness is the point.
Two design choices matter for anyone evaluating it. First, it is transport-agnostic: the specification describes representations for HTTP, MCP and A2A, so the same payment semantics work whether the caller is a browser, an MCP client or an agent-to-agent exchange. Second, settlement is separated from the protocol through facilitators. The exact scheme uses EIP-712 and EIP-3009 on EVM networks and TransferChecked on Solana.
The licence is Apache 2.0. The specification no longer lives with its creator: the repository moved under the x402 Foundation, and coinbase/x402 is now described on GitHub as a development fork. No transfer date is stated on the repository, so we date that observation rather than the event.
The verifiable timeline
| Date | What happened | Why it matters |
|---|---|---|
| 6 May 2025 | Coinbase launches x402, alongside named collaborators AWS, Anthropic, Circle and NEAR. | An infrastructure provider, an AI lab, a stablecoin issuer and a chain, present from day one. The collaborator list predicted the protocol's later shape better than the announcement did. |
| 16 Sep 2025 | Google announces AP2 with an A2A x402 extension for crypto payments. | x402 becomes a settlement option inside another standard rather than a competitor to it. |
| 14 Oct 2025 | Visa unveils the Trusted Agent Protocol and states it is collaborating with Coinbase to align on interoperability with x402. | A card network treating an on-chain payment standard as something to interoperate with, not to displace. |
| Observed 31 May 2026 | The specification repository sits under the x402 Foundation; coinbase/x402 is a development fork; licence Apache 2.0. | Governance separated from the creator, which is the same move AP2 made toward FIDO. No date is published for the transfer. |
| Through Q1 2026 | Chainalysis reports more than 100 million cumulative x402 transactions on Base and flags meme-coin farming activity. | A large on-chain count, but not a clean measure of commercial adoption. |
| 15 Jun 2026 | Coinbase and AWS announce that publishers using AWS CloudFront and WAF can charge agents for content access through x402, initially with USDC settlement on Base. | Payment moves closer to an edge configuration, within the scope described by the announcement. |
Why the AWS integration is the turning point
Every previous milestone was an endorsement. The June 2026 integration is different in kind, because of where the payment logic sits.
Before it, charging an agent per request meant writing code: intercept the request, price it, issue a 402, verify the payment, then serve. Now a publisher already behind CloudFront and WAF configures it. The facilitator verifies inside a single request cycle, so there is no callback, no queue and no separate checkout session. That is the difference between a protocol you adopt and a protocol your infrastructure already speaks, and it is the same distribution argument that made Shopify's June change the most consequential event in UCP's first six months.
It also gives publishers something they have been asking for since crawlers started training models: a priced, per-request answer to automated traffic that is neither blocking it nor giving it away. Whether they take it is an open question, and not one we can answer with a source.
What the 100 million figure does and does not prove
Chainalysis reports more than 100 million cumulative x402 transactions on Base through Q1 2026. That is a published on-chain measurement, but the same source identifies meme-coin farming as a material part of the activity.
It is a transaction count, not revenue. It counts wallet activity, not distinct payers or merchants, and does not isolate production agent commerce. Treat it as evidence that the rails are being exercised, not as a measure of commercial adoption. Our statistics page records it with the same caveat.
Where x402 sits relative to the other standards
x402 is not competing with ACP or UCP, and reading it that way leads to bad decisions. Those protocols describe a commerce flow: a catalogue, a cart, an order, a refund. x402 describes a single priced request. A shopping agent buying a sofa needs the former. An agent paying for one API call, one article or one inference needs the latter.
That is why it keeps appearing inside other standards rather than against them: as an extension in AP2, and as an interoperability target named by Visa when it announced TAP. If you want the layered view, see how AI agents pay, which separates authorisation, commerce flow and settlement.
What to do about it
If you publish content or run an API that automated clients already hit, the June 2026 edge integration is the first version of this that does not require a project. Pricing a request is now a configuration decision, which means the interesting question moved from feasibility to policy: what is a request worth, and which callers do you want.
If you sell physical goods, x402 is not your layer, and implementing it will not help an agent find your products. That work is described in how agents find and read your products. Read the x402 standard page for the dated facts, and the card networks versus open protocols analysis for how the settlement layer is being contested.