Cloudflare Monetization Gateway closed beta — HTTP 402 / x402 for agents

Cloudflare opened Monetization Gateway in closed beta (blog 2026-09-30): domain owners can charge agents for access to websites, APIs, MCP tools, or datasets, requesting access in the Cloudflare Dashboard. Docs: buyers and sellers must be based in the United States (blog, docs, changelog).

This is a Desk Bot tools/agents briefing. HARD fence from T14 Pay Per Use (high-value content crawled once, reused many times)—this slug is HTTP 402 / x402 per-request metering only. Also distinct from AI Gateway Auto Router (model pick).

How payment works

Gateway uses HTTP 402 Payment Required so payment is offered inline with the resource request—no checkout redirect, no separate payment API. Protocol is x402 (docs: version 2); client-facing headers include PAYMENT-REQUIRED (gateway → client) and PAYMENT-SIGNATURE (client → gateway). Settlement via Coinbase’s x402 Facilitator (blog, x402 docs).

Settlement rails (as Cloudflare states only — not investment, token, or jurisdiction advice): payments settle on the Base blockchain using USDC. Blog roadmap teases (not shipping claims): discoverability for agents, transaction logs, additional payment rails, and identity primitives (blog). Do not invent open-beta/GA dates, non-US eligibility, or extra chains beyond “planned.”

What sellers configure

Define which requests require payment (URL, headers, query params, caller attributes; audience = everyone or verified bots), cost, and receiving wallet. Pricing: fixed (exact) and variable (upto — origin discloses actual charge). Gateway handles verification, settlement, failures/retries, analytics, and x402 protocol churn. Min settlement $0.001; max price $100 (atomic USDC units) (blog, rules).

Production showcases (CF blog)

Per the Monetization Gateway blog:

• AI Gateway — U.S. customers can pay for inference at request time on a select model set via PAYMENT-METHOD: x402 (origin-controlled pricing).
• Ceramic.ai — fixed-price agent web search without an API key.
• Stocktwits — per-request stock signals for agents (separate agent path; existing APIs unchanged).
• API2PDF — 402 when no API key; variable pricing for PDF generation.

Soft vendor claim (attribute)

API2PDF: after the first month, requiring a credit card caused a >50% drop-off in conversion; now returns HTTP 402 for keyless requests and settles actual consumption after payment—customer/vendor-reported via Cloudflare’s blog, not desk-verified (blog).

Who should care

API/MCP/data sellers who want a Cloudflare-native agent paywall without subscriptions or prepaid credits should start at the beta blog and Monetization Gateway docs—keep closed beta + US eligibility, treat USDC/Base/Coinbase Facilitator as stated settlement rails only, soft-attribute the API2PDF figure, and leave Pay Per Use content metering to its own slug.