Cloudflare opens Monetization Gateway: charge via x402

As part of its Content Independence Day announcements (July 1), Cloudflare opened the waitlist for Monetization Gateway — a service to charge for any resource behind Cloudflare: web pages, datasets, APIs or MCP tools, without building your own payments stack.

Payments run on x402, an open protocol named after the HTTP 402 Payment Required status code: a client requests a payment-gated resource → the server responds 402 with a small payload stating the price and accepted asset → the client pays and retries with proof of payment attached → a facilitator verifies before the server returns the resource. Charges settle in stablecoins.

Key points

• A flexible payment rules API expresses exactly when a caller must pay to access your digital resources.
• Supports micro-payments down to fractions of a cent, since the protocol adds almost no overhead.
• No account needed between buyer and seller — the payment itself is the credential.
• Squarely aimed at agentic scenarios: AI agents/crawlers paying machine-to-machine to read content, call APIs or use MCP tools.
• Currently at the waitlist stage for Cloudflare customers.

It is the monetization piece sitting alongside the Search/Agent/Training AI bot controls Cloudflare announced the same day.