Cloudflare Launches Beta for Two Landmark AI Payment Products: Monetization Gateway and Pay Per Use

SAN FRANCISCO — In a move poised to reshape the economic architecture of the internet, Cloudflare officially launched two pioneering artificial intelligence payment products into beta on September 30. The rollout introduces the Monetization Gateway, which allows sellers to charge AI agents per request for accessing APIs, Model Context Protocol (MCP) tools, datasets, or full websites. Simultaneously, the company introduced Pay Per Use, a separate framework designed to compensate publishers when an AI company utilizes their content after retrieval.

These products represent a significant escalation in Cloudflare’s efforts to solve one of the defining challenges of the generative AI era: how to fairly, efficiently, and automatically monetize content and digital services consumed by autonomous AI agents rather than human eyes.

Main Facts: The Core Mechanics of Cloudflare’s New AI Economy

The simultaneous launch of the Monetization Gateway and Pay Per Use addresses two distinct monetization pain points in the modern AI ecosystem: real-time utility access and downstream content utilization.

The Monetization Gateway

The Monetization Gateway is engineered for digital resources that require active compute, data fetch, or programmatic interaction with every request. Unlike traditional subscription models or human-facing credit card checkouts—which often suffer from severe friction and steep conversion drop-offs—the Gateway is built specifically for machine-to-machine transactions.

• Under the Hood: The Gateway leverages the innovative x402 protocol and the standard HTTP 402 Payment Required status code. When an autonomous AI agent attempts to access a protected resource, it receives an immediate response containing payment terms. The agent signs a payment authorization and retries the request. The payment is processed synchronously and verified before the seller’s server generates a response.
• Pricing Flexibility: Sellers retain absolute control. They can implement fixed pricing (where every identical request costs the same) or variable pricing (where a maximum spending limit is authorized, and the origin server reports the precise cost incurred). Settlements range from as low as $0.001 up to $100 per request.
• Infrastructure: Payments are executed using the USDC stablecoin on the Base blockchain via Coinbase’s x402 Facilitator. Cloudflare has confirmed that additional payment rails and fiat support are in development.
• Current Eligibility: The Gateway is currently restricted to a closed beta for U.S.-based buyers and sellers. Sellers must meet rigorous criteria, including maintaining an active Cloudflare account older than 60 days, passing security proxies, and having a valid credit card on file.

Pay Per Use

Whereas Pay Per Crawl (another Cloudflare framework) charges crawlers simply for the right to access a webpage, Pay Per Use rewards what happens after the crawl—such as when an AI search engine synthesizes a publisher’s data into a cited answer.

• The Workflow: Under this model, AI companies define the specific use case and establish a price. Publishers can review these offers, deciding whether to accept or decline. Once opted in, the buyer tracks usage—logging timestamps, source URLs, and event IDs—and self-reports this data to Cloudflare. Cloudflare validates the reporting against enrolled publishers, manages the billing cycle, and distributes monthly payouts.
• Beta Status: During this initial phase, Cloudflare is working directly with undisclosed AI buyers and opt-in publishers to iron out the operational wrinkles of self-reported usage tracking.

Chronology: The Road to the September 30 Beta

Understanding how Cloudflare arrived at this milestone requires tracking a rapid sequence of product iterations and industry positioning over the summer and autumn of 2025:

• July 1, 2025: Cloudflare officially announces the Monetization Gateway, opening an initial waitlist and positioning the underlying technology as an experimental step toward autonomous machine commerce. In the same window, early references to Pay Per Use frame it as an experimental tool for publisher compensation.
• September 18, 2025: Industry analysts and observers compare Cloudflare’s emerging suite—encompassing Pay Per Crawl and Pay Per Use—against alternative models like Google’s AI contribution pilot and Microsoft’s Publisher Content Marketplace. At this stage, the Monetization Gateway is still heavily anticipated but not yet live.
• September 30, 2025: Cloudflare officially pushes both the Monetization Gateway and Pay Per Use into active beta testing, transitioning its frameworks from conceptual waitlists to operational, transaction-capable systems.

Supporting Data and Live Implementations

