Mastering the Cloudflare Monetization Gateway is officially the best proven way for publishers and API developers to monetize generative AI traffic.
On September 30, 2026, Cloudflare moved two major AI payment products into beta. The Cloudflare Monetization Gateway enables sellers to charge AI agents for each request to an API, Model Context Protocol (MCP) tool, dataset, or site. Alongside it, a separate product called Pay Per Use compensates publishers when an AI company reports using their content after retrieval.
Just as marketers must mine first-party data for insights AI search citations, technical SEOs and site owners must adapt their server architecture to capture AI revenue.
If you are tired of AI bots scraping your data for free, here are 5 proven insights into how the Cloudflare Monetization Gateway will revolutionize web monetization.
1. How the Cloudflare Monetization Gateway Works {#how-it-works}
The Cloudflare Monetization Gateway is designed for resources that involve usage with every single request.
Unlike traditional subscription paywalls, the gateway charges an AI agent on a per-request basis. Sellers have total control to decide which requests are billed and at what precise price point. Each monetization rule specifies the target domain, URL, price, and target audience. Sellers can choose to open access to everyone or restrict it entirely to verified bots identified by Cloudflare’s BotBase.
Sellers can also choose between fixed pricing (where requests with fixed inputs all cost the same) and variable pricing, which authorizes a maximum spending limit. For variable pricing, the seller’s origin server reports the actual paid amount, accommodating micro-settlements starting from $0.001 up to $100.
2. HTTP 402 and the x402 Protocol Integration {#http-402}
The technical foundation of the Cloudflare Monetization Gateway relies entirely on the x402 protocol and the HTTP 402 “Payment Required” status code.
When an AI agent attempts to access a protected resource on your server, it is initially blocked. It receives the payment terms and must sign a payment authorization before retrying the request. The payment is instantly processed within this retry request and verified before the seller’s server ever responds with the data.
To handle these micro-transactions securely, payments are processed using the USDC stablecoin on the Base blockchain via Coinbase’s x402 Facilitator. To understand the foundational mechanics of decentralized ledgers, you can review technical documentation on the blockchain.
3. Cloudflare Monetization Gateway vs. Pay Per Use {#pay-per-use}
It is critical to distinguish the Cloudflare Monetization Gateway from Cloudflare’s other new beta product: Pay Per Use.
While the gateway charges an agent upfront for access to a resource, Pay Per Use “pays for what happens next” (such as providing a cited answer in an AI search engine). Under the Pay Per Use model, the AI company defines the use case and sets the price. Publishers simply decide whether to accept or decline the offer.
The AI buyer is responsible for tracking every use by reporting a timestamp, the source URL, and an event ID to Cloudflare. Cloudflare then verifies that the reported use matches an enrolled publisher, bills the buyer, and distributes monthly payouts to the creators.
4. Current Beta Limits and U.S. Restrictions {#beta-limits}
If you want to integrate the Cloudflare Monetization Gateway into your technology stack today, you must navigate several strict beta limitations.
Currently, the gateway is operating in a closed beta. The eligibility requirements dictate that both buyers and sellers must be legally based in the United States. Sellers must have a credit card on file, a verified email address, and a Cloudflare account that is more than 60 days old.
Additionally, the specific DNS zone you want to monetize must be proxied through Cloudflare, be more than 30 days old, and successfully pass all internal zone security checks before you can request access via the dashboard.
5. Live Examples Charging AI Bots Today {#live-examples}
Despite being in closed beta, the Cloudflare Monetization Gateway already supports several live implementations that prove the model works.
Four specific use cases are currently live:
- Ceramic.ai: Provides a web search API for agents with fixed pay-per-search pricing without requiring an API key.
- Cloudflare AI Gateway: Accepts payment per inference request across four open models for U.S. users.
- Stocktwits: Charges AI agents for each market signal request via a dedicated routing path.
- API2PDF: A PDF-generation API utilizing variable pricing based on the actual compute and bandwidth of each specific request.
As this technology scales, the era of AI companies scraping the web for free will rapidly come to an end. You can read the official product announcements and documentation directly on the Cloudflare Blog.
Frequently Asked Questions
What is the Cloudflare Monetization Gateway?
The Cloudflare Monetization Gateway is a new beta product that allows website owners and API developers to automatically charge AI agents a micro-fee for every single request using the HTTP 402 “Payment Required” protocol.
How does Pay Per Use differ from the Gateway?
While the Monetization Gateway charges an AI agent upfront for mere access to data, Pay Per Use compensates a publisher retroactively when an AI company successfully uses their content to answer a user’s prompt in an AI search engine.
How are payments processed in the Cloudflare Monetization Gateway?
Payments are currently processed and verified instantly using the USDC stablecoin on the Base blockchain via Coinbase’s x402 Facilitator, allowing for variable micro-transactions as low as $0.001 per request.
