Web Search API
- ID
- 31933
- Status
- summarized
- Published
- 05 Oct 2026, 6:47 PM
- Fetched
- 06 Oct 2026, 12:11 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://developers.cloudflare.com/changelog/post/2026-10-02-introducing-web-search-api/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 6.0
- Created
- 06 Oct 2026, 12:11 AM
- Tags
- Audience
- developersai_agent_usersai_ml_learnersstartup_founders
What happened
Cloudflare launched a beta Web Search API that lets AI agents and apps run web searches to ground responses in live information rather than relying on model training cutoffs. At launch it routes to three providers — Ceramic.ai, Exa, and Linkup — all supporting Zero Data Retention for requests made through Cloudflare and committed to Cloudflare's verified bot crawling standards. Requests run through AI Gateway, appear in gateway logs, and are billed at each provider's list API price with no markup, with an option to bring your own provider API key; it is callable via REST or the Workers AI binding (env.AI.websearch).
Why it matters
If you already route model calls through Cloudflare AI Gateway, adding search grounding is now a config change rather than a new vendor contract: one credential, one log stream, provider billed at list price, and you can still BYO key if you have existing Exa or Linkup credits. The decision to make this week is whether centralising search through Cloudflare's proxy is worth it versus calling Exa/Linkup SDKs directly — the tradeoff is unified billing and ZDR terms against an extra hop and dependency in your agent stack.
Discussion angle
Is an aggregator layer over Exa/Linkup/Ceramic actually valuable, or is it just a thin proxy you could replace with a direct SDK call? Worth comparing what Cloudflare adds — ZDR handling, bot-crawling standards, unified gateway logs — against the cost of another dependency in your retrieval path, and whether the 'no markup, list price' claim holds once you model real query volume.