Cloudflare has made its Monetization Gateway available as a closed beta, giving eligible businesses a way to charge software agents for access to digital resources on a per-request basis.

The gateway can sit in front of websites, APIs, MCP tools and datasets. When an agent requests a paid resource, the service can use an HTTP 402 payment flow and verify payment before allowing access.

Why HTTP 402 matters

HTTP 402 has long existed as “Payment Required” but has seen little standardised use on the web. The x402 ecosystem is attempting to turn that status code into a machine-readable payment flow suitable for software agents and automated services.

For an AI agent, that means a resource can effectively respond: this request costs money, here is how to pay, and access will be granted once payment is verified.

What Cloudflare's beta supports

Cloudflare says domain owners can use the gateway to monetise resources such as APIs, MCP tools and datasets without building a separate payment-verification layer into each application.

At launch, payment verification and settlement are handled through Coinbase's x402 Facilitator, with settlement in USDC on Base.

Availability is limited

The Monetization Gateway is a closed beta, not a worldwide general release. Cloudflare says eligibility currently focuses on US-based buyers and sellers, and access must be requested.

Why this matters for agentic commerce

Most online business models still assume a human subscriber, shopper or API customer. Autonomous agents create demand for smaller, machine-initiated transactions that may happen too frequently for manual checkout flows.

Per-request payments could make it easier to sell structured data, premium tools, compute or specialised API calls directly to agents.

What businesses should evaluate

Before adopting machine payments, sellers should consider pricing logic, fraud controls, refund handling, accounting, tax treatment, rate limits and whether agents can spend money without explicit human approval.

Bottom line

Cloudflare's closed beta is an early attempt to make machine-to-machine payments a normal part of the web stack. The opportunity is clear, but broad adoption will depend on standards, user controls and wider regional availability.