The ad-and-subscription internet breaks when the visitor is a bot. Cloudflare’s answer: make the bot pay. Monetization Gateway, waitlisted July 1, lets any website, API, dataset, or MCP tool behind Cloudflare charge AI agents per request — stablecoin settlement, sub-second, fees near zero.
How a 402 becomes a paywall
The whole flow lives inside plain HTTP. An agent requests a resource, the server returns 402 Payment Required with a price, the agent pays in USDC or Open USD and retries with proof, and Cloudflare’s edge verifies and lets it through. No signup, no API key, no prior relationship between buyer and seller. Pricing goes down to fractions of a cent — $0.001 base plus $0.01/MB for uploads, or $0.99 per resolved support escalation. You set rules with the same expression syntax Cloudflare already uses for firewall rules.
Why this matters
x402 is an open protocol — the x402 Foundation sits under the Linux Foundation with 25+ backers, AWS included. But Cloudflare fronts roughly a fifth of the web. When the company that blocks AI crawlers starts selling them access instead, “scrape for free” turns into “pay per crawl.” That’s agent-economy infrastructure, not another paywall widget.
You Might Also Like
- Onecli Puts a Security Gateway Between Your ai Agents and Your api Keys
- Your ai Agent is Burning Tokens on Noise Context Gateway Wants to fix That
- Parlor Runs a Full Voice Vision ai on Your Macbook no api key no Cloud 2 6 gb Total
- Roborock Saros 20 Sonic Launches Globally With a 7 98cm Chassis and an Open api Your Home Assistant Agent can Actually Call
- Assemblyais Voice Agent api Undercuts Vapi and Retell With 307ms stt Latency

Leave a comment