Cloudflare's beta Web Search API is available through REST endpoints and Cloudflare Workers. Applications authenticate with an AI Gateway token, name a search provider in the request payload, and receive search results in the response. The service supports bring-your-own-provider keys and offers a unified interface across providers.
The company says the feature targets a common agent failure, where an agent guesses a page URL and calls curl, often producing 404 Not Found errors. Live results, including recent news, API changes and technical documentation, can be passed to language models as context during inference.
Search requests are logged alongside model inference, and billing is integrated with AI Gateway. Providers must follow Cloudflare's verified-bot requirements and return links to where crawled content is located. Cloudflare plans to identify providers that support Zero Data Retention and to add native server tools to AI Gateway, starting with web search.
Why it matters if you build agents
Agents can retrieve current web pages through one endpoint, with search logs and billing kept alongside their model calls instead of guessing URLs. Developers should check each provider's terms on storing and redistributing results before building features that keep them. Until native server tools arrive, Cloudflare Workers is the way to wire search into existing workflows.
Get stories like this every weekday
One short email with the day's agent tooling news.