Building an open Agentic Internet: readable, discoverable, callable, and payable

The event marks a structural change in web traffic. Agents are not browsers or scrapers but economically motivated visitors with distinct needs: they don’t render CSS, click ads, or tolerate human-scale latency. Their requests carry direct costs for both the agent operator and the domain owner, creating a financial incentive to optimize interactions. This shifts the engineering focus from page-load performance to token efficiency, bandwidth reduction, and outcome-driven requests. The web’s existing caching, analytics, and monetization models were not designed for this, so engineers must now distinguish between human and agent traffic to avoid misallocating resources or blocking revenue.

Cloudflare’s proposed protocols address the gaps between agent capabilities and web infrastructure. Web Bot Auth provides cryptographic identity, letting domain owners whitelist or block agents without guessing from user-agent strings. Private Access Control Tokens (PACT) extend this by letting sites vouch for agents anonymously, reducing friction for legitimate use cases. On the content side, Markdown for Agents strips human-oriented markup, reducing bandwidth and token costs. These standards are open, meaning domain owners can implement them without relying on Cloudflare’s stack. However, adoption requires coordination: agents must support the protocols, and domain owners must update their servers to serve agent-optimized content.

The economic model of the web changes when every request has a bill attached. Agents run because someone pays for their tokens, so their behavior is outcome-driven. This creates pressure to eliminate wasteful re-fetches of unchanged content, which Cloudflare’s data shows is a major inefficiency. The proposed payment standard (x402) lets agents pay merchants directly, bypassing human-scale checkout flows. For engineers, this means integrating payment rails into APIs and content delivery, not just frontend interfaces. The risk is fragmentation: if open standards fail, a few platforms could dominate agent discovery, identity, and payments, closing the web for everyone else.

The technical trade-offs are clear. Serving agent-optimized content (e.g., Markdown) reduces costs but requires maintaining parallel representations of the same data. Identity protocols like Web Bot Auth add security but introduce complexity in managing cryptographic keys and access policies. Payment integration (x402) enables new monetization paths but demands compliance with financial regulations. Cloudflare’s approach avoids vendor lock-in by making its tools one option among many, but this also means the success of the Agentic Internet depends on widespread adoption of the standards. Engineers must weigh the cost of early adoption against the risk of being left behind as agents become a larger share of web traffic.