Cloudflare launched two AI payment products into beta on September 30, giving website owners and API sellers a concrete path to charge or earn money from AI systems that access their content. The Monetization Gateway lets sellers set per-request prices for AI agents; Pay Per Use compensates publishers after an AI company reports actually using their content.
What are the two products and how do they differ?
The two products target different moments in how AI systems interact with content. Monetization Gateway charges at the point of access; Pay Per Use pays after the AI company reports a use. Cloudflare’s own post frames the distinction directly: Pay Per Crawl (launched in 2025) “charges for access,” whereas Pay Per Use “pays for what happens next,” such as a cited answer in AI search.
- Monetization Gateway: sellers protect APIs, MCP tools (Model Context Protocol tools, a standard way for AI agents to call external services), datasets, or sites. Each incoming request from an AI agent triggers a payment flow before the content is delivered. Currently in closed beta for U.S.-based buyers and sellers.
- Pay Per Use: publishers enroll and choose which AI companies’ offers to accept. The AI company crawls and indexes content normally, then self-reports each downstream use. Cloudflare bills the AI company and pays publishers monthly.
How does the Monetization Gateway actually work?
The Gateway uses the x402 protocol (an emerging open standard that adds payment instructions directly into HTTP web requests) and the HTTP 402 “Payment Required” status code. When an agent tries to access a protected resource, it first receives the payment terms, signs a cryptographic authorization, then retries the request. Payment is verified before the seller’s server responds, according to Cloudflare’s documentation published September 30.
Pricing is either fixed (every matching request costs the same) or variable (seller sets a maximum; the seller’s server reports the actual amount charged). For variable pricing, settlements start at $0.001, with prices up to $100, per Search Engine Journal. All payments are processed in USDC (a digital dollar stablecoin pegged 1:1 to USD) on the Base blockchain via Coinbase’s x402 Facilitator. Cloudflare says it plans to add more payment methods.
Sellers configure rules specifying the domain, URL, price, and target audience. The audience can be open to everyone or restricted to verified bots identified by Cloudflare’s BotBase system.
Eligibility for sellers currently requires: a U.S.-based account, a credit card on file, a verified email address, an account older than 60 days, and a zone that is proxied through Cloudflare, is more than 30 days old, and passes zone security checks.
Which sellers are live today?
Cloudflare lists four live implementations as of the beta launch, per Search Engine Journal’s October 1 report:
- Ceramic.ai: a web search API for agents, with fixed pay-per-search pricing and no API key required. Cloudflare described Ceramic as a Pay Per Use partner in July; in the Gateway it acts as a seller.
- Cloudflare’s own AI Gateway: accepts payment per inference request (the process of an AI model generating an answer) across four open models for U.S. users.
- Stocktwits: charges per market signal request via a dedicated agent route.
- API2PDF: a PDF-generation API using variable pricing based on each request’s compute and bandwidth. Cloudflare’s post notes that requiring a credit card after the first month caused API2PDF to see a drop of over 50% in conversion, illustrating one business case for metered access without upfront commitment.
How does Pay Per Use track what gets paid?
Usage under Pay Per Use is self-reported by the AI company. For each use, the buyer reports a timestamp, the source URL, and an event ID as a single line of JSON. Cloudflare’s blog post acknowledges that “usage is self-reported” while noting that “the program rules require complete reporting” and that Cloudflare checks each reported use maps to an enrolled publisher. The company then bills the buyer and pays publishers monthly.
Publishers review available offers in the Cloudflare dashboard under Monetize > Pay Per Use, seeing the AI company, the type of use being paid for, and the offer price. They can accept or withdraw at any time. Each program’s terms also define what the AI company may do with the content, including any restrictions on training.
During the beta, Cloudflare says it is working directly with each buyer and with publishers who opt in, without publicly naming the AI company buyers.
What this means for AI-search visibility
Think of it this way: until now, when an AI answer engine read your article and gave a user a summary, you got nothing. These two products are an infrastructure-level attempt to attach a price tag to that moment, at scale, without requiring you to negotiate a deal with every AI company individually.
The practical significance is in the architecture, not just the business model. Payment is embedded directly in the HTTP request flow, meaning an AI agent that hits a Monetization Gateway-protected resource either pays automatically or gets blocked, with no separate checkout or API credential needed. For publishers with high-value, fast-changing content (news, research, trade data) that AI products actively seek out, this lowers the barrier to monetizing that access considerably.
That said, the Pay Per Use model carries a structural tension worth watching. Because usage is self-reported by the AI company, publishers have limited independent means to verify whether every use is being reported. Cloudflare’s role as the billing intermediary provides one layer of accountability, but the system ultimately depends on buyer compliance with program terms. How Cloudflare enforces complete reporting at scale is a question the beta period will need to answer.
In Hingewise’s view, the more strategically interesting product for most publishers is Pay Per Use, not the Gateway. The Gateway primarily serves API and data sellers who can technically enforce access. Most content publishers cannot gate their pages without hurting organic search indexing. Pay Per Use sidesteps that problem entirely: crawling stays open, but downstream commercial use triggers payment. If major AI search players join as named buyers, that changes the economics of publishing for AI audiences meaningfully. Right now, the buyer side of the beta is unnamed, which is the single most important unknown to track.
For brands thinking about AI-search visibility, there is a secondary implication: content that participates in Pay Per Use programs gets flagged as “enrolled publisher” content to verified AI buyers. Whether that enrollment influences how AI systems prioritize or attribute sources is not stated by Cloudflare, but it is worth monitoring as these products move from beta to general availability.
The key development to watch next is which AI companies sign on as named buyers in Pay Per Use. That disclosure, more than any technical detail, will determine whether these products reshape the economics of AI content access or remain a niche option for a small set of API sellers.
Sources: Search Engine Journal, October 1, 2026; Cloudflare Blog, September 30, 2026; Cloudflare Developer Docs, September 30, 2026
Lam Nguyen · Hingewise
This article was drafted with AI assistance from the sources cited above and checked against them before publishing. The "What this means for AI-search visibility" section is Hingewise's editorial analysis, built on the frameworks and positions we use in our GEO work. How we work: Editorial policy.