Cloudflare is testing a checkout built for agents

Its Monetization Gateway beta uses HTTP 402 so software can pay for a request inside the request itself.

Four-step diagram showing an AI agent receiving an HTTP 402 price and paying before an API response
Visual · AIpreneur editorial graphic

The checkout was designed for a person

Most paid APIs assume a human has already opened an account, entered a card, selected a plan and stored an API key. An autonomous agent that discovers a useful endpoint in the middle of a task cannot complete that journey on its own. The service may be available, but the commercial path blocks the buyer.

Cloudflare’s Monetization Gateway beta moves the transaction into the request. A service can answer with HTTP status 402 and a price. The agent pays and retries the request with proof, then receives the response. Cloudflare says the beta uses USDC on Base through Coinbase’s x402 protocol.

A direct test of machine demand

Cloudflare cites API2PDF, which said more than half of prospective users abandoned its conventional credit-card flow after a free month. With the gateway, a buyer can reach a paid response without first managing an account or permanent credential. That reduces steps, although the beta has not yet established how conversion, fraud or support behave at scale.

The current scope is narrow. Cloudflare launched a closed beta for U.S.-based sellers, and the announcement does not publish a platform fee. The settlement method also introduces operational and regulatory questions that sellers will need to assess for their own jurisdiction.

What becomes sellable

Request-level payment could suit data lookups, document conversion, specialised search, verification and other atomic services. A seller no longer has to persuade every customer to buy a monthly bundle before proving usefulness. Price can sit next to the individual outcome.

For builders, the immediate task is to identify a bounded response that is worth paying for on demand. The payment rail is only part of the product. Quality, latency, repeatability and clear usage rights still determine whether an agent should buy the next request.

A machine customer needs a purchase path it can complete without creating an account or reaching for a card.

Sources and review

Developed from an approved AIpreneur post and reviewed against the cited sources on 4 October 2026.

The question behind every AIpreneur piece: why does this matter to someone building, creating or contributing to the AI economy?

← Back to News

Keep exploring