Cloudflare Opens Closed Beta to Let Sellers Charge AI Agents Per Use

A seller can now put a price on an AI agent’s request and collect payment before delivering the resource. Cloudflare opened the closed beta of Monetization Gateway on September 30, 2026, letting domain owners charge per use for websites, APIs, tools and datasets behind its network. Payment happens inside the request flow, rather than sending the buyer to a checkout page.

From subscriptions to individual requests

Cloudflare announced its plan for the gateway three months earlier. Its argument is that subscriptions and prepaid credits ask buyers to commit money before they know which services an agent will need. An agent pursuing a task may instead visit an unfamiliar site, call a tool or consume a data feed along the way.

The company’s proposed response is to align payment with consumption: a request, search query or token. Cloudflare says it worked with customers to develop the gateway and that four customer use cases were already in production when the beta opened. That is a company-reported deployment claim, not a measure of transaction volume or market adoption.

The payment request travels with the resource request

The gateway uses HTTP 402 Payment Required, a response that tells the buyer payment is needed. The x402 protocol carries the payment authorization within that same HTTP exchange. There is no checkout redirect or separate payment API call. Instead, the buyer receives instructions, signs a cryptographic authorization and retries the request.

Cloudflare’s documentation separates authorization from settlement. The gateway first verifies the authorized payment. The seller’s server then produces a response, and the gateway settles payment through Coinbase’s x402 Facilitator before the buyer receives the requested resource. Payments settle on the Base blockchain in USDC, a stablecoin pegged to the U.S. dollar.

Sellers choose the paid traffic and the price

The seller controls which requests require payment, how much they cost and the receiving wallet. Supported resources include Model Context Protocol (MCP) tools, alongside sites, APIs and datasets. The configuration can distinguish among requests rather than impose one blanket charge across a domain.

• Match the request: rules can use URLs, headers, query parameters or caller attributes, including charging every caller or only verified bots.
• Set a fixed price: the gateway settles the amount the buyer signed and authorized.
• Use variable pricing: the seller’s server reports the actual amount to charge.

Cloudflare says the gateway also handles payment failures and retries, analytics and changes to the x402 protocol. Those functions sit alongside the pricing rules: sellers specify the commercial terms, while the gateway manages the payment machinery.

A request fee has a specific boundary

Access is limited in two ways. The service remains in closed beta, with access requests handled through the Cloudflare dashboard. Its official documentation also requires both buyers and sellers to be based in the United States. The launch therefore does not offer unrestricted participation to every agent or domain owner.

There is also a boundary around what is being sold. Cloudflare describes the gateway as suited to resources where each request is itself a use, such as tools and APIs. High-value content can behave differently: a page retrieved once may be reused many times. Charging for retrieval is therefore not the same as charging for every later use of its contents.

Cloudflare’s next proposed steps reach beyond collecting a request fee. It plans to help agents discover sellers’ services, expose logs for all transactions, add payment networks and incorporate identity features. Those remain plans. The open question is how the gateway will connect paid access with service discovery and buyer identity, rather than simply enforce a price at the point of entry.