Cloudflare Outlines Framework and Tools for an Open Agentic Internet

Cloudflare Outlines Framework and Tools for an Open Agentic Internet Cloudflare has introduced its vision for an 'Agentic Internet' designed to support autonomous AI agents acting on behalf of paying human users. The initiative centers on making the web readable, discoverable, callable, and payable using open standards to avoid centralized platform control. AI agents represent a new type of web visitor driven by paying users and specific goals rather than standard human browsing or simple bot scraping. Cloudflare relies on open protocols including Web Bot Auth, PACT, WebMCP, and x402 to handle identity, execution, and transactions without proprietary lock-in. The framework addresses four architectural layers: readable content, discoverability, direct tool invocation, and automated micropayments. Domain owners are given tools to differentiate between extractive scrapers and paying, resource-conscious agents. Identity and Open Standards Cloudflare advocates for an open ecosystem rather than walled gardens where a handful of platforms monopolize discovery and payments. To establish trust, Web Bot Auth cryptographically verifies bot identity, while Private Access Control Tokens (PACT)—developed alongside Mozilla, Google, Microsoft, and Shopify—allow sites to issue anonymous, vouched tokens so legitimate agents face less friction across the web. Readability and Discoverability To prevent agents from wasting bandwidth and context-window tokens on human interface elements, Cloudflare offers server-side Markdown for Agents alongside Kitesurf, a lean headless browser built for Cloudflare Workers. For discovery, AI Search enables agent-optimized queries, while Agent Engine Optimization (AEO) provides site operators with metrics on how visible their brands and content are to major AI models. Execution and Micropayments Instead of requiring agents to scrape and parse changing HTML DOMs, WebMCP and Code Mode expose direct tool contracts and endpoints that agents can execute using code while reusing session state. To replace broken advertising and seat-based pricing models, Cloudflare integrates tools like Wallets and the Monetization Gateway, allowing agents with preconfigured budgets to pay tiny fees or licensing costs per request via standards like x402.

Cloudflare 推动构建开放代理互联网：确立可读、可发现、可调用与可支付四大标准 Cloudflare 宣布致力于构建开放的“代理互联网”（Agentic Internet）。面对代表付费人类用户访问网络的 AI 代理，Cloudflare 基于开放标准推出一系列技术框架与工具，旨在解决代理网络在可读性、可发现性、可调用性及支付交易四个维度的基础设施需求，防止互联网沦为少数巨头垄断的封闭生态。 AI 代理已成为代表付费用户访问网络的新型访客，传统针对人类设计的广告和席位订阅模式面临失效。 代理互联网依赖开放协议与标准，涵盖 x402、MCP、Web Bot Auth 和 PACT 等跨厂商协作机制。 Cloudflare 围绕可读（Readable）、可发现（Discoverable）、可调用（Callable）与可支付（Payable）四大支柱发布多项工具与服务。 网站管理者可通过精细化控制区分善意与掠夺性代理，支持代理以微支付和 API 调用的形式对内容和服务付费。 代理互联网的兴起与网络生态挑战 大量网络流量来自重复抓取未变更页面的善意机器人，造成巨大算力浪费。现代 AI 代理不再渲染样式或点击广告，而是由付费用户驱使以完成特定任务。若简单将其当作恶意爬虫拦截，网站将直接失去真实客户。Cloudflare 认为，必须建立开放的基础设施让域名所有者与代理协作，避免少数技术堆栈垄断身份、发现和支付体系。 基于加密身份与开放标准的信任机制 代理互联网的基础在于确立身份。Web Bot Auth 让机器人能够向访问的网站进行加密身份认证；同时，Cloudflare 与 Mozilla、Google、Microsoft 和 Shopify 联合推出的私密访问控制令牌（PACT）使网站能够对合法代理进行匿名担保，降低访问摩擦。底层规范依托 x402、MCP 等开放标准，确保所有参与者均可自由实现，Cloudflare 自身亦作为普通客户运行在相同网络路径上。 四大基础支柱：从高效阅读到程序化调用 为提高代理交互效率，Cloudflare 从阅读、发现与调用层面提供了全套方案。在可读性方面，Markdown for Agents 减少带宽和上下文窗口浪费，轻量级浏览器 Kitesurf 专为代理运行设计；在可发现性方面，AI Search 和代理引擎优化（AEO）协助代理检索内容并帮助创作者衡量曝光度；在可调用性方面，WebMCP 允许代理直接调用网页原生工具，Code Mode 则让代理直接编写代码调用端点而非解析 HTML。 重构商业变现与微支付体系 代理不会产生人类的页面浏览量和广告展现，使传统依赖展示广告的商业模式难以为继。在代理互联网中，内容可按次结算微费，代理通过携带预算的钱包直接向商家付款。通过 Wallets 和 Monetization Gateway，域名所有者可快速配置收款，每笔交易均保留凭证，使食谱网站、本地新闻和数据提供商能够通过按次授权或超限付费实现可持续盈利。

