Cloudflare Opens a 402 Beta: Agents Pay Per Call in USDC

Cloudflare has opened a closed beta for Monetization Gateway, which lets domain owners charge AI agents per use. Four customers are already running it in production.

The product applies to websites, APIs, MCP tools and datasets. The pitch is narrow and concrete: if agents are going to hit your endpoint anyway, bill them per request instead of per contract.

How the handshake works

The mechanism rests on HTTP 402, the "Payment Required" status code.

Sellers define pricing rules that match a request's URL, headers or query parameters. A buyer that hits a priced resource receives payment instructions, signs an authorization, and gets the resource once payment settles through Coinbase's x402 Facilitator. Payments settle in USDC on the Base blockchain.

Cloudflare is also eating its own cooking. Its AI Gateway now accepts the header Payment-Method: x402, so US-based customers can pay for inference at request time rather than maintaining a prepaid credit balance.

That detail is the one worth noting for anyone building agents rather than selling to them. Prepaid balances are an operational tax on agent workloads: someone has to watch them, top them up, and explain the outage when they run dry. Per-request settlement removes that job.

Three sellers, three pricing shapes

The named production users show the pattern is flexible enough to fit different businesses.

• Ceramic.ai, a web search API built for agents with an index of more than 40 billion pages, uses fixed pricing. Agents pay per search without an API key at all.
• Stocktwits built a separate agent-facing path to sell stock sentiment, message-volume, follower and trending signals per request — while keeping its existing data licenses unchanged.
• API2PDF, a PDF-generation API, now returns a 402 to unauthenticated requests and prices variably, tied to the compute and bandwidth each job actually consumes.

The Ceramic.ai case is the most interesting of the three. Removing the API key removes signup, quota provisioning and key rotation in one move. The payment itself becomes the authentication.

Stocktwits points at the other reason to care. A per-request agent path can be added beside existing licensing rather than in place of it, which is the version of this that a legal team will actually approve.

The limits

Access is currently restricted to eligible US-based sellers and buyers. Cloudflare says support for other geographies is planned, without a date.

Several things a production rollout would need are still listed as future additions rather than shipped features: discoverability tooling so agents can find priced resources, transaction logs, support for more payment rails, and identity primitives.

Read that list carefully before planning around this. Transaction logs and identity primitives are not nice-to-haves for anyone who has to reconcile a bill or answer who bought what. Until they land, this is a beta you pilot on a non-critical endpoint, not a billing system you migrate revenue onto.

What to watch

The single-rail design is the open question. Everything settles in USDC on Base today, and "support for more payment rails" is on the roadmap rather than in the product, so sellers outside crypto-comfortable finance teams are waiting on that line.

The other number to track is the count of production customers. Four is a pilot. The signal that per-call agent billing has arrived is that figure moving by an order of magnitude, and the geography restriction lifting.