Member-only story
There's a status code in the HTTP spec that has been reserved since 1997 and almost never used: 402 Payment Required
. For 29 years it sat there as a placeholder, a joke among backend developers, the "we'll figure out internet money later" IOU of HTTP/1.1.
In the last four weeks, it got a job. On June 15, AWS shipped x402 payment support as a generally available feature of CloudFront and WAF — any site behind Amazon's edge can now charge AI agents per request, settled in USDC, at no extra charge beyond standard WAF pricing. On July 1, Cloudflare opened the waitlist for its Monetization Gateway, the same capability across its network in 330+ cities. Two hyperscalers that together front a massive share of global web traffic implemented the same payment protocol at the edge within two weeks of each other.
And the protocol they picked isn't a speculative whitepaper. Coinbase reports x402 processed over 169 million payments across 590,000 buyers and 100,000 sellers in its first year — before either hyperscaler flipped the switch.
I spent the weekend wiring x402 into a test API and teaching an agent to pay for it. The whole thing took under an hour, the handshake is disturbingly elegant, and I now think per-request agent payments are going to be boring infrastructure by next year. Here's how it works, how to try it in five minutes, and where the skeptics are still right.