Cloudflare Monetization Gateway puts HTTP 402 paywalls in front of agents

Cloudflare's Monetization Gateway, now in closed beta, lets a website, API or data feed charge an AI agent for each request inside the ordinary web exchange. There is no redirect to a checkout page and no separate payment API to call. According to Cloudflare's beta announcement, when an agent requests a paid resource, the gateway replies with HTTP 402 Payment Required, a standard web status code, along with payment instructions. The agent signs a payment authorization and receives the resource once the payment has settled.

Sellers decide which requests cost money by writing pricing rules that match parts of a request, such as the URL, headers or query parameters. Cloudflare handles verification and settlement through Coinbase's x402 Facilitator, x402 being the payment protocol the gateway follows. Payments settle in USDC, a stablecoin pegged to the U.S. dollar, on the Base blockchain. Cloudflare's argument is that subscriptions and prepaid credits fit badly with agents, which consume in small units such as a single search or a single API call.

API2PDF, a service that turns HTML and Office documents into PDFs, shows the change most concretely. It used to require an account and an API key, then a credit card after the first month, a step Cloudflare says cut conversion by more than 50%. Now a request without a key gets a 402 response quoting the most that request could cost, and API2PDF charges only for what the request actually used. Cloudflare announced the plan earlier. This post opens the beta with customers in production, limited for now to eligible U.S.-based sellers and buyers.