Cloudflare turned a 30-year-dormant HTTP status code (402 Payment Required) into a new business: letting AI agents (autonomous AI programs that call tools to complete tasks) pay per call to access websites, APIs (application programming interfaces), and datasets. What makes this worth our attention: it signals that the future internet's "customer" is no longer a human, but the AI running errands on their behalf.
What this is
On Monday, Cloudflare launched the "Monetization Gateway," three years in the making, currently in closed beta. In one sentence: owners of websites, APIs, and datasets can now charge AI agents per call when they access them.
Technically, it activates HTTP status code 402, which has sat on the protocol shelf for nearly 30 years. In the past, accessing a webpage was "human → server"; in the future, it will be "AI Agent → server → pay → get data." Payments run over stablecoins (digital currencies pegged to fiat like the US dollar), because traditional credit card networks are unfriendly to sub-cent high-frequency microtransactions. Cloudflare disclosed that four customers are already running pay-per-use scenarios in production across APIs, tools, and datasets.
Industry view
Supporters see this as the last missing piece of infrastructure for the "Agent Internet" — only when AI can spend small money on small tasks will developers have real incentive to keep delivering high-quality data and services. Cloudflare's own judgment: within five years, the majority of internet traffic will be generated by Agents, and Agents consume by the call or the token, not by monthly subscription.
The objections and risks are equally clear. First, HTTP 402 slept for 30 years for a reason — billing, reconciliation, and dispute handling are each non-trivial. Stablecoin compliance, exchange-rate volatility, and refund mechanisms have no industry consensus today. Second, if "pay-per-call" becomes mainstream, small and mid-sized content sites that rely on subscriptions, ads, and SEO traffic could be inversely marginalized — fewer Agent calls means less exposure. Third, Cloudflare is simultaneously the infrastructure provider and the payment intermediary; conflicts of interest and data visibility will be amplified.
The cooler read: Cloudflare is betting that an "Agent traffic explosion" will happen, but real-world Agent commerce volume is still very small today. Working in proof-of-concept is not the same as running at scale.
Impact on regular people
For enterprise IT and data teams: if your company has public APIs, datasets, or tools callable by Agents, now is the time to evaluate the feasibility of "pay-per-use" pricing rather than selling one-time packaged deals. This is a business design problem, not a technical problem.
For individual careers: customer support, junior data lookup, and content curation — work with "low per-call value, cheap per-head billing" — may be replaced faster, since Agents can solve them for a few cents on their own.
For the consumer market: when you open a webpage, the one behind the screen might be another AI price-comparing and ordering on your behalf. Short term it gets smoother; medium term, the chain of your data being scraped by Agents and resold back to you gets longer, and pricing gets more opaque.