HTTP status code 402, "Payment Required," has been sitting in the spec since the 1990s like a reserved parking space nobody ever used. Cloudflare just painted the lines, put up a meter, and pointed it squarely at AI agents.
Two Tollbooths for the Agentic Web
Cloudflare has moved two AI payment products into beta. The Monetization Gateway lets sellers charge AI agents per request for an API, MCP tool, dataset or website, using the open x402 protocol built on that long-dormant 402 status code. An agent requests a gated resource, gets a 402 response stating the price and accepted payment, pays, retries with proof of payment, and the resource is served, with enforcement happening at Cloudflare's edge rather than hammering your origin server.
The second product, Pay Per Use, compensates publishers when an AI company reports actually using their content after retrieval, such as for a cited answer in AI search. Per Search Engine Journal, the AI company defines what a "use" is and sets the price, publishers accept or decline, and Cloudflare handles tracking, billing and monthly payouts. The Gateway beta is closed and limited to U.S.-based buyers and sellers, with requirements like an account older than 60 days and a zone proxied through Cloudflare for at least 30 days.
Your Content Strategy Just Grew a Price List
For years the deal with AI crawlers has been simple: they take, you hope for traffic. This flips the question from "should I block bots?" to "what should I charge them?" Cloudflare's original announcement describes pricing by request type, by task complexity, or only for unauthenticated callers, configurable through the dashboard, API or Terraform, with settlement in stablecoins like USDC.
The fine print matters, though. With Pay Per Use, the buyer sets the price and self-reports usage, so publishers have visibility but limited leverage for now; Cloudflare says counter-offers by use type are coming later. And none of this works unless your content is cleanly structured and sensibly gated in the first place. The sites that win here will be the ones whose CMS already knows which pages are premium, which endpoints are valuable, and which bots are which.
The web's oldest unused status code finally has a business model. Now the real question is whether your site is ready to send an invoice.
If you're wondering which parts of your site or API are worth gating for AI agents, and how to structure your CMS so the answer isn't "all of it, badly," let's map it out together.
Source: Search Engine Journal