Cloudflare published six announcements in a single day that, taken together, outline a complete infrastructure for agents. Kitesurf is a stateless browser running on V8 isolates in Workers, designed to let agents navigate without maintaining state between sessions. MCP v2 rewrites the protocol without sessions: each tool call is an independent HTTP request. WebMCP turns any website into an agent-readable interface, without writing new APIs. AI Search gives agents a search engine over your data. AEO measures how discoverable and recommendable your site is to AI assistants. And the post on the Agentic Internet introduces the concept of a «payable» site: agents as visitors with a human willing to pay on the other side.

For those scaling agents, the question stops being «which tool» and becomes «which architecture». Cloudflare is putting every piece of the agentic infrastructure on its edge: the browser, the protocol, search, site visibility. As we reported on August 5, the first step was security with temporary credentials and behavioral gateway. Now the model expands to the entire stack: the cloud organizes itself around agents as first-class visitors.

The point on AEO is concrete: more than half of requests now come from machines, not people. If your site isn’t readable by an agent, you lose a channel that’s growing.

If you want to try it: the WebMCP developer preview is open on the Cloudflare dashboard. The first step is to enable it on a test domain and see what an agent can read from your site.

In detail

Cloudflare’s thread with agents starts early in the week, when it put the agent runtime at the center of the cloud with @cloudflare/computer. On August 5, three announcements composed the security model: temporary credentials, behavioral gateway, spending cap. On August 6 the picture closes with the entire stack, from security through browser, protocol, and search.

Kitesurf: the agent browser.

Agents need to navigate the web, but normal browsers are built for humans: they render CSS, execute JavaScript, maintain state across tabs. Kitesurf flips the design: it runs on V8 isolates (the same runtime as Workers), is stateless, and costs a fraction of a traditional headless browser. For those building agents that need to read pages or fill forms, the point isn’t performance: each execution is a clean instance, with no cookies polluting the result and no sessions to manage.

MCP v2: stateless, finally.

The Model Context Protocol was born with persistent sessions: the server maintained state for each connected client. Scaling meant managing long connections, timeouts, reconnections. MCP v2 removes sessions from the server: one HTTP request, one response, done. Cloudflare rewrote it to run natively on Workers, and early adopters are already in production. It’s the same thread as the MCP 2.0 protocol that became standard on July 28: Cloudflare is the first platform to implement it natively on the edge.

WebMCP and AI Search: the site as API.

WebMCP transforms a site into an agent-readable interface with a toggle. No new APIs, no changes to origin. The human stays in control and the creator keeps their traffic. AI Search does the same thing on your data: point the engine at your files or site, and get a search that an agent can query. For those with internal knowledge bases, it’s Cloudflare’s version of managed RAG without primitives to stitch together.

AEO and the Agentic Internet: agent SEO.

The AEO post contains the most interesting data point: more than half of requests now come from machines. Cloudflare introduces two metrics: Agent Readiness (how well an agent can discover and read your site) and Answer Engine Optimization (how often AI assistants recommend you). It’s SEO adapting to a world where the visitor is an agent, not a person clicking AdSense.

The Agentic Internet post is the manifesto: agents don’t render CSS and don’t click banners, but they have a human willing to pay. Blocking them means blocking the customer. The x402 protocol, cited in the post, introduces the concept of a «payable» site: the agent can pay to access content or services, and the transaction happens natively over the HTTP protocol.

What remains open.

The six announcements are mostly developer preview or beta. Kitesurf and AI Search are closest to use, MCP v2 has early adopters in production but is a recent rewrite. AEO is a new metric: it takes time to understand whether it actually predicts visibility in AI assistants, or if it’s just another dashboard to watch. And the x402 model for payments is the most speculative of the bunch: elegant in concept, but without an ecosystem of publishers and agents adopting it, it remains theory.