Cloudflare starts charging AI agents per API call, and four companies are already collecting

Cloudflare has taken its Monetization Gateway and a companion product called Pay Per Use out of private testing, announcing on Sept. 30 that U.S.-based sites can now charge AI agents real money for every API call, search query or data request they make, with four customers already running paid traffic through the system live.

The mechanism runs on the old HTTP 402 status code, long reserved for "Payment Required" but rarely used in practice. When an agent hits a protected endpoint without paying, Cloudflare's edge returns a 402 instead of the data. The agent, or the wallet software behind it, reads the price, authorizes payment in USDC on the Base blockchain through Coinbase's x402 settlement system, and retries the request. Cloudflare says a single transaction can settle anywhere from a fraction of a cent up to $100, and sellers can charge either a flat rate or a variable one tied to how much compute or bandwidth a request actually consumes.

What changed

This solves a different problem than the crawler-blocking tools Cloudflare shipped earlier this year. Those let a site decide whether an AI bot could read its pages at all. Monetization Gateway and Pay Per Use start from the assumption that the agent is going to show up anyway, and give the site owner a built-in way to get paid for it without building payment infrastructure themselves. Pay Per Use specifically charges for a reported outcome rather than a raw page fetch: an AI company defines what counts as a "use" of a publisher's work, sets the price for it, and the publisher accepts or declines each offer as it comes in. Cloudflare totals everything up and pays out monthly. That distinction matters because Cloudflare's own argument for the new product is that charging for every crawl makes a buyer pay before it even knows whether a page was useful to it, and many buyers would rather walk away than pay upfront for an unknown. Pay Per Use, by Cloudflare's framing, is meant to get more of those buyers to the table by billing only for outcomes a publisher can see and verify.

Four early customers show how differently the pricing can work in practice. Cloudflare's own AI Gateway charges per inference call across the models it resells. Ceramic.ai, a search API built for agents that indexes more than 40 billion pages, charges a flat fee per query. Stocktwits is now selling its sentiment and trending data to agents through a dedicated paid route, layered on top of its existing licensing deals. And API2PDF, a document-generation API running since 2018, replaced a signup flow that required a credit card up front — which it says cost it more than half of prospective customers before they ever sent a request — with variable per-request billing that only charges an agent for what it actually consumes.

Who it affects

Any software company with documentation, a public API, benchmark data or a content library that AI agents already crawl for free is a candidate here, whether or not it ever planned to sell access. So is any vendor already charging for API usage through a conventional billing stack: Monetization Gateway is effectively a second, agent-native checkout sitting in front of the same endpoints, built for buyers that would rather authenticate with a wallet than fill out a signup form. The beta is still narrow — U.S. sellers and buyers only, with accounts and domains needing to clear Cloudflare's age and security checks — so this is not something most marketing teams need to ship this quarter. But it is the clearest signal yet that a major infrastructure vendor treats "AI agents reading your content for free" as a temporary condition rather than a permanent one.

What to do differently

Start by finding out what is already being read for free. Most software marketers can get a breakdown of non-human traffic hitting docs, pricing pages, and any public API or data endpoint from their engineering team — the same audit that AI-crawler-blocking decisions already require, just read for revenue potential instead of exposure risk. Separately, any team that already prices an API by usage should treat Monetization Gateway as a second front door worth testing in beta rather than a theoretical option later: API2PDF's experience suggests agents will tolerate a pay-as-you-go meter that human developers would not. And product-marketing teams writing pricing pages or API documentation should start drafting the agent-facing version now, even informally — a price list meant for a developer to read is not the same thing as terms a piece of software has to parse and act on without asking a human for clarification.

• Pull non-human traffic logs on docs, pricing pages and any public API or data feed
• For each one, decide: keep it open, block it, or price it through a gateway like this
• If you already meter API usage, apply for the Monetization Gateway beta and test one low-risk endpoint
• Draft a machine-readable version of your pricing terms before an agent has to guess at one

"Publishers shouldn't have to choose between blocking every agent and giving their work away." — Cloudflare, Pay Per Use announcement