Cloudflare Opens Per-Request Payments for AI Agents

On September 30, Cloudflare opened a closed beta for its Monetization Gateway. The service lets AI agents pay for web pages, APIs, datasets and agent-callable tools as they use them. The company says four use cases are already in production, including Cloudflare’s own AI Gateway, search startup Ceramic.ai, Stocktwits and API2PDF.

The gateway makes a purchase part of the request itself. A seller sets a price and rules for which requests require payment. When an agent asks for a paid resource, it receives a 402 payment response with the payment terms, authorizes a payment and retries. There’s no separate checkout page. Cloudflare says payments currently settle in USDC on Base, and the closed beta is limited to eligible U.S.-based buyers and sellers.

Cloudflare first announced the Gateway as a waitlist in July. The September release is the useful change for marketers. Cloudflare says customers have production use cases, while the developer docs confirm the service remains in closed beta.

The shift matters most for software and data companies whose products can answer a single question or complete a small task. A monthly plan asks the buyer to choose a vendor before they know how much they’ll use it. An agent can request one search, one market signal or one PDF, then decide whether the result helps with its larger task.

Cloudflare CEO Matthew Prince made the ad challenge clear in a recent Decoder interview with The Verge. He said, “Bots don’t click on ads.” If agents become a meaningful audience for data and software, the product and payment model will shape how companies reach them.

The four examples show different versions of the same opening. Cloudflare’s AI Gateway lets U.S. customers pay for inference on selected models at request time. Ceramic.ai lets an agent pay for an individual search without an API key. Stocktwits created a separate path for agents to buy a market signal per request. It kept its existing API and enterprise licensing in place, according to Cloudflare’s launch report. Those examples suggest agent payments can sit beside a company’s current plans.

Stocktwits CEO Howard Lindzon described the change in Cloudflare’s announcement: “An agent can ask for exactly what it needs, when it needs it.” That creates a direct product-marketing question. Companies will need to decide which parts of their product can be sold as a single useful result. They also need to explain the price to software and set limits on each transaction.

API2PDF offers the clearest onboarding example. The document-generation service now accepts x402 payments through Cloudflare’s Gateway, so an agent can request a file without an account or API key, according to API2PDF’s documentation. Its docs say each request costs the measured compute and bandwidth, rounded up to the nearest cent, with a disclosed maximum of five cents. Cloudflare says API2PDF saw more than 50% conversion drop-off after it began requiring a credit card after a user’s first month. That figure comes from Cloudflare’s customer account. Neither company has published the underlying sample, timeframe or a post-launch conversion result.

That gap matters. The launch shows a payment path exists and that four named products are using it. It doesn’t show how many agents are paying, how much revenue sellers are earning, or whether small transactions cover the costs of attracting and supporting those buyers. Cloudflare’s own release separates this request-based Gateway from Pay Per Use for content that can be fetched once and reused many times. One billing model won’t fit every product.

The practical move for a B2B marketing team is to map one task its product can complete. Then define the smallest result an agent could buy on its own. Price, access rules and spending limits need to be clear at the request level. The response format matters too. Our earlier look at agents getting stuck on B2B pricing pages covered the discovery problem. Cloudflare’s beta adds a possible transaction step after discovery. For publishers and data businesses, the agent-ready web has its own monetization tradeoffs.

The right next move is a small product and pricing test. Start with one request a customer can price and explain clearly. If the task is repeatable and its value can be priced per use, make the request flow legible to a machine. Most buyers can’t access this beta yet.