Cloudflare has rolled out a new Monetization Gateway that lets providers charge per request for machine-to-machine calls. Announced July 1, the system uses an HTTP 402 payment challenge to gate access to web pages, APIs, datasets, and MCP tools. Payments settle in stablecoins over the x402 protocol, with verification happening at the edge before the request reaches the origin server.
How the Gateway Works
The gateway intercepts incoming requests and returns a 402 Payment Required status if the caller hasn't paid. The caller then sends a stablecoin payment via the x402 protocol. Cloudflare verifies the transaction at the edge, and only after confirmation forwards the request to the origin. That means providers don't have to build their own payment infrastructure or handle crypto wallets directly.
Cloudflare says the system is built for an agent-native future. Agents will soon carry wallets and buy resources without human intervention, the company stated. The gateway reduces the need for prepaid credits and enables true pay-as-you-go endpoints for machine-to-machine interactions.
Sub-Second Settlement and Open Questions
A report from ai|expert on August 6 adds that Cloudflare aims for sub-second stablecoin settlement. The system is positioned for per-request billing on agent inference calls and tool usage. But several questions remain unanswered. The report flags key areas to watch: which stablecoins will be supported, how mature the SDKs are, whether production examples can demonstrate sub-second settlement, how many API and dataset providers adopt the gateway, and what wallet custody patterns emerge.
Cloudflare hasn't released a timeline for broader availability or named any early partners. Providers and developers are waiting to see if the gateway can deliver on its promise of frictionless micropayments for the machine economy.
