Skip to briefing

TTB/Archive/06 OCT 2026

TTB-2026-1006
Prepared 06 OCT 2026
UNCLASSIFIED
FOR PUBLIC RELEASEPRIORITY6 min readConfidence high

Search before the fetch

Builders are typing "web search api" and "cloudflare web search api" after Cloudflare shipped a beta on 2 October. The product is not model-native web_search proxied through AI Gateway, and it is not a SerpAPI sidecar. It is a first-class /ai/websearch/ call that returns structured results from Ceramic, Exa, or Linkup on the same control plane as inference.

CloudflareAgentsSearchAI GatewayBuilder tools

Situation

01

This week the search bar, not the press wire, is the signal. Google autocomplete for "web search api" completes into "for ai agents", "for llm", "pricing", and "free". "cloudflare web search" completes into "cloudflare web search api". On 2 October 2026 Cloudflare published Web Search API in open beta. By 5 October the changelog post was on the Hacker News front page at 520 points with 236 comments. X posts matching Cloudflare Web Search API went from zero in the days before launch to 37 on 2 October, 44 on 3 October, 42 on 4 October, and 84 on 5 October (225 in the week through early 6 October). The typed intent is how to give an agent live web context without guessing URLs. The common misread is that this is either (a) the older AI Gateway trick of forwarding a model's built-in web_search tool, or (b) Cloudflare inserting itself as another SerpAPI-style bill you wire by hand. It is neither.

Facts

02
  1. 01On 2 October 2026 Cloudflare's changelog announced Web Search API in beta: agents and applications can search the internet and ground responses in live information instead of guessing URLs or relying on a model's training cutoff. Launch providers are Ceramic.ai, Exa, and Linkup. All three have committed to Cloudflare's verified bot crawling standards. The post states all three support Zero Data Retention for requests made through Cloudflare.Cloudflare changelog, Introducing Web Search API, 2 Oct 2026
  2. 02Web Search API runs through AI Gateway. Searches appear in gateway logs and are billed to AI Gateway credits at each provider's list API price with no additional markup. You can also bring your own provider API key. Call paths are REST POST /accounts/{account_id}/ai/websearch/ and the Workers AI binding env.AI.websearch().Cloudflare changelog, 2 Oct 2026; Web Search API overview and how-to-use docs
  3. 03If provider is omitted, Ceramic.ai is the default. Provider list prices when paying with AI Gateway credits: Ceramic $0.25 per 1,000 requests (Zero Data Retention: Yes), Exa $7.00 per 1,000 (Zero Data Retention: No), Linkup $5.00 per 1,000 (Zero Data Retention: Yes). Limit defaults to 10 and maxes at 10 results per request. Query max length is 1,024 characters. Response items normalize to url, title, and description (plus optional fields when the provider returns them).Cloudflare Web Search providers and how-to-use docs, updated 2 Oct 2026
  4. 04A separate, older AI Gateway page titled "Web Search" (last updated 26 June 2026) documents something else: proxying native web search tools from model providers (Anthropic web_search_20250305, OpenAI web_search_preview, xAI web_search, Alibaba enable_search) so the upstream model runs search. That page explicitly says AI Gateway does not provide a provider-agnostic web search abstraction for search-first vendors such as Perplexity and Parallel.Cloudflare AI Gateway docs, Web Search, last updated 26 Jun 2026
  5. 05The About page states the failure mode Web Search API is meant to replace: without search, an agent that needs live information usually guesses a URL and fetches it; a wrong guess returns 404 and the agent retries. Web Search API returns a list of results to inject into model context. Docs also show a pattern where a model tool named web_search is implemented by calling env.AI.websearch() and feeding results back.Cloudflare Web Search About and how-to-use docs, 2 Oct 2026
  6. 06Demand evidence (verified 6 Oct 2026, Africa/Maseru): Google autocomplete suggestions for "web search api" included "web search api for ai agents", "web search api for llm", "web search api pricing", "web search api free". Suggestions for "cloudflare web search" included "cloudflare web search api". HN Algolia: story "Web Search API" objectID 49963171, 520 points, 236 comments, created 2026-10-05T10:47:06Z, URL the 2 Oct changelog. X get_posts_counts_recent for ("Web Search API" Cloudflare) OR variants: total_tweet_count 225 from 2026-09-29T06:10Z through 2026-10-06T06:05Z, with daily counts 0/0/0/37/44/42/84 and 18 partial on 6 Oct.suggestqueries.google.com; hn.algolia.com; X API via user-X connector, fetched 6 Oct 2026

