Skip to content
Tech News
← Back to articles

Monetization Gateway: Charge for any resource behind Cloudflare via x402

read original more articles
Why This Matters

The Cloudflare Monetization Gateway introduces a new way for businesses to monetize digital assets and APIs through usage-based payments, leveraging the x402 protocol and stablecoins. This shift reflects the evolving web economy, where AI-driven agents demand more granular, pay-per-use models rather than traditional subscription or ad-based revenue. It represents a significant step towards more flexible, scalable monetization strategies aligned with modern digital consumption patterns.

Key Takeaways

7 min read

Today, we are announcing the Cloudflare Monetization Gateway, an engine that will give Cloudflare customers the ability to charge for any asset protected by Cloudflare: web pages, datasets, APIs, or MCP tools.

It will provide a single control plane to manage payment policies and access controls across your applications, while also protecting your origin from high payment volumes by handling payment verification and enforcement at the edge. At launch, payments will settle in stablecoins over x402 , the open protocol we are building with a coalition of more than 25 industry leaders via the x402 Foundation .

The evolving business model of the web

For 30 years, the web has run on a simple economic bargain: trading content for human attention. That attention has been monetized through advertising, subscriptions, and e-commerce. This bargain funded the Internet as we know it.

But as agents become the dominant Internet users, the model is breaking. An agent does not look at ads or need to maintain a monthly subscription to all the tools it wants to access. It reads a page or consumes a data feed once, takes what it needs, and moves on. Across the web, AI crawlers already request content anywhere from a hundred to tens of thousands of times for every visitor they send back .

This reality demands a new model: usage-based pricing for everything. If attention and e-commerce are moving from websites to AI harnesses and AI-written software, then agents should pay for the inputs they need — training data, inference content, developer tooling, and API usage. The natural unit of payment for software is the request, the token, or the outcome, not the seat or the month. A few examples of what that could look like:

A few cents per web search, billed per call

\$0.001 base fee plus a \$0.01 per MB charge for an upload endpoint

\$0.99 per resolved support escalation, paid only when the work succeeds

... continue reading