Drop-off in conversion at the credit card step (API2PDF): >50% (Source: Cloudflare blog, Monetization Gateway beta (September 30, 2026))
The checkout page was built for people
Most software is sold by subscription or prepaid credit. A buyer signs up, enters a card and commits money up front. That works for a person choosing a few tools. It works poorly for software that decides on its own which services to use.
This is the idea behind a beta Cloudflare announced on September 30. Cloudflare says agents are now the main source of internet traffic, and that they buy in small units: per request, per search, per token. In its view, today's payment systems assume slow, large and identified buyers. Cloudflare argues that stablecoin networks can meet the needs of agents and that existing rails cannot.
The mismatch is as much a business problem as a technical one. A site that cannot accept very small payments from a machine cannot sell to it this way. That is the author's view, not Cloudflare's finding.
What Cloudflare launched
The Monetization Gateway is in closed beta. It lets a domain owner charge agents for access to a website, an API, a tool server (MCP) or a dataset. Eligibility is limited to U.S.-based sellers and buyers for now. Cloudflare says support for new regions is on the way.
Cloudflare describes the design as a "paywall for agents." Sellers write pricing rules that match the URL, headers or query parameters of a request. They choose a pricing scheme and say where the money should go.
How the payment works
The gateway uses HTTP 402 Payment Required. This is a status code the web has long reserved for payment. When an agent asks for a protected resource, the server replies with 402 and the payment instructions. The agent signs an authorization. Once payment settles, it receives the resource.
Payment rides along with the request itself. The agent is never sent to a separate checkout page or asked to call a second payment service.
Behind the scenes, Cloudflare says it handles verification and settlement through Coinbase's x402 Facilitator. The money moves as USDC, a token tied to the U.S. dollar, on the Base blockchain. Cloudflare also handles retries, failures and analytics. It says it plans to add discovery, transaction logs, more payment rails and identity features over time.
Four production uses, one of them Cloudflare's own
Cloudflare presents four cases running in production. Three are outside companies: Ceramic.ai, Stocktwits and API2PDF. The fourth is Cloudflare's own AI Gateway.
Through AI Gateway, U.S. customers can pay for inference on selected models at request time. They add the header PAYMENT-METHOD: x402. Cloudflare presents this as an alternative to holding a credit balance, which it calls unnecessary friction as more agents carry wallets.
Ceramic.ai sells a search API for agents. It says its index holds more than 40 billion pages and can return results in as little as 50 milliseconds. Agents pay per search without an API key. Cloudflare points out that search demand swings widely: one query for a simple question, hundreds for a research task. Paying as it goes lets the agent decide how hard to look, instead of staying inside a budget fixed beforehand.
Stocktwits opened a new lane for agents to its investor-conversation signals, such as whether posts lean bullish or bearish. Its current API and enterprise data products stay as they are. Each agent request is priced individually.
API2PDF generates PDFs through an API. Cloudflare reports that once users had to supply a credit card after the first month, conversion dropped by more than 50%. Now a request without an API key gets a 402 reply. Because cost varies per request, the reply states the maximum a single request could cost. Only actual consumption is settled.
What the announcement does not show
This is Cloudflare describing its own product and the cases it chose to show. The post gives no figures on payment volume, revenue or the number of agents paying.
One of the four cases is Cloudflare's own product. That leaves three outside companies. Three examples are not a trend.
The announcement also does not cover how buyers should limit what their agents spend. The API2PDF maximum-price design is one example of a cap set on the seller's side. Whether a buyer can set its own limits is not something the source describes.
Questions to put to your team
If you sell data, an API or tools: which requests would an agent pay for by the unit? Could you offer that without touching your existing contracts, as Stocktwits did with a separate path?
If you build or deploy agents: who approves spending, and what stops a loop from running up a bill? Who reviews the wallet and its transactions?
If you handle finance or compliance: how would stablecoin settlement be recorded and audited? Cloudflare's beta is limited to the U.S., so the question is not yet pressing for everyone.
The checkout page assumed a person was watching. This beta tests what happens when almost nobody is. What it has not yet shown is whether buyers and sellers will trust the controls around it.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Cloudflare.
