Build2 publishers2 min readPublished
Cloudflare opens a closed beta that bills AI agents per request over HTTP 402
Cloudflare put its Monetization Gateway into closed beta, letting domain owners charge AI agents per request via HTTP 402, with four use cases in production. Cloudflare scopes it to APIs, tools and data, where each request is a single use.
The Engineer · Build desk
What happened
- Payment is offered over HTTP under the 402 Payment Required status code, inline with the request, with no redirect to a checkout page and no separate payment API.
- Sellers write pricing rules that match a request's URL, headers or query parameters, and choose among several pricing schemes.
- Coinbase's x402 Facilitator verifies and settles each payment, while Cloudflare absorbs failures, retries, analytics and changes to the x402 protocol.
- Pages crawled once and reused many times go to a separate Cloudflare program, Pay Per Use, where verified buyers report each use and pay for it.
- Cloudflare lists transaction logs, agent discovery, additional payment rails and identity primitives as future plans.
Compiled by The EngineerSomething wrong?How this is made
Why it matters
- constraint Publishers whose pages are fetched once and reused have to go through Pay Per Use and its verified buyers to charge for the reuse, since per-request billing reaches one use in a thousand in Cloudflare's own example.
- decision Teams building agents that call priced APIs or MCP tools have to fund a wallet that can sign USDC authorizations on Base before their first paid call.
- exposure Every settlement in the beta runs through one facilitator on one chain, so a delay or fee change at Coinbase's facilitator or on Base reaches every paid request a seller serves.
- capability A seller can price individual API requests or MCP tool calls without writing or maintaining payment, retry or x402 protocol-upgrade code.
A buyer receives payment instructions, signs an authorization, and gets the resource only after the payment has settled [10]. Settlement time is therefore part of every paid response [3]. Cloudflare's post does not say how long settlement on Base takes or what a transaction costs. Its case for stablecoins is that today's popular rails assume high latency, large dollar values and a buyer the seller can identify, and that agents need the opposite [6]. It says stablecoin networks can meet those requirements today [7]. For that to hold on a particular API, settlement has to finish inside the latency budget of whoever is waiting on the agent's answer.
The best engineering decision in the post is a limit Cloudflare puts on its own product. A 402 exchange prices the request it answers [9]. Cloudflare's example of where that falls short is a page crawled once and used a thousand times [8]. Billed per request, that page collects on one fetch out of 1,000 uses, or 0.1% [1].
Cloudflare's own shorthand, a "paywall for agents", is more exact than the product name [11]. Its line that sellers can "go live in seconds with a few clicks" holds for the seller's half of the exchange [11]. The buyer's half is heavier. An agent has to be able to sign an authorization for a USDC payment on Base, the only settlement path the beta offers [2].
Identity is where Cloudflare's two products part ways. Pay Per Use runs on verified buyers who report their own use [8]. The gateway grants access on a settled payment, with identity primitives listed as a later addition [4]. Cloudflare's post counts an identifiable buyer among the assumptions of today's rails that agents do not meet [6].
Cloudflare describes agents as "the predominant source of traffic on the Internet" [5]. It argues that subscriptions and prepaid credits need a considerable upfront outlay, so buyers limit themselves to a few that fit their budget [4]. It wants prices in the agent's units: per request, per search query, per token [6]. The first production case in the post is Cloudflare's own AI Gateway, used to pay for inference [16].
What to watch
- Whether Cloudflare publishes settlement latency and per-transaction costs for paid requests on Base.
- Which payment rail joins USDC on Base first, and whether it settles through a facilitator other than Coinbase's.
- When identity primitives ship, and whether the gateway then lets sellers price by verified buyer the way Pay Per Use does.