Introducing Web Search API via AI Gateway
- ID
- 31130
- Status
- summarized
- Published
- 02 Oct 2026, 9:28 PM
- Fetched
- 02 Oct 2026, 10:45 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/introducing-web-search-api/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 5.0
- Created
- 02 Oct 2026, 10:45 PM
- Tags
- Audience
- developersai_agent_usersai_ml_learners
What happened
Cloudflare announced a Web Search API inside AI Gateway, launching with three search partners: Ceramic.ai, Exa, and Linkup. The pitch is that agents currently guess a URL and curl it, often returning 404, so instead the API injects fresh structured web snippets straight into the model context. Cloudflare says partner crawlers must meet its published 'Verified bots' requirements and that every web search response must include a link to the crawled content source.
Why it matters
If you already run inference through Cloudflare AI Gateway, this is a drop-in way to ground agent answers in live docs instead of building your own search-plus-crawl pipeline. The catch is what the post does not say: there is no pricing, rate limit, or quota information, and the partner list is only Ceramic.ai, Exa, and Linkup, so you cannot make a cost or vendor-lock-in decision from this announcement alone. The concrete thing you can act on is the sourcing rule — if you build on these partners, your search responses must carry a link back to the crawled content, which affects how you render citations. No Malaysia or Southeast Asia detail appears in the text.
Discussion angle
Cloudflare is trying to make 'good crawler' behaviour a condition of being a search partner — is that a real standard or a moat for the partners who signed up, and what does it mean for anyone in Malaysia running a content site that these crawlers will hit?