Cloudflare has announced a planned Monetization Gateway that would let customers charge AI agents and automated systems for access to web pages, datasets, APIs and MCP tools delivered through its network.

Customers would define which resources require payment, while Cloudflare would verify payments and enforce access at the edge. The gateway builds on Pay Per Crawl, Cloudflare’s project to let publishers charge AI crawlers for content access, but expands the model beyond publisher content to the data feeds, API endpoints and tool calls software agents may need.

The Monetization Gateway is built around x402, an open protocol that revives the HTTP 402 “Payment Required” status code for machine-to-machine payments. Under that model, a client requests a protected resource and receives a response with the price and payment instructions. The client then pays and repeats the request with payment proof attached. If the payment is verified, the resource is returned.

The protocol is not solely a Cloudflare project. In April, the Linux Foundation announced the x402 Foundation, intended to provide a neutral home for the protocol as it moves toward an open source model, after Coinbase contributed it. The governing body was initially developed by Coinbase, Cloudflare and Stripe, with early support from companies across cloud, payments and commerce, including AWS, Google, Microsoft, Shopify, Visa, Mastercard and American Express.

Cloudflare said the Monetization Gateway will initially support payments settled in stablecoins through x402. Sellers would be able to keep the stablecoins or convert them into traditional currency such as U.S. dollars, according to the company. Cloudflare describes the gateway as infrastructure for small automated transactions, where agents may pay per request, token, API call or task outcome rather than through subscriptions, account signups or traditional checkout flows.

For technology leaders, that raises questions about whether existing payment, access and billing systems are ready for software that can buy digital resources one request at a time. Cloudflare argues that APIs and cloud services already use metered billing, but those systems usually assume a known buyer who has signed up, received an API key and accepted usage-based charges. The company says the Monetization Gateway is meant to support transactions where an agent can request a resource, receive a price, pay and get access without a signup, API key or prior relationship with the seller.

Customers would manage payment policies through the Cloudflare dashboard, API or Terraform. Cloudflare gives examples including paid access for specific API routes, variable pricing tied to task complexity and replacing some unauthorized responses with payment instructions instead of a simple denial.

The model still depends on adoption outside Cloudflare. Sellers would need to set prices and expose resources through x402, while agent developers and other buyers would need to recognize payment requests, accept the cost and return payment proof. Stablecoin settlement may also create policy, compliance and treasury questions for organizations that do not already handle digital asset payments.

Cloudflare has opened a waitlist for the Monetization Gateway but did not announce general availability timing, customer pricing or supported payment assets. For now, the gateway remains an early step toward payment infrastructure for software that can buy resources as it requests them.