Cloudflare starts charging AI agents over HTTP 402

Cloudflare has opened a closed beta of its Monetization Gateway, a service that lets a site owner charge an AI agent for a single request instead of selling it a subscription or handing it an API key. Sellers decide which requests cost money, how much they cost and where the payment goes. Buyers are quoted a price inline with the request and receive the resource once the payment has settled.

The mechanism is the HTTP 402 Payment Required status code, a slot reserved in the original HTTP specification that the web has almost entirely ignored. Cloudflare's implementation keeps the transaction inside the request, so there is no redirect to a checkout page and no separate payment API to call. Payment verification and settlement run through Coinbase's x402 Facilitator, and payments settle on the Base blockchain in USDC, a stablecoin pegged to the US dollar.

A paywall priced per request

Pricing is written as rules that match any part of a request, whether that is the URL, a header or a query parameter, and sellers choose between several pricing schemes. In its simplest form, Cloudflare describes the product as a paywall for agents. The company says it plans to make seller services discoverable to agents, expose logs for every transaction, support additional payment rails and add identity primitives.

Four customers already in production

The beta arrives with four production users. Ceramic.ai charges agents to run a web search against an index of more than 40 billion pages that answers in as little as 50 milliseconds, which lets an agent decide how hard to look based on the task rather than rationing itself against a budget. Stocktwits sells per-request signals on a ticker, including sentiment, message volume, follower counts and trending status, without requiring a data licence.

API2PDF returns HTTP 402 to callers who arrive without a key and uses variable pricing to quote the maximum a single request could cost, settling only the consumption once the client has paid. The company says it was losing more than half of its conversions at the point where customers had to supply a card after their first month. Cloudflare's own AI Gateway is the fourth: customers in the United States can now pay for inference at request time on a selection of models by sending the header PAYMENT-METHOD: x402.

A companion beta for publishers

Content is priced differently. Pay Per Use, also in beta, has a buyer offer a price for a specific use of a page, the publisher accept or decline that offer, and the buyer report each use so that Cloudflare can bill the buyer and pay the publisher monthly. Cloudflare argues that charging per crawl, as its earlier Pay Per Crawl product does, makes buyers pay before they know what they need. Both products sit on the same foundations of identity, metering, pricing and analytics.

Our opinion

The clever part of the Monetization Gateway is not the 402 plumbing, which is a decade-old idea only now getting a customer, but the admission that an agent is a different kind of buyer. Subscriptions assume somebody who signs up once and forgets about it; agents arrive with no memory, no card and no patience, and they will happily spend half a cent to save a thousand tokens. Cloudflare is betting that sellers would rather be paid per request by a machine than scraped for free by one, and it already has four companies taking that money in production. The open question is whether x402 and USDC become the rail agents actually carry wallets for, or whether the payments industry ships something less exotic first. Either way, the paywall for bots is now a product with a dashboard.