The web just started sending agents a bill

Cloudflare shipped the Monetization Gateway this morning. On the surface it is a Cloudflare feature announcement. Underneath it is a small tectonic shift: the pricing rails for the agent web just went from “coming soon” to “in your CDN dashboard.”

The mechanism is HTTP 402 and the x402 protocol, Coinbase’s tiny handshake that Cloudflare has been co-shepherding through an open foundation. A client hits a resource, gets back “402 Payment Required” with a machine-readable payment offer, submits proof of payment on the retry, and gets the resource. Settlement is in stablecoins today, batched via a deferred scheme so the crawler does not pay per page. Cloudflare says its network already emits over a billion 402 responses a day and that the vast majority of those are agents.

Two things worth sitting with.

First, the unit of pricing quietly stopped being the seat and started being the request. Cloudflare’s own example prices read like a menu: a few cents per web search, a fraction of a cent per megabyte uploaded, ninety-nine cents per resolved support escalation. If you are an ISV, your API can now have a price tag your customer’s agent can pay without a signed contract, without a portal, without a human. If you are an SI, “we bill per outcome, verified at the edge” stopped being a slide and started being a settlement primitive.

Second, this is the first serious answer to the ad-model collapse. AI harnesses have been consuming content without generating page views for two years; publishers and API vendors have been eating that cost. A protocol that puts a price at the door, denominated in fractions of a cent and settled in seconds, is the first infrastructure that could plausibly replace the ad economy for machine traffic. Not necessarily win. But at least contest.

Where this gets uncomfortable for platform vendors: if the ISV can charge the agent directly at the edge, the agent runtime does not need to own the billing relationship. Whoever owned the wallet was going to own the platform. It is now much less obvious that the wallet has to live inside a specific vendor’s agent host.

Build with this in mind. If your 2026 product roadmap still assumes a seat license and a monthly invoice, an agent that reads your docs, uses your API, and disappears is not on it. Cloudflare just made sure that agent leaves a receipt.