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.
Why it matters
- What it limits 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.
- Who has to decide 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.
- Who's exposed 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.
- What's now possible capability A seller can price individual API requests or MCP tool calls without writing or maintaining payment, retry or x402 protocol-upgrade code.
Next story · Invest · 2d ago
Chainalysis counts 138 million x402 agent payments, most of them worth 10 cents or lessConfirmed6 publishers
A buyer receives payment instructions, signs an authorization, and gets the resource only after the payment has settled [3]. Settlement time is therefore part of every paid response [14]. 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 [12]. It says stablecoin networks can meet those requirements today [13]. 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 [2]. Cloudflare's example of where that falls short is a page crawled once and used a thousand times [6]. Billed per request, that page collects on one fetch out of 1,000 uses, or 0.1% [15].
Cloudflare's own shorthand, a "paywall for agents", is more exact than the product name [19]. Its line that sellers can "go live in seconds with a few clicks" holds for the seller's half of the exchange [19]. 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 [16].
Identity is where Cloudflare's two products part ways. Pay Per Use runs on verified buyers who report their own use [6]. The gateway grants access on a settled payment, with identity primitives listed as a later addition [17]. Cloudflare's post counts an identifiable buyer among the assumptions of today's rails that agents do not meet [12].
Cloudflare describes agents as "the predominant source of traffic on the Internet" [18]. It argues that subscriptions and prepaid credits need a considerable upfront outlay, so buyers limit themselves to a few that fit their budget [11]. It wants prices in the agent's units: per request, per search query, per token [12]. The first production case in the post is Cloudflare's own AI Gateway, used to pay for inference [10].
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.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence60
- Adoption20
- Hype gap+20
- Incentives70
- Confidence60
Perspective Coverage
3 publishers- Builder
- Builder 58%
- Operator
- Operator 22%
- Investor
- Investor 20%
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Cloudflare made the Monetization Gateway available as a closed beta and showcased four customer use cases that are in production.
- [2]
The gateway uses the HTTP 402 Payment Required status code so buyers can offer payment inline with the request for the resource, with no redirect to a checkout page and no separate payment API to call.
- [3]
Sellers define which requests require payment, the cost, and where the payment should be sent; buyers receive the payment instructions, sign an authorization, and receive the resource after the payment has been settled.
- [4]
The Monetization Gateway allows domain owners to charge agents for access to their website, APIs, MCP tools, or datasets; access is requested in the Cloudflare Dashboard.
- [5]
Cloudflare plans over time to help sellers make services discoverable to agents, expose logs for all transactions, support additional payment rails, and incorporate identity primitives.
- [6]
The gateway is built for resources where every request is the use, like APIs, tools and data; high-value content differs because a page might be crawled once and used a thousand times, and for that Pay Per Use offers a trusted network of verified buyers who report each use and pay for it.
- [7]
Sellers write pricing rules that match any part of a request, such as the URL, headers, or query parameters, and choose from several pricing schemes.
- [8]
Cloudflare handles payment verification and settlement through Coinbase's x402 Facilitator, failures and retries, analytics, and keeping up with changes to the x402 protocol.
- [9]
Payments settle on the Base blockchain using USDC, a stablecoin pegged to the U.S. dollar.
- [10]
One of the production use cases Cloudflare showcases is its own AI Gateway, used to pay for inference.
- [11]
Cloudflare says most software businesses sell through subscriptions or prepaid credits that require a considerable upfront economic investment, so buyers limit themselves to a few subscriptions that fit into their budget.
- [12]
Cloudflare says payments must match an agent's consumption unit (per request, per search query, per token), and that today's popular payment rails assume high latency, large dollar values, and a well-known or identifiable buyer, while agents desire the opposite.
- [13]
Cloudflare says stablecoin transactions and their underlying blockchain networks are able to support these requirements today.
- [14]
Because the resource is released only after settlement, settlement time is part of every paid response.
- [15]
Per-request billing on a page crawled once and used 1,000 times collects on one fetch out of 1,000 uses, or 0.1%.
- [16]
An agent buying through the gateway must be able to sign an authorization for a USDC payment on Base, the only settlement path in the beta.
- [17]
In the beta, the gateway grants access on a settled payment, with identity primitives still a future plan.
- [18]
the predominant source of traffic on the Internet
- [19]
Cloudflare calls the gateway a 'paywall for agents' and says sellers can go live in seconds with a few clicks.
Sources
3 independent publishers whose own reporting we read for this story.
- blog.cloudflare.comMonetization Gateway beta: charge AI agents for consumption with HTTP 402
1 article · September 30, 2026
- dev.toThe 402 beta is open. The roadmap says 'discovery.'
3 articles · October 2, 2026
- thenewstack.ioCloudflare brings paid access to MCP tools — who controls the agent’s spending?
1 article · October 1, 2026