Our data shows that a lot of traffic from well-behaved bots is [re-fetching pages that have not changed](https://blog.cloudflare.com/making-ai-search-smarter/). Billions of requests. An enormous amount of machine effort, attached to no outcome at all. That's the signature of a web built for humans being visited by something else. Agents are here - not as a new kind of software, but as a new kind of visitor to the web. The web reshaped around this new visitor is what we call the Agentic Internet. We see its future as readable, discoverable, callable, and payable. To realize that future, it needs its own tools and protocols. Cloudflare's developer platform gave agents a place to run, and the first tools to build them. What's missing are the ones that let agents and domain owners cooperate instead of collide — on the open Internet, not just inside a single platform. Every browser has always identified itself to the web with a header called User-Agent. The name only made sense once you realized the browser was acting on your behalf. Now a user agent is truly a user's agent: a program that fetches the web on a person's behalf. Today its most mature form is the coding agent that reads and writes code, pulls the docs it needs, and never sees the pages it reads. An agent doesn't render your CSS, see your hero image, or click your ads. But it has a paying human on the other end. Every request now costs someone money and carries a purpose. Block it and you block your customer. Treat it like a scraper and you lose them. Every agent runs because someone — a person or a business — is paying for what it does. Most people don't spend tokens for the sake of it. This version of the Internet, one with an outcome and a bill on the other end of every request, is going to look nothing like the one we have now. The web was not built for this, and neither were your analytics. Nor, in most cases, was your business model. How agents read, discover, call, and pay is going to decide whether the Internet stays open or gets closed. In one version of the future, a handful of stacks own discovery, identity, and payments, and everyone else routes through them. In another, the Internet stays open: primitives built on standards anyone can implement, running on rails that are neutral because the code is public. Cloudflare believes in the open Internet, and we're in a position to help build the future where it thrives. The specifications we build on are open standards that anyone can implement — x402, MCP, Web Bot Auth, PACT. Domain owners choose their own identity providers, their own payment processors, their own agent partners. Cloudflare is one option, not the whole stack. We are Customer Zero of the same rails our customers use, with no privileged path or early-access API that only we can reach. This is the job we've done for the human web for fifteen years, and it's the job we intend to do for the Agentic Internet. The engineering is not what humans on the Agentic Internet will notice. They're picking up a new medium, and they'll judge it the way they judged the web: on whether it's better. Whether finding and booking a table takes one exchange instead of nine. Whether they know who they're dealing with. Whether paying feels safe. This starts with identity. [Web Bot Auth](https://blog.cloudflare.com/web-bot-auth/) lets a bot cryptographically identify itself to any site it visits, so publishers can decide who they welcome and who they don't. No more guessing and no more spoofed user agents. Many sites already know the human behind a request from login, in-app behavior, or purchase history. That site can issue [Private Access Control Tokens](https://cloudflare.net/news/news-details/2026/Cloudflare-Collaborates-With-Leading-Browsers-to-Develop-a-Privacy-First-Protocol-For-the-Global-Internet/default.aspx) (PACT). Announced with Mozilla, Google, Microsoft, and Shopify, PACT lets sites vouch anonymously, so the agent can present the token elsewhere. Legitimate agents get in with less friction. We can then make it easier for an agent to do its job. [Markdown for Agents](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/) lets agents read websites with fewer tokens and less bandwidth. [WebMCP](https://blog.cloudflare.com/webmcp/) gives them a native way to interact on your behalf. Standards like [x402](https://x402.org/) let them pay merchants directly. **Readable** is straightforward. Can AI agents read content in a way that is native to them and plays to their strengths? The less bandwidth and fewer tokens an agent burns, the better. Every HTML tag rendered for a human that never looks at it is not only a waste of compute but also a pollution of the context window the agent then has to pay to ignore. [Markdown for Agents](https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/) addresses this from the server side. On the client side, we approached building a browser with agents in mind as first-class citizens. [Kitesurf](http://blog.cloudflare.com/kitesurf) is our new browser lean enough to run on Workers, spun up per request and thrown away after. It delivers content and features that agents need without any of the bloat from human-oriented features in traditional browsers. **Discoverable** is where every economic moment on the Agentic Internet begins. Before an agent can read a resource, call a tool, or pay for a transaction, it has to know the resource is there. Search is one half of the story, as agents need to find what they need through interfaces built for them, not through a keyword box designed for a human who types slowly and skims. [AI Search](https://developers.cloudflare.com/ai-search/) is available today, so any public site can be made searchable by agents. Being discovered is the other part. Content creators and API owners need to know how visible they are to agents. [Agent Engine Optimization (AEO)](http://blog.cloudflare.com/aeo) measures brand visibility across the models and agents that matter. If you are not measurably visible to the agents your customers use, then you are effectively offline for them. **Callable** is where the agents start doing things: booking a table, renewing a subscription, pulling a report. On the human web these all look different, because they were built for humans clicking through user interfaces. An agent trying to add an item to a to-do list has to parse the HTML, guess which button is “Add”, synthesize a click, and hope the DOM didn’t change since it last looked. [WebMCP](https://blog.cloudflare.com/webmcp/) lets a site expose its actions directly to agents through the browser: The tool “contract” becomes explicit. No HTML parsing, no guessing at form fields. As the tools run inside the page, they reuse the user’s existing session and state. [Code Mode](https://blog.cloudflare.com/code-mode/) goes one step further. Agents think in code, and calling tools by writing code is faster and more accurate than prose. As agents are calling endpoints rather than scraping webpages, there is a clear signal back to the content owner of what content is actually being used. **Payable** is where we believe the Agentic Internet is going. Every economic transaction eventually needs a way to pay. Ad-based models are breaking. Seat-based models do not work when the user is a program. The publishers we all rely on cannot fund themselves on pageviews that never happen and browsers that do not render their ads. A recipe site that never turned a profit using ads can charge a fraction of a cent per fetch and be profitable at the scale of the Agentic Internet. A local paper can license articles at read time without a licensing deal or login. On the other side, the agent shows up with a wallet and a budget the human set once. Every paid interaction leaves a receipt. The publisher can prove which agent fetched which page. The agent can prove it paid for what it used. [Wallets](https://blog.cloudflare.com/wallets/) allow agents to easily pay for content and APIs. [Monetization Gateway](https://blog.cloudflare.com/monetization-gateway/) lets domain owners set up payments from agents in a few clicks. Cloudflare sits in the middle of all of this by design. We already sit between billions of humans and the sites they visit, protecting them, speeding them up, keeping them online. Agents change the traffic but not the shape of that job — we're the neutral, high-performance layer that publishers, merchants, agent builders, and end users can all trust to be on their side, not competing with them. We want to give domain owners the tools to empower the kinds of AI agents that they want to support and [block the ones that they don’t](https://blog.cloudflare.com/cloudflare-ai-audit-control-ai-content-crawlers/). A developer tool likely wants to become [agent-ready](http://blog.cloudflare.com/aeo) to encourage AI agents to discover, recommend, and pay them. A publisher may want to block extractive AI agents (which consume resources without giving anything back) but allow AI agents that license their content or compensate them. A nonprofit data provider may want to block bots or humans who exceed their rate limits, but allow them to pay to get unblocked and use those funds to cover the excess resource consumption. The distinction between a [bot and a human isn’t so simple anymore](https://blog.cloudflare.com/past-bots-and-humans/). It’s not as straightforward as bots are bad and humans are good, or bots wasting resources that humans should instead consume. This is the old way of thinking that is outdated in the world of agents. We see agents as a new type of actor. Their actions can be desirable, say, by reading content in a way that preserves resources, interacting with websites in the way that the domain owners specify, and paying for what they use. Or their actions can be undesirable, for example, by scraping millions of pages without compensation, attempting to circumvent blocks, or ignoring [robots.txt](https://www.cloudflare.com/learning/bots/what-is-robots-txt/). We believe that many of the undesirable actions will diminish, and even convert to desirable actions, if humans and bots are given the right tools. Cloudflare has spent years detecting bots, allowing domain owners to take control of whether bots can access them. What's been missing is the other half: how agents interact with those sites once they're let in. That's what this suite of agentic tools is for: making the web readable, discoverable, callable, payable. These four primitives are all built on open standards, so no single company owns the rails. An open Agentic Internet needs diversity on both sides. Not just diverse publishers and content creators but also diverse agents. If the demand side converges, it doesn’t matter how open the supply side is. The Internet will still be a walled garden. We are building this open alternative. Join us by getting your site [agent ready with our new dashboard](http://blog.cloudflare.com/aeo), and sign up to receive news on our Answer Engine Optimization product. If you run a site or an agent, you can experiment with all of the Internet's new technologies using our [AI Playground](https://playground.ai.cloudflare.com/).