Cloudflare's Monetization Gateway and What It Means for x402

Cloudflare just launched Monetization Gateway, betting that AI agents should pay for content. Now, anyone using Cloudflare can charge for access to a page, API, dataset, or MCP tool with x402, which brings back the old HTTP 402 "Payment Required" status code. When an agent tries to access a protected resource, it gets a 402 response with a price, pays in stablecoin, and then tries again with proof of payment. Payments are settled directly between parties in less than a second, with almost no fees. Cloudflare handles this at the edge in over 330 cities. Bot traffic is either charged or blocked before it ever reaches your server. This makes the protocol worth building on.

I've been using a similar setup on Uristocrat. In my case, an x402 Cloudflare Worker uses Stripe's x402 system to charge bots and crawlers for each request, based on what kind of bot they are, while people can browse for free. Cloudflare's new release shows this idea has legs. The old web relied on trading content for human attention, making money from ads and subscriptions. But that approach fails when visitors skip ads or don't subscribe, yet send thousands of requests every day.

The question isn't if publishers will start charging agents, but what the price should be, who controls the payment verification layer, and whether services like Cloudflare's and Stripe's will come together or stay separate.