CloudflareJack GalileeAnnouncement
Building an open Agentic Internet: readable, discoverable, callable, and payable
Summary
The modern web produces billions of bot requests that repeatedly fetch unchanged pages, highlighting an architecture fundamentally misaligned with automated visitors acting on behalf of paying users. Cloudflare outlines an open Agentic Internet structured around four foundational capabilities: readability, discoverability, callability, and payability. Identity and access rely on open specifications such as Web Bot Auth and Private Access Control Tokens, while Markdown for Agents and the Kitesurf browser reduce token overhead and context window bloat. For execution and monetization, WebMCP exposes structured tools directly through the browser, and protocols like x402 paired with Monetization Gateway enable per-fetch transactions. These open standards allow domain owners to define tool contracts, verify bot identities, and monetize agent traffic without relying on legacy advertising models.
Context
Traditional web architecture, analytics, and monetization models are built for humans rendering visual interfaces and viewing ads, causing automated agents to waste compute by re-fetching unchanged content, parsing raw DOM elements, and polluting context windows with unrendered HTML tags.
Approach / What changed
Cloudflare outlines an open Agentic Internet framework based on open standards (x402, MCP, Web Bot Auth, PACT). The architecture makes sites readable via Markdown for Agents and the Kitesurf browser, discoverable via AI Search and Agent Engine Optimization, callable via WebMCP tool registration, and payable via Monetization Gateway and agent wallets.
Takeaways
WebMCP allows websites to register explicit tool contracts directly via document.modelContext.registerTool, eliminating the need for agents to parse HTML DOM structures or synthesize clicks.
Web Bot Auth provides cryptographic bot identity verification, while Private Access Control Tokens (PACT) enable anonymous third-party vouching across participating platforms.
The Kitesurf browser executes on Cloudflare Workers on a per-request basis and is discarded immediately after, removing human-oriented browser bloat to optimize agent performance.
Source and freshness
- Source
- blog.cloudflare.com
- Published
- Added to Yomu
- Last updated
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.