AI agents are your new customers! Cloudflare's vision for an open, next-generation web that's readable, discoverable, callable, and payable

Hi, it's Shii! Today I want to share something a bit different from Cloudflare's usual feature announcements. It's a post about how the internet and AI agents should work together going forward, Cloudflare's own big-picture vision. It looks like several related announcements came out the same day too, things like AI Search, AEO, the Kitesurf browser, and WebMCP, but the piece I'm covering here is the philosophy that ties all of it together. Let's dive in!

Cloudflare Blog blog.cloudflare.com

What was announced?

Cloudflare published a post on its blog titled "Building an open Agentic Internet." As the title says, it lays out Cloudflare's approach to building the infrastructure and standards needed for a web where AI agents are just as common as human visitors.

The piece is built around four pillars:

• Readable — agents can efficiently understand your content
• Discoverable — agents can find your site in the first place
• Callable — agents can directly invoke your site's functionality
• Payable — usage through agents can actually be paid for

Cloudflare's stance is that agents are a fundamentally new kind of visitor, different from humans, and that instead of publishers and agents colliding, Cloudflare wants to build open tools and protocols that let them cooperate.

Why it matters

The line that really stood out to me in the article was this one:

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.

The point is that if you treat agents as nuisance traffic to be blocked outright, you end up losing the actual paying customer behind them. The article also notes that treating an agent like a scraper means losing that customer entirely.

On top of that, the article points to data showing that a lot of traffic from well-behaved bots is just re-fetching pages that haven't changed, and that this happens at a scale of billions of requests, wasted effort with no upside for either the site or the agent. That's the starting problem this whole piece is responding to.

What changes

What this article offers isn't a single new feature, it's more of a map for what the agent-era web should look like. Each of the four pillars is tied to technology Cloudflare already offers or plans to offer, giving site owners a framework to work from as they figure out how to support agents.

Dive Deep

Here's a closer look at each of the four pillars.

• Readable: To help agents understand content using fewer tokens and less bandwidth, Cloudflare offers "Markdown for Agents," which formats sites in a machine-friendly way. The article also mentions "Kitesurf," a lightweight browser that runs on Workers, built to strip away human-oriented visual bloat so agents can efficiently pull just the information they need.
• Discoverable: The article argues that agents need agent-native search interfaces rather than a plain keyword search box, and introduces "AI Search" for making public sites discoverable by agents. It also mentions "Agent Engine Optimization (AEO)," which measures how visible a brand is to agents, with a pretty striking line: "if you are not measurably visible to the agents your customers use, then you are effectively offline."
• Callable: Instead of agents having to parse HTML, "WebMCP" lets them call a site's functionality directly through explicit tool contracts, and "Code Mode" lets agents call tools by writing code instead of prose. The article includes sample code for something like adding a to-do item, showing what an explicit tool definition looks like.
• Payable: The article argues that ad-based models don't work well for agent traffic, and that seat-based pricing doesn't make sense when the user is a program. It offers an example: "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." Supporting this are "Web Bot Auth," which lets bots cryptographically identify themselves, "PACT" (Private Access Control Tokens), which lets sites vouch for legitimate agents anonymously, "x402," an open standard for agents to pay merchants directly, "Wallets" for handling payments, and "Monetization Gateway" for site owners to quickly set up agent-facing payments.

These are all tools Cloudflare already provides in some form; since this particular post is the philosophy piece tying them together, it doesn't go into detailed specs for each one. The article closes by noting that site owners can make their sites "agent-ready" from the dashboard, and developers can experiment with these ideas in the AI Playground.

Wrap-up

• Treats AI agents as a new kind of visitor, aiming for cooperation over blocking
• Organizes agent support around four pillars: Readable, Discoverable, Callable, and Payable
• Introduces micropayment tooling (x402, Wallets, Monetization Gateway) for an ad-model-resistant agent era
• Site owners can go "agent-ready" from the dashboard, and developers can experiment in the AI Playground

Shii thinks this is especially worth reading if you're a site owner wondering how to handle growing AI agent traffic, or a developer building products for agents!