--- title: Cloudflare brings paid access to MCP tools — who... description: Cloudflare opened a closed beta of its Monetization Gateway, letting domain owners charge AI agents for APIs, MCP tools, websites, and datasets using the x402... canonical: https://daily.dev/posts/cloudflare-brings-paid-access-to-mcp-tools-who-controls-the-agent-s-spending--ahhn1cm31 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Cloudflare brings paid access to MCP tools — who controls the agent’s spending? | daily.dev og:description: Cloudflare opened a closed beta of its Monetization Gateway, letting domain owners charge AI agents for APIs, MCP tools, websites, and datasets using the x402... og:url: https://daily.dev/posts/cloudflare-brings-paid-access-to-mcp-tools-who-controls-the-agent-s-spending--ahhn1cm31 og:image: https://api.daily.dev/og/posts/aHhn1Cm31.png og:image:alt: Cloudflare brings paid access to MCP tools — who controls the agent’s spending? og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Cloudflare brings paid access to MCP tools — who controls the agent’s spending? **[The New Stack](https://daily.dev/sources/newstack)** · 6 min read · 0 upvotes · 0 comments ## Summary Cloudflare opened a closed beta of its Monetization Gateway, letting domain owners charge AI agents for APIs, MCP tools, websites, and datasets using the x402 protocol, with payment settling in USDC on the Base blockchain. The beta is limited to eligible U.S. sellers and buyers. Cloudflare's planned Virtual Wallets let owners set allowances, allowlists, and transaction caps, and the Agents SDK's withX402Client wrapper supports a confirmation callback before payment. The piece walks through unresolved developer problems: per-call caps don't bound total task spend, variable pricing (the upto scheme) means agents know only a ceiling not a final charge, failed or timed-out paid requests risk double-charging on retry, price now factors into tool selection alongside latency and reliability, and sellers' transaction logs won't give buyers the telemetry needed to trace spend across tool calls, retries, and model inference drawing from the same wallet. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is Cloudflare's Monetization Gateway and how does it let sellers charge AI agents for MCP tools? Cloudflare's Monetization Gateway, opened in closed beta, lets domain owners charge AI agents for access to APIs, MCP tools, websites, and datasets. It carries payment authorization inside the HTTP request using the x402 protocol and releases the resource only after payment settles in USDC on the Base blockchain. The beta is limited to eligible U.S. sellers and buyers, and Cloudflare's own AI Gateway already uses it to charge for inference per request. _Teams weighing paid MCP tools can follow how agent payment infrastructure evolves on daily.dev._ ### How does x402's upto pricing scheme work for variable-cost agent tool calls? Under x402's upto scheme, the client authorizes a ceiling price and the seller's origin reports the actual charge after the job completes, which suits variable-cost work like PDF generation where compute and bandwidth vary per request. This differs from the exact scheme used for fixed-price requests. The safer assumption for budgeting is that each call consumes its full authorized ceiling until settlement reports the real amount. _Developers budgeting agent spend under variable pricing can track these cost-control patterns on daily.dev._ ### Why can retrying a failed paid agent tool call result in paying twice? A paid request can fail before authorization, during settlement, or after payment succeeds but before the response reaches the client; retrying in that last case risks paying twice for the same resource. Cloudflare's gateway handles failed transactions needing another attempt, but the agent framework still needs its own payment record to distinguish a failed purchase, a lost response after successful payment, and a genuinely new transaction. _Engineers building retry logic for paid agent calls can track these payment-tracing patterns on daily.dev._ ## Similar posts on daily.dev - [Announcing the Monetization Gateway: charge for any resource behind Cloudflare via x402](https://daily.dev/posts/announcing-the-monetization-gateway-charge-for-any-resource-behind-cloudflare-via-x402-aylb3tuzy) · Cloudflare · 1 upvotes · 0 comments - [AI agents are learning to spend money. Who will handle the payments?](https://daily.dev/posts/ai-agents-are-learning-to-spend-money-who-will-handle-the-payments--oahxtfqem) · The Next Web · 0 upvotes · 0 comments - [Cloudflare and AWS Embed x402 Agent Payments at the Edge](https://daily.dev/posts/cloudflare-and-aws-embed-x402-agent-payments-at-the-edge-vmwjvbzct) · InfoQ · 0 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#mcp](https://daily.dev/tags/mcp), [#cloudflare](https://daily.dev/tags/cloudflare) [View this post on daily.dev](https://daily.dev/posts/cloudflare-brings-paid-access-to-mcp-tools-who-controls-the-agent-s-spending--ahhn1cm31) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Cloudflare brings paid access to MCP tools — who controls the agent’s spending?","url":"https://daily.dev/posts/cloudflare-brings-paid-access-to-mcp-tools-who-controls-the-agent-s-spending--ahhn1cm31","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/cloudflare-brings-paid-access-to-mcp-tools-who-controls-the-agent-s-spending--ahhn1cm31"},"datePublished":"2026-10-01T20:11:55.317Z","dateModified":"2026-10-01T20:21:11.292Z","description":"Cloudflare opened a closed beta of its Monetization Gateway, letting domain owners charge AI agents for APIs, MCP tools, websites, and datasets using the x402...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a5a90f7a95c748da830a17021c6f2250?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a5a90f7a95c748da830a17021c6f2250?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"The New Stack","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"The New Stack","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/newstack","url":"https://daily.dev/sources/newstack"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/cloudflare-brings-paid-access-to-mcp-tools-who-controls-the-agent-s-spending--ahhn1cm31","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,mcp,cloudflare","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"The New Stack","item":"https://daily.dev/sources/newstack"},{"@type":"ListItem","position":3,"name":"Cloudflare brings paid access to MCP tools — who controls the agent’s spending?"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/cloudflare-brings-paid-access-to-mcp-tools-who-controls-the-agent-s-spending--ahhn1cm31#faq","mainEntity":[{"@type":"Question","name":"What is Cloudflare's Monetization Gateway and how does it let sellers charge AI agents for MCP tools?","acceptedAnswer":{"@type":"Answer","text":"Cloudflare's Monetization Gateway, opened in closed beta, lets domain owners charge AI agents for access to APIs, MCP tools, websites, and datasets. It carries payment authorization inside the HTTP request using the x402 protocol and releases the resource only after payment settles in USDC on the Base blockchain. The beta is limited to eligible U.S. sellers and buyers, and Cloudflare's own AI Gateway already uses it to charge for inference per request. Teams weighing paid MCP tools can follow how agent payment infrastructure evolves on daily.dev."}},{"@type":"Question","name":"How does x402's upto pricing scheme work for variable-cost agent tool calls?","acceptedAnswer":{"@type":"Answer","text":"Under x402's upto scheme, the client authorizes a ceiling price and the seller's origin reports the actual charge after the job completes, which suits variable-cost work like PDF generation where compute and bandwidth vary per request. This differs from the exact scheme used for fixed-price requests. The safer assumption for budgeting is that each call consumes its full authorized ceiling until settlement reports the real amount. Developers budgeting agent spend under variable pricing can track these cost-control patterns on daily.dev."}},{"@type":"Question","name":"Why can retrying a failed paid agent tool call result in paying twice?","acceptedAnswer":{"@type":"Answer","text":"A paid request can fail before authorization, during settlement, or after payment succeeds but before the response reaches the client; retrying in that last case risks paying twice for the same resource. Cloudflare's gateway handles failed transactions needing another attempt, but the agent framework still needs its own payment record to distinguish a failed purchase, a lost response after successful payment, and a genuinely new transaction. Engineers building retry logic for paid agent calls can track these payment-tracing patterns on daily.dev."}}]} ```