{
  "id": "p_DVKj9xIPPUua9HiZ",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_DVKj9xIPPUua9HiZ",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apisio"
  },
  "body": "Picture the last time you watched an agent try to read a live page. You asked it for something current, and it did what Cloudflare describes in its own launch post: it \"usually just guesses the URL of the page and then makes a tool call to curl it.\" The guess was wrong, the fetch came back 404, and you were left reading a log of a machine knocking on doors that were never there.\n\nCloudflare's answer is the one a person would use: search first. In Introducing Web Search API via AI Gateway, the company is launching web search through AI Gateway with three partners, Ceramic.ai, Exa and Linkup. What comes back is \"fresh, structured snippets from the web injected straight into context.\" So instead of your agent guessing a URL, it asks a search provider and gets pages it can actually use.\n\nNow think about what you are buying when your agent does that. This is the part of the post worth slowing down for. Cloudflare attaches conditions to its partners. Each partner's crawler \"must comply with Cloudflare's publicly stated requirements for 'Verified bots',\" and every web search response \"must include a link to the location of crawled content.\" The post offers no usage figures, so you cannot tell from it how many agents are doing this yet. What it does give you is a rule: an agent buying search through Cloudflare buys only from crawlers that identify themselves and respect site preferences. The rule sits at the point of sale, not in a policy document you would have to go and check.\n\nThe money side follows the shape of AI Gateway. Search draws down your gateway credits at the partners' list prices \"without any additional markup.\" It shows up in the same observability logs as your other gateway traffic. It supports bring-your-own-key, and it flags partners with zero data retention. You can reach it as a REST endpoint under your account's AI path, or as a one-line Workers binding. Cloudflare also says web search will be one of the first built-in server tools in the gateway.\n\nHere is where the APIs.io record comes in, and where the post turns to look at the company itself. The catalog holds the control plane this release lands in. The Cloudflare provider page lists 650 API pages, and this launch extends the Cloudflare AI Gateway API, with the Workers binding reached through the Cloudflare Workers API. The agentic access profile maps 3,118 operations, 1,576 of them acting, and sixteen Agent Readiness dimensions are lit. The Kin Score is 81.3, exemplar band, and Agent Readiness is 74.8, agent-native.\n\nBut the record is not all lit. Three dimensions remain unlit for Cloudflare, and this release touches one of them: agentic commerce. That dimension measures whether an agent can pay for a capability through the API itself. In this launch, your agent's search spend comes out of a gateway balance at a published per-call price, attributed and logged. The post calls that close to the shape the dimension describes, metered and agent-initiated, though still bound to an account that a human funds. So the catalog does not credit Cloudflare with the dimension yet. The company has built most of a meter, and the record says only that.\n\nWhat do you take from this? First, if your agents browse, the 404 problem has a named fix, and it is search rather than better guessing. Second, you can ask a sharper question of any search provider your agent uses: does the crawler identify itself, and does the response link back to what was crawled? Cloudflare has made that the entry requirement for its partners. Third, watch the spending. Because search is metered through the gateway, you can see what your agent spends on the web in the same logs where you already watch everything else, and the account behind it is still yours.\n\nThe post's closing line sums it up: Cloudflare has made the honest crawler the only crawler an agent can buy from, and has built most of a meter for what agents spend.\n\nRead the original: https://apis.io/2026/10/20/cloudflare-gives-agents-web-search-through-ai-gateway-with-verified-crawlers-only/",
  "title": "You Told Your Agent to Read the Web. Cloudflare Wants It to Search First.",
  "topics": [
    "cloudflare",
    "ai-gateway",
    "agent-web-search",
    "verified-crawlers"
  ],
  "published_at": "2026-10-21T02:50:17.711Z",
  "expires_at": null,
  "policy_version": "2026.09.25-1"
}