Lifestyle

Cloudflare Launches Monetization Gateway Closed Beta: Charging AI Agents Per Request with HTTP 402

Cloudflare has opened a closed beta of Monetization Gateway, which lets website and API owners charge AI agents each time they use a page, tool or dataset, with payment built into the web request itself via the HTTP 402 status code. Here is how it works, the four customer examples Cloudflare describes and who it affects.

About 6 min read

Cloudflare Launches Monetization Gateway Closed Beta: Charging AI Agents Per Request with HTTP 402
Image: Mokaair (Original editorial artwork)

What happened

On September 30, 2026, Cloudflare announced on its official blog that Monetization Gateway is launching as a closed beta, meaning access is limited to approved participants. The announcement showcased four customer use cases already running in production. The company said it first announced the plan about three months earlier. According to Cloudflare, the gateway lets domain owners charge AI agents for access to websites, APIs, MCP tools (tools that agents can call) or datasets. AI agents are software that carries out tasks on someone's behalf. Applications are made through the Cloudflare Dashboard.

In the post, Cloudflare argues that agents are now the predominant source of traffic on the internet. It says today's popular payment rails, meaning the networks that move money between buyers and sellers, assume buyers will tolerate high latency, transact only in large amounts and be identifiable to sellers. None of that fits how agents operate. The company says stablecoin transactions can currently support payments per request, per search query or per token. This is Cloudflare's own view.

Cloudflare Launches Monetization Gateway Closed Beta: Charging AI Agents Per Request with HTTP 402
Mokaair editorial verification flow · Image: Mokaair (Original editorial artwork)
Read the full description

Sources are collected, independently checked, then reviewed by Jev.

How it works: putting payment inside the HTTP request

As Cloudflare describes it, Monetization Gateway uses the HTTP 402 Payment Required status code, a standard code a web server can send back when payment is required. Sellers configure which requests require payment, how much they cost and where the funds go. Buyers, usually AI agents, receive payment instructions and sign an authorization. They obtain the resource only once the payment has settled. Cloudflare stresses that the flow needs no redirect to a checkout page and no separate call to a payments API. It can be thought of as "a paywall for agents."

Cloudflare says sellers can write pricing rules that match on URLs, headers or query parameters, and choose from several pricing schemes. Payment verification and settlement are handled through Coinbase's x402 Facilitator. Funds settle on the Base blockchain in USDC, a stablecoin pegged to the US dollar. The company also notes that high-value content, which may be crawled once but used a thousand times, is handled by a separate Pay Per Use offering. Over time, Cloudflare says it plans to:

  • Help sellers make their services discoverable to agents
  • Expose logs for all transactions
  • Support additional payment rails
  • Incorporate identity features

Comparing the four customer examples

Cloudflare's announcement lists four live use cases. They span AI inference (running an AI model to produce an answer), web search, market data and document conversion. The summary below is based on Cloudflare's post.

Four Monetization Gateway customer examples (source: Cloudflare official blog)
ServiceWhat it offersPricing (per Cloudflare)Highlights
Cloudflare AI GatewayAI model inferencePrices can be supplied by the originUS-based Cloudflare customers can add a PAYMENT-METHOD: x402 header to pay at request time for a select set of models
Ceramic.aiWeb search API designed for agentsFixed pricingIndex of over 40 billion pages, results in as little as 50 ms; no API key needed
StocktwitsData signals derived from market discussionPriced per individual requestSeparate agent-only path; existing API and enterprise data products unchanged
API2PDFHTML and Office documents to PDFVariable pricing, with a maximum per-request cost disclosed upfrontOnly actual usage is settled; credit card requirements previously caused over 50% conversion drop-off

Take API2PDF as an example. Cloudflare notes that the service launched in 2018 and previously required customers to create an account and obtain an API key. Customers then had to provide a credit card after the first month, which led to over 50% conversion drop-off. Now, requests without an API key receive an HTTP 402 response, and the request is fulfilled once payment is completed. As for Stocktwits, Cloudflare says the platform launched in 2008 and is used by more than 10 million people.

Practical impact for everyday readers

Most everyday users will see no direct change in the short term. The service is a closed beta open only to eligible US sellers and buyers, and Cloudflare says support for other regions is on the way. It mainly affects website operators, API developers and teams building AI agents.

In the longer term, such mechanisms could become widespread. Some data and tools online might then shift from "subscriptions or prepaid credits" to "agents paying each time they use something." More automated small payments could happen behind the scenes when people use AI assistants. Users and businesses may need to watch the scope of their agents' payment authorizations and their spending limits. These are inferences drawn from the announcement, and actual developments remain to be seen.

Frequently asked questions

What is HTTP 402?

HTTP 402 Payment Required is a status code in the HTTP protocol, the system web browsers and servers use to talk to each other. According to Cloudflare, Monetization Gateway uses it to let buyers pay within the same flow as requesting a resource. There is no redirect to a checkout page and no separate payments API call.

Can ordinary people use it now?

Cloudflare says it is currently a closed beta open only to eligible US sellers and buyers, with applications made through the Cloudflare Dashboard. Support for other regions is on the way.

How are payments settled?

According to Cloudflare, payment verification and settlement are handled through Coinbase's x402 Facilitator. Settlement happens on the Base blockchain in USDC, a stablecoin pegged to the US dollar. The company also says it plans to support additional payment rails over time. This is not investment advice.

How is this different from an ordinary website paywall?

Cloudflare describes it as "a paywall for agents." It charges per use, with payment embedded directly in the HTTP request. That makes it suited to resources such as APIs, tools and data, where each request is a single use.

Who does this mainly affect?

Mainly website operators, API developers and teams building AI agents. During the closed beta, only eligible US sellers and buyers can take part, so most everyday users will not notice a direct change in the short term.

Browse the latest news in this topic

Latest travel guides

Sources

Lifestyle