To demonstrate the versatility of the Monetization Gateway, Cloudflare highlighted four diverse live implementations spanning search APIs, foundational model inference, financial data, and document generation:

1. Ceramic.ai: Ceramic provides a web search API tailored specifically for AI agents, operating on a fixed pay-per-search pricing structure that entirely bypasses the need for traditional API keys. While initially flagged in July as a Pay Per Use content partner, Ceramic acts directly as a seller within the new Gateway architecture.
2. Cloudflare AI Gateway: Demonstrating internal adoption, Cloudflare’s own AI Gateway now accepts payments per inference request across four open-source AI models for U.S.-based users.
3. Stocktwits: Providing a crucial bridge between financial markets and automated agents, Stocktwits utilizes a dedicated route on the Gateway to charge agents for real-time market signal requests.
4. API2PDF: A utility for generating PDF documents programmatically, API2PDF showcases why machine-native payments are vital. Cloudflare’s internal data notes that when API2PDF previously forced human customers to enter a credit card after their first month of use, conversion rates plummeted by over 50%. Streamlining payments via automated agent authorizations aims to eliminate this conversion friction.

Official Responses and Strategic Philosophy

Cloudflare’s executive and technical documentation emphasizes that the traditional web monetization model—built on human attention, intrusive display advertising, and high-friction credit card entry forms—is fundamentally incompatible with an internet dominated by autonomous software agents.

In its public documentation, Cloudflare delineates the exact psychological and operational boundaries of its ecosystem:

"Each AI company defines the use it will pay for and sets a price. Publishers decide which offers to accept, and then can see how often their content is used and what it has earned. Cloudflare handles enrollment, usage records, billing, and payment."

Regarding the philosophical distinction between its content-focused products, Cloudflare notes that Pay Per Crawl is strictly about paying for access, whereas Pay Per Use compensates publishers for value generation further down the pipeline.

Furthermore, the introduction of the Monetization Gateway expands Cloudflare’s monetization taxonomy into three distinct event triggers:

• Pay Per Crawl: Charged per successful retrieval by an AI scraper based on site-owner rates.
• Gateway Requests: Charged per API, tool, or dataset request at rates strictly controlled by the seller.
• Pay Per Use: Disbursed based on downstream utilization, priced by the AI buying entity.

Implications: What This Means for Publishers, Developers, and the AI Industry

The launch of these beta programs carries profound implications for stakeholders across the digital landscape:

For Publishers

For content creators and media organizations struggling to monetize traffic intercepted by AI overviews and conversational search engines, Pay Per Use offers a structured pathway. However, publishers must remain vigilant. Because the current beta relies heavily on self-reported usage data from AI buyers, publishers are placing a degree of trust in buyer reporting accuracy—though Cloudflare acts as an auditor to ensure compliance. Looking ahead, Cloudflare has signaled that future iterations of the beta will introduce counter-offer mechanisms, allowing publishers to negotiate pricing rather than merely accepting or rejecting a buyer’s baseline offer.

For API and Tool Developers

U.S.-based developers offering MCP tools, proprietary datasets, or specialized APIs finally have a turnkey infrastructure for micro-transactions. By utilizing the x402 protocol and USDC on Base, developers can monetize programmatic calls at fractions of a cent ($0.001) without building bespoke billing engines or dealing with traditional payment gateway chargeback fraud.

For AI Companies

AI developers and agent builders gain predictable, legal access to high-value data feeds and computational tools without entering into cumbersome, bespoke enterprise licensing agreements for every minor integration. Automated micro-payments allow agents to dynamically query the best available tools on the fly, dramatically enhancing their autonomy and utility.

Looking Ahead

As the beta periods progress, industry watchers will be tracking several key milestones. First, will Cloudflare soon reveal the identities of the major AI enterprises participating as buyers in the Pay Per Use program? Second, when will the Monetization Gateway expand its geographical footprint beyond the United States?

Cloudflare has already confirmed that support for international regions is "on the way." If successful, these tools could quietly establish the foundational financial rails for the entire autonomous agent economy, transforming how digital value is exchanged in an era where software—not humans—does the browsing.