Agentic Commerce and the x402 Protocol
How AI-Native Payments Could Reshape Working Capital and Programmable Money
The dormant code that may rewire commerce: HTTP status code 402 — “Payment Required” — was specified in the original HTTP/1.0 RFC in 1996 and promptly left unimplemented for three decades. There was no practical micropayment infrastructure to make it meaningful. That constraint no longer exists. In May 2025, Coinbase launched x402, an open protocol that revives the 402 status code to embed stablecoin payments directly into standard HTTP interactions. The thesis is straightforward: if a machine can request a resource and receive a payment prompt in the same round-trip, with settlement occurring on-chain in milliseconds, then the entire category of “machine-to-machine commerce” becomes technically and economically viable for the first time.
This is not a niche developer curiosity. Within five months of launch, x402 had processed over 100 million transactions. By the week of October 14–20, 2025, the protocol was handling nearly 500,000 payments in a single week — a 10,780% increase from the prior month. The growth reflects a structural reality: AI agents are becoming autonomous economic actors, and they need payment rails that work at machine speed, machine scale, and sub-cent cost.
1) What x402 is, technically
The x402 protocol is elegantly minimal. The interaction flow works as follows:
A client (a human developer, a script, or an AI agent) sends a standard HTTP request to an x402-enabled server — for example,
GET /api/data.If payment is required, the server responds with HTTP 402 Payment Required, including payment instructions in a structured
PAYMENT-REQUIREDheader (price, acceptable tokens, chain identifier).The client constructs a signed payment payload using a supported stablecoin — typically USDC — and retries the request with an
X-PAYMENTheader containing the encoded payload.The server routes verification and settlement to a facilitator (either Coinbase’s hosted infrastructure or a self-hosted node), which confirms the on-chain transaction. The server then returns the requested resource.
