How to control agent spending with Cloudflare’s payment gateway

The closed U.S. beta handles payments for tool access. Developers still need to control spending authorization, reserve variable charges and track spending for each task.

The closed U.S. beta handles payments for tool access. Developers still need to control spending authorization, reserve variable charges and track spending for each task.
Cloudflare has opened a closed beta of Monetization Gateway, letting domain owners charge superintelligence (SI) agents for access to software interfaces, tools, websites and datasets, according to The New Stack’s October 1 report. Access is limited to eligible U.S. sellers and buyers. The gateway handles payment, but developers still need controls over how much an agent can spend on an entire task.
The reported payment flow uses x402, a protocol that carries payment authorization inside an HTTP request—the message a client sends to a server. A client requesting a paid tool without payment receives HTTP 402, a payment-required response, and can retry with proof of payment. The gateway releases the resource only after payment settles in USDC, a digital currency, on the Base blockchain.
Analysis
According to the report, Cloudflare supports x402’s exact scheme for fixed-price requests and upto for variable prices. With variable pricing, the client authorizes a maximum charge, and the seller’s server reports the actual amount. Launch customer API2PDF uses this approach because PDF jobs consume different amounts of computing resources and bandwidth. The agent knows the ceiling, not the final bill, before the job runs.
The New Stack recommends treating the full authorized ceiling as spent until settlement reports the actual charge. In budget terms, that means reserving the maximum rather than treating those funds as available for another call. The runtime must check both the next call’s permitted cost and the task’s remaining budget.
Analysis
A timeout does not necessarily mean a purchase failed. A paid request can fail before authorization, during settlement, or after payment succeeds but before the response reaches the client. In the last case, repeating the request could pay twice for the same resource.
The report says Cloudflare handles payment processing inside the gateway, including failed transactions that need another attempt, while x402 clients check the HTTP status and response before retrying. The agent framework still needs its own payment records to distinguish a failed purchase, a settled payment with a lost response and a new transaction. Two attempts are not necessarily two purchases—but they can be.
Buyer-side telemetry—records of the application’s activity—must connect payments to the tool calls and tasks that triggered them. A wallet balance alone cannot explain which task spent the money or whether a retry caused a duplicate payment. The report also says Cloudflare’s AI Gateway already accepts x402 payments for inference, the process of running a model to produce an output. Model requests and paid tools can therefore draw from the same wallet, and developers need to account for both against the task budget.
Cloudflare says it plans transaction logs for Monetization Gateway, but those logs are aimed at sellers. Developers buying tools will still need their own records to explain each task’s spending and decide whether another paid attempt is safe.

The feature names Tastemade, Court TV and The Young Turks, but gives conflicting dates, leaving the removal’s status unclear.
1 min

The streaming model returns draft text while a person is still speaking, letting apps start processing requests earlier. Microsoft says response speed depends on the network and the system generating a reply.

Activision says server culling will cover every launch multiplayer map, with Combat Outpost and Warzone also in its plans.
2 min