{
  "id": 11269698,
  "title": "Cloudflare brings paid access to MCP tools — who controls the agent’s spending?",
  "url": "https://urgent.news/2026/10/01/cloudflare-brings-paid-access-to-mcp-tools-who-controls-the-agents",
  "topic": "ai",
  "section": "AI",
  "published": "2026-10-01T20:09:20.000Z",
  "source": {
    "name": "The New Stack",
    "slug": "the-new-stack",
    "url": "https://thenewstack.io/cloudflare-x402-agent-spending/"
  },
  "original_language": "en",
  "account": "Cloudflare has launched a closed beta of its Monetization Gateway, allowing domain owners to charge AI agents for accessing APIs, MCP tools, websites, and datasets. The gateway embeds payment authorization within HTTP requests using the x402 protocol and only releases the requested resource after payment is settled in USDC on the Base blockchain. The beta is restricted to eligible U.S. sellers and buyers, with Cloudflare's own AI Gateway already utilizing it to charge for inference per request.\n\nFor developers of AI agents, a paid tool call introduces an additional decision in the execution loop, as the runtime must first determine whether the agent has authorization to spend before proceeding. Spending authority should ideally reside outside the model, and Cloudflare's Virtual Wallets aim to achieve this by enabling owners of Account Wallets to set allowances, allowlists, and maximum transaction sizes that apply regardless of which tool the agent decides to call.\n\nOn the client side, the Agents SDK's withX402Client wrapper includes a confirmation callback that receives payment requirements before any money is moved. Passing null as the callback allows the agent to pay automatically. This mechanism also enables teams to require approval before a paid call is executed, similar to MCP's elicitation feature that pauses a tool call and seeks user intervention. Budgets beyond per-call caps may not offer sufficient protection, as an agent limited to $0.10 per call could still spend $10 over the course of a lengthy research or coding task without triggering a budget limit. Developers can impose task-level spending caps using Virtual Wallets, but the platform itself does not dictate the maximum amount a single task can spend.\n\nVariable pricing adds complexity to budget management, as the price may change between authorization and settlement. Cloudflare supports both fixed-price requests and variable pricing through the upto option, where clients authorize a ceiling, and sellers report the actual charge. TrueFoundry's TrueForge AI Gateway allows teams to enforce budgets and rate limits across agents, and variable pricing necessitates tracking two boundaries: the maximum cost of an individual tool call and the remaining task budget after each paid call.",
  "summary": "Cloudflare opened a closed beta of its Monetization Gateway on Wednesday, giving domain owners a way to charge AI agents The post Cloudflare brings paid access to MCP tools — who controls the agent’s spending? appeared first on The New Stack .",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}