Cloudflare Wires Up HTTP 402 to Charge AI Agents Per Request
The HTTP 402 status code has sat unused since the 1990s, labeled “Payment Required” and waiting. Cloudflare just wired it up so any resource behind its network can charge AI agents a few cents in stablecoins per request.
Cloudflare's Monetization Gateway revives the dormant HTTP 402 status code: any page, API, dataset or MCP tool behind Cloudflare can now return a price that AI agents pay in stablecoins, settled in under a second. Sample pricing runs to $0.001 per call plus $0.01 per MB.
The catch the thread seizes on: payment is stablecoin-only and Cloudflare-brokered. A developer who shipped a Bitcoin Lightning version of this eight years ago notes such paywalls have existed for years and never reached critical mass.
Turning on the web's dormant payment code
Cloudflare's Monetization Gateway lets a site charge for any asset it already protects: web pages, datasets, APIs, or MCP tools. It runs on x402, an open protocol named after HTTP's long-dormant 402 "Payment Required" status code, and it settles at the network edge rather than at the origin server. The flow is mechanical: a client requests a gated resource, gets back a 402 with pricing, pays, then resubmits with proof of payment, with Cloudflare targeting sub-second settlement.
Payment is in stablecoins, with USDC named among them; sellers can hold the stablecoins or redeem them for fiat in a bank account. The buyer Cloudflare has in mind is not a person but a bot. Its argument is that "as agents become the dominant Internet users, the model is breaking," because agents "do not look at ads or need to maintain a monthly subscription." Sample prices in the post include a few cents per web search billed per call, a "$0.001 base fee plus a $0.01 per MB charge," and "$0.99 per resolved support escalation." The protocol itself came from Coinbase and now sits under a Linux Foundation body, the x402 Foundation, backed by a coalition of more than 25 companies. Cloudflare frames the endgame as "an agent-first Internet with Internet-scale settlement built in."
The toll-road objection, and the ghosts of micropayments past
A Cloudflare product manager on the project dropped into the thread to field questions, but the reception leaned skeptical. The first snag was the word "open."
"It seems like it is a technology that is intended to be open an universal while also being supported and developed primarily by US companies (Linux Foundation, Coinbase, CloudFlare.)" — a commenter reading the x402 Foundation's roster
The reframe that landed hardest cast the whole scheme as infrastructure for tolls.
"Every road a toll road. … How big a cut does Cloudflare want? Whose 'stablecoin' does this use? … For comparison, FedNow bank to bank transfers cost $0.045, regardless of size." — the author of Nagle's algorithm
Others had seen this movie before.
"For Bitcoin / Lightning these kind of pay-per-request API paywalls have existed for many years already… None became mainstream. I think the friction is always the extra setup on the client side." — a developer who shipped a Lightning pay-per-request paywall eight years ago
The deeper doubt is whether the gateway touches the problem operators actually have.
"This doesn't seem to solve the issue that website operators face... which is providing a free public experience to humans while the price of hosting is driven up by increased bot traffic… if we can't tell bot from human, why would bots choose to pay rather than just use the public endpoints we serve to our customers?" — an operator of a public-facing site
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
Z.ai's ZCode chases Claude Code with GLM-5.2, and looks a lot like Codex
Z.ai, the Zhipu team behind the open-weight GLM models, shipped ZCode: a desktop coding agent wired to GLM-5.2. What several developers spotted is that the app is closed source and its UI reads as a near-copy of OpenAI's Codex.