How Cloudflare’s Two AI Payment Betas Charge Agents and Pay Publishers

Cloudflare put two AI payment products into beta on September 30, 2026, addressing different moments in the exchange between AI services and online content. Monetization Gateway lets sellers charge when an agent requests a resource. Pay Per Use lets publishers receive payment when an AI buyer reports using their content. The first is request-based access; the second is payment for reported use.314

Monetization Gateway: sellers charge for access

Monetization Gateway is in closed beta. A domain owner sets rules for which requests require payment, how much they cost, and which wallet receives payment. Rules can apply to sites, APIs, Model Context Protocol (MCP) tools, or datasets. Cloudflare says sellers can match requests using details such as the URL, headers, query parameters, or caller attributes.34

The Gateway uses the x402 protocol to handle payment authorization in the HTTP request flow. A buyer receives payment instructions, authorizes the payment, and gets the resource after settlement.23 Cloudflare’s setup documentation describes fixed pricing per request and a variable option that authorizes a maximum amount; sellers choose the pricing scheme rather than following a universal published rate.17

Access is restricted: buyers and sellers must be based in the United States, and sellers need an eligible account and domain, a receiving wallet, and access to the closed beta.417 Reporting on the launch identifies USDC as the payment currency, while Cloudflare’s documentation describes the system more generally as x402 payments.6

Pay Per Use: publishers accept offers for reported content use

Pay Per Use works differently. An AI company defines the content use it is willing to pay for and offers a price. A publisher decides whether to accept. If accepted, the buyer reports each use through an API; Cloudflare says it records usage, bills the buyer, pays the publisher, and displays usage and earnings in the publisher’s dashboard.14

That means the payment is tied to a reported use after content has been retrieved—not automatically charged when an agent requests a page. The available information does not specify a standard price, universal eligibility requirements, payout method, or payout schedule for this beta.14

The key difference: access event or reported use

	Monetization Gateway	Pay Per Use
What triggers payment	A matching request for a protected resource	A buyer-reported use of a publisher’s content
Who sets the terms	The seller sets request rules and price	The AI buyer defines the use and offer; the publisher chooses whether to accept
Payment process	x402 authorization within the HTTP request flow	Buyer reports use; Cloudflare handles billing, payment, and usage reporting
Beta access	Closed beta for U.S.-based buyers and sellers	In beta; the available information does not establish universal eligibility rules

The distinction matters for publishers and service owners deciding what they want to charge for. The Gateway is designed for paid access to resources; Pay Per Use is designed for compensation when a buyer reports using content.3414

What Cloudflare has—and has not—disclosed

Cloudflare has showcased four customer use cases for Monetization Gateway, but that does not establish the total number of participating buyers or sellers across the two betas.13 The available sources do not provide aggregate figures for paid transactions, reported content uses, publisher earnings, or overall buyer demand. Without those figures, the launches alone are not enough to estimate likely publisher revenue.1314