Monetization Gateway beta: charge AI agents for consumption with HTTP 402

Cloudflare has opened a closed beta for its Monetization Gateway, allowing domain owners to charge AI agents for access to websites, APIs, tools, or datasets with minimal setup. The service uses HTTP 402 status codes to embed payment requests directly into resource access, eliminating the need for redirects or separate payment APIs. Sellers can define pricing rules based on request attributes like URLs or headers, while buyers receive payment instructions and authorize transactions inline. The system is designed to reduce friction for agents, which currently face high upfront costs under traditional subscription models.

The gateway leverages Coinbase’s x402 Facilitator for payment verification and settlement, processing transactions on the Base blockchain using USDC, a U.S. dollar-pegged stablecoin. Sellers retain control over pricing logic, with the option to integrate existing pricing engines or define new rules within the gateway. Buyers authorize payments and receive resources only after settlement, ensuring predictable and immediate access. The approach targets high-frequency, low-latency use cases where agents require granular, per-request billing.

Cloudflare’s AI Gateway is among the first adopters, enabling U.S.-based customers to pay for AI model inference at request time by adding a specific header. The AI Gateway’s existing pricing engine integrates with the Monetization Gateway, allowing sellers to rely on their current billing systems without duplicating rules. This configuration supports complex token-based pricing while maintaining a seamless user experience for agents. The feature is available today via AI Gateway Developer Docs.

Ceramic.ai, a web search API provider, uses the Monetization Gateway to allow agents to pay per search query without API keys, aligning costs with task complexity. Stocktwits, a financial social network, is also testing the gateway to monetize real-time market signals for AI agents. Both companies highlight the gateway’s ability to support elastic, agent-native consumption models, where costs scale with usage rather than fixed budgets.