Assessment

03

We assess, with high confidence, that the thing people are searching for this week is a way to ground agents without URL roulette, and that Cloudflare's answer is a search endpoint, not a model feature flag.

Hold the split. The June AI Gateway "Web Search" page is still real: it forwards Anthropic, OpenAI, xAI, or Alibaba's own search tools when you call those models through the gateway. The 2 October Web Search API is a different object. You POST a query to /ai/websearch/ (or call env.AI.websearch), pick ceramic, exa, or linkup, and get a normalized items[] of urls and snippets. Same AI Gateway logs and credits. Different contract.

The mixup we keep seeing in autocomplete and in builder chatter is that "web search" on Cloudflare means either (1) flip a model's built-in web_search tool, or (2) stand up a separate SerpAPI/Bing key outside the gateway. After 2 October, neither is the default path for a Cloudflare-native agent. Search is an infrastructure call on the inference control plane. List price, no markup, max ten results, Ceramic default at $0.25 per thousand. Exa's Zero Data Retention is No on the providers table even though the changelog's launch sentence grouped all three under ZDR for requests through Cloudflare; treat the providers table as the operational source for Exa until Cloudflare reconciles the wording.

Implications

04
  • If your agent still guesses URLs and curls until it hits 404, the product Cloudflare shipped is the search step before the fetch, not a smarter fetcher.
  • Do not brief "Cloudflare added web search" as identical to enabling Anthropic or OpenAI web_search through AI Gateway. That older path still exists on a different docs page.
  • Budget Ceramic ($0.25/1k), Linkup ($5/1k), and Exa ($7/1k) as different unit costs. Switching providers is one parameter; the bill is not.
  • For Zero Data Retention decisions, read the providers table: Ceramic and Linkup Yes, Exa No, as of the 2 October providers doc.
  • A max of 10 results and a 1,024-character query are hard limits in the how-to docs. Agent loops that assume deep result pages will truncate.
  • BYOK stores the provider key on the gateway. Setting byokAlias makes a missing key fail closed instead of falling back to credits.

Recommended action

05

If you are answering the search intent "web search api for ai agents" inside a Cloudflare stack this week, wire POST /ai/websearch/ or env.AI.websearch through an AI Gateway, pick a provider on purpose (Ceramic default is the cheap lane; Exa and Linkup are not), and treat the returned items[] as context for the model rather than as a page fetch. Separately confirm whether any existing code path was using the June AI Gateway model-native web_search proxy; that is a different switch. Put Ceramic/Exa/Linkup list prices in the cost model before you let an agent search in a loop.

What to watch

06
  • Whether Cloudflare reconciles the changelog's all-three ZDR claim with the providers table that marks Exa Zero Data Retention as No.
  • Additional providers beyond Ceramic, Exa, and Linkup, or a raise of the 10-result cap.
  • GA (exit from open beta) and any change from list-price-with-no-markup billing.
  • Whether the June AI Gateway model-native web_search docs and the October Web Search API docs get a single comparison page so searchers stop conflating them.
  • Independent quality comparisons across Ceramic, Exa, and Linkup on the same agent workloads.

Sources

07
  • Cloudflare changelog - 2 Oct 2026: Introducing Web Search API (beta), partners, AI Gateway billing, REST and Workers examples
  • Web Search API overview - developers.cloudflare.com/web-search/: open beta, structured results, AI Gateway control plane
  • How to use Web Search API - REST /ai/websearch/, Workers websearch(), parameters, BYOK, limits (1024 chars, max 10 results)
  • Providers - Ceramic default $0.25/1k ZDR Yes; Exa $7/1k ZDR No; Linkup $5/1k ZDR Yes
  • About Web Search API - Guess-URL failure mode; normalize-to-items flow; verified bot commitments
  • AI Gateway Web Search (older) - developers.cloudflare.com/ai-gateway/usage/web-search/, updated 26 Jun 2026: model-native search tools, not the Oct API
Cable

PRIORITY / CLOUDFLARE / Web Search API (beta, 2 Oct): /ai/websearch/ via AI Gateway. Ceramic (default, $0.25/1k), Exa ($7/1k), Linkup ($5/1k). Not model-native web_search. List price, no markup. Max 10 results. / TTB 1003

Request a related brief