Cloudflare has announced 'Monetization Gateway,' a system that allows them to charge users every time an AI visits their website.
On July 1, 2026, Cloudflare announced 'Cloudflare Monetization Gateway,' which allows users to set up per-access billing for web pages, datasets, APIs, and MCP tools protected by Cloudflare. This system allows for billing for access from AI agents and software using the x402 payment protocol.
Announcing the Monetization Gateway: charge for any resource behind Cloudflare via x402
When people read websites, they open articles from search results, view ads on pages, subscribe to monthly plans to read paid articles, or purchase products on e-commerce sites. Many web businesses have been built on the premise that people will view pages and react to ads, subscriptions, and purchases.
However, AI agents will read only the necessary data without viewing the ads and then leave the site. Although the agent's output may sometimes include a link as the source, Cloudflare says that AI crawlers can make hundreds or even tens of thousands of requests for each human visitor sent back to the site.
While API services have long used a pay-per-use model, applying a similar usage-based system to web pages or small data retrievals presents a problem: the cost per use becomes so small that payment processing fees and billing management costs outweigh the benefits. Cloudflare explains that a pay-per-use model, where small amounts are charged per use, will be necessary in the age of AI agents.
Cloudflare Monetization Gateway is a gateway that allows you to configure which resources to charge, how much to charge, and under what conditions to request payment for access coming through Cloudflare. This means that website operators and API providers don't have to build their own payment systems; payment verification and access control can be handled on the Cloudflare edge.
Cloudflare has long offered 'Pay Per Crawl,' which allows users to charge content usage fees for their AI crawlers. Monetization Gateway is the next step up from Pay Per Crawl, expanding the scope of billing to include not only content retrieved by crawlers, but also various Cloudflare-protected resources such as APIs, datasets, and MCP tool calls.
The payment process uses x402, an open payment protocol that utilizes the HTTP status code '402 Payment Required'. When a client accesses a resource that requires payment, the server returns the fee, available payment methods, and payment destination. The client makes the payment, submits a payment confirmation, and resubmits the request. Once payment is confirmed, the client can access the resource.
In typical online payments, buyers need to navigate to a checkout screen, create an account, and register a payment method. With x402, payment transactions proceed within normal HTTP requests and responses, making it easy to use even for software that processes large amounts of data at high speed, such as AI agents. Monetization Gateway payments are planned to be made using stablecoins, where transaction fees are less of an issue, even for small amounts.
Specific use cases include charging 1 yen for each GET or POST request to a specific API route, setting variable fees up to 300 yen for tasks with varying processing loads, such as image generation, and requiring payment only for unauthenticated access. Pricing rules can be configured on the Cloudflare dashboard, and are also planned to be manageable as part of infrastructure configuration via the Cloudflare API or Terraform.
Monetization Gateway reduces the load on origin servers because payment verification and access control are performed at Cloudflare's edge. Cloudflare processes x402 transactions across a global network spanning more than 330 cities, aiming to minimize latency by performing payment verification closer to the buyer.
The sellers can use the received stablecoins for trading or exchange them for fiat currency in their bank accounts. Furthermore, the buyer's AI agent will be able to check prices, make payments, and receive responses without prior registration, API key issuance, or contractual relationships. If necessary, agent authentication can be required using Cloudflare's 'Web Bot Auth.'
Cloudflare Monetization Gateway has a waiting list for early access available at the time of writing. Cloudflare states that much of the valuable API calls, responses, and tool usage on the internet is not being adequately monetized, and that they will be developing towards an agent-centric internet where 'the request itself becomes a transaction.'
Related Posts:
in AI, Web Service, Posted by log1d_ts