Cloudflare launched a closed beta of its Monetization Gateway on Wednesday, allowing domain owners to charge AI agents for access to APIs, MCP tools, websites, and datasets. The gateway embeds payment authorization directly inside HTTP requests using the x402 protocol and only releases resources after payment settles in USDC on the Base blockchain. The beta is currently limited to eligible U.S. sellers and buyers, with Cloudflare's own AI Gateway already using the system to charge for inference on a per-request basis.
The gateway supports prices ranging from $0.001 to $100 per transaction, according to the company. Cloudflare offers two pricing schemes: an exact scheme for fixed-price requests and an "upto" model for variable pricing, where the client authorizes a maximum amount and the seller's origin reports the actual charge after the job completes. Launch customer API2PDF uses the variable pricing model because each PDF job consumes different amounts of compute and bandwidth, meaning the agent knows the ceiling for what a request could cost but not the final figure. For agent developers, a paid tool call introduces another decision point in the execution loop because the runtime must determine whether the agent has permission to spend before it can proceed.
Cloudflare's planned Virtual Wallets allow the owner of an Account Wallet to set an allowance, an allowlist, and a maximum transaction size that apply regardless of which tool the agent decides to call, placing spending authorization outside the model itself. On the client side, the Agents SDK's withX402Client wrapper accepts a confirmation callback that receives the payment requirements before any money moves, and passing null in its place lets the agent pay automatically. The company says it will make sellers' services discoverable to agents, which would allow agents to find paid tools while a workflow is already running, with the runtime then deciding whether to approve the seller and how much the agent can spend. Cloudflare's Agents SDK lets MCP servers mix free and paid tools through paidTool, with developers setting a per-call price in USD, and a client that chooses a paid tool without payment gets a 402 status code and can retry through x402 with proof of payment.
The system creates new tracking challenges for agent developers because per-transaction limits alone don't prevent runaway spending during long tasks—an agent capped at $0.10 per call could still spend $10 during extended research or coding work without breaking the rule. Variable pricing complicates budgets further because the runtime must track both what an individual tool call is allowed to cost and how much of the task budget remains when the next paid call arrives, and under variable pricing, the safer assumption is that each call consumes its full authorized ceiling until settlement reports the actual amount. Once a request can trigger settlement, the runtime also has to know what happened to the transaction before deciding whether another attempt is safe, since a paid request might fail before authorization, during settlement, or after payment has gone through but before the response reaches the client—meaning retrying the request could mean paying twice for the same resource. Cloudflare says it plans to expose logs for Monetization Gateway transactions, but those logs are aimed at sellers, so developers buying paid tools will still need their own telemetry to connect payments with the model and tool calls that triggered them. The company's AI Gateway now accepts x402 payments for inference, allowing model calls and paid tools to draw from the same wallet, and developers will need to track both against the task that spent the money. As payments become a standard part of agent workflows, teams will need to decide whether the flexibility of autonomous tool purchasing justifies the overhead of budget enforcement and transaction auditing at every step of execution.