Cloudflare spent three months building a paywall for bots that actually have wallets. On September 30 the company opened a Monetization Gateway closed beta so U.S. sellers can charge AI agents for APIs, MCP tools, sites, and datasets without a checkout page or a monthly subscription. Payments ride the HTTP 402 status code, settle in USDC on Base through Coinbase's x402 Facilitator, and start at a $0.001 floor per request in the get-started docs.
We checked that announcement against Cloudflare's Monetization Gateway documentation and changelog entry, then added the request-math and early production cases you will not get from a single outlet rewrite. Fortune also covered the closed beta the same day.
How the payment flow actually works
Cloudflare's docs describe a seven-step loop. An agent requests a protected resource. The gateway returns payment requirements (HTTP 402). The buyer signs an authorization and retries. Cloudflare verifies the signature, the origin produces the response, the gateway settles through Coinbase's x402 Facilitator, and the agent gets the resource. There is no redirect to a card form and no separate payments API for the happy path. Matching can key off URL, headers, query parameters, or caller attributes, including a Verified Bots audience.
Pricing schemes are fixed or variable. Fixed settles the signed amount. Variable lets the origin report the actual cost after work finishes, which matters for PDF renders or token-billed inference where you cannot know the bill before the job runs. Buyers and sellers must be based in the United States during the closed beta.
| Piece | What Cloudflare publishes |
|---|---|
| Status code | HTTP 402 Payment Required, inline with the resource request |
| Settlement | USDC on Base via Coinbase x402 Facilitator |
| Minimum price | $0.001 per charged request (get-started docs) |
| Audiences | Everyone or Verified Bots |
| Schemes | Fixed amount, or variable with origin-reported settle |
| Eligibility | Closed beta; U.S. buyers and sellers |
Request math at the $0.001 floor
Cloudflare's get-started page sets the minimum charge at $0.001. That is not a toy number once agents loop. One thousand paid requests at the floor is $1.00 (1,000 × $0.001). Ten thousand is $10. A research agent that fires 200 search calls on a hard brief would owe $0.20 if every call sat at the floor. Raise the rule to a more realistic $0.01 per search and that same brief is $2.00 (200 × $0.01). Raise it to $0.05 and you are at $10 for one busy task.
That is the whole pitch against subscriptions. An agent that needs one query should not prepay a month of API access, and a seller that wants to meet agents where they browse should not force a credit-card form that never gets filled. Cloudflare's blog even notes API2PDF saw more than a 50 percent drop-off once humans had to add a card after the first month. The gateway's job is to make the unpaid request return 402 with payment instructions instead of a dead end.
Who is already charging agents
Cloudflare is not launching an empty beta. The company lists four production-leaning cases on day one. Cloudflare AI Gateway can take a PAYMENT-METHOD: x402 header so U.S. customers pay for select inference at request time instead of only burning prepaid credits. Ceramic.ai prices web search as fixed per query for machine callers. Stocktwits exposes retail sentiment and volume signals as per-request agent data without rewriting its enterprise licenses. API2PDF uses variable pricing so an HTML-to-PDF job authorizes a maximum, then settles the real compute and bandwidth.
That mix matters more than the marketing line. Search, inference, market signals, and document APIs are exactly the elastic purchases agents make while chasing an outcome. Subscriptions force a human to guess the budget in advance. Micropayments let the agent spend more when the task gets harder.
Geeknewz verdict
If you sell an API, MCP tool, or dataset that agents already hit, the closed beta is worth requesting in the Cloudflare dashboard this week, especially if your conversion dies at the credit-card step. If you are building buyers, treat x402 plus a USDC wallet on Base as table stakes for headless commerce, and expect more rails later because Cloudflare says it will. Geeknewz's view: this is the first mainstream edge network making "pay per agent request" a dashboard checkbox instead of a custom crypto integration, but it is still a U.S.-only beta, so do not rewrite your global billing stack until eligibility widens and you have seen settlement reliability on your own traffic.
Source: Cloudflare Blog; also Cloudflare Monetization Gateway docs, Cloudflare changelog, and Fortune.