I'm Nitin Kumar, Lead Project Coordinator at Debugged Pro. I help software and IT agencies in India and the USA ship agent features clients can trust. Cloudflare Web Search API is Cloudflare's new open beta that grounds agents with live web results through AI Gateway.

Cloudflare announced the product on its developer blog on October 2, 2026, during Birthday Week. The Web Search API docs say agents can stop guessing URLs and curl-ing 404s when they need fresh pages.

This guide sticks to verified facts from Cloudflare. It maps those facts to delivery choices for India and USA agency teams that already run agents on Workers, AI Gateway, or mixed stacks. You will see pricing, limits, BYOK rules, and a pilot checklist you can paste into a client SOW.

Cloudflare Web Search API launch artwork from the official blog — Feature image: Web Search API artwork from the Cloudflare Blog post Introducing Web Search API via AI Gateway. Credit: Cloudflare.

What Cloudflare Web Search API solves for agency agents

Models freeze at a training cutoff. Clients still ask for last week's changelog, today's pricing page, or a new vendor API. Many agents guess a URL, fetch it, and fail when the path is wrong.

Cloudflare Web Search API gives the agent a search step first. It returns structured titles, URLs, and descriptions you can inject into model context, so answers track live sources.

Cloudflare also ties the launch to crawler honesty. Partners must meet verified bot rules, respect robots.txt, and include a source link on every result. That matters when India and USA clients care about publisher trust and audit trails.

How Cloudflare Web Search API fits AI Gateway

Web Search API is not a stand-alone silo. Every call routes through an AI Gateway you already use for model traffic. Logs, analytics, billing, and access controls sit next to inference.

Observability: search requests show in the same gateway logs as model calls.
Unified Billing: searches draw AI Gateway credits at each provider list price, with no Cloudflare markup.
BYOK: store Ceramic, Exa, or Linkup keys on the gateway when you want direct provider billing.
Access control: decide which providers a gateway may use and who can call them.

Prerequisites are simple: a Cloudflare account, a gateway (every account has one named default), and either gateway credits or a stored provider key. REST tokens need Account Workers AI Read and Account AI Gateway Read.

Cloudflare Web Search API documentation overview graphic — Body image: Web Search API overview artwork from Cloudflare Docs. Credit: Cloudflare.

Cloudflare Web Search API providers and list prices

The providers page lists three search engines behind one response shape. You change a provider field. Your parsing code stays the same.

Ceramic.ai (default)

Provider value: ceramic.
Independent index of more than 40 billion pages built for agents and LLM apps.
Long descriptions up to 8,000 characters. Strong fit for many searches per task.
Zero Data Retention: Yes. Price: $0.25 per 1,000 requests.

Exa

Provider value: exa.
Keyword plus embeddings search. Uses Exa auto mode with page highlights as descriptions.
Useful when you want short, query-relevant snippets for context windows.
Zero Data Retention: Yes. Price: $7.00 per 1,000 requests.

Linkup

Provider value: linkup.
Fast search depth with raw results, not a generated answer.
Good for tool calls that need quick, cited snippets from trusted sources.
Zero Data Retention: Yes. Price: $5.00 per 1,000 requests.

For agency pricing reviews, start on Ceramic for cost-sensitive loops. Spot-check Exa or Linkup on the same queries when snippet quality or citation style matters more than unit price.

REST, Workers binding, and tool-loop patterns

Cloudflare documents two first-class call paths. Both end in the same normalized items array with url, title, and optional description fields, plus metadata such as requestId and latencyMs.

REST: POST to /ai/websearch/ on the Cloudflare API with query, optional provider and limit, and options.gateway.id.
Workers AI binding: call env.AI.websearch({ gatewayId, query, provider, limit }) and read response.json().
Tool loop: expose a web_search function tool to a model, run websearch on the tool call, then pass JSON results back as tool content.

Limits to put in design docs: query length max 1,024 characters, and at most 10 results per request (default 10). The blog also says native Server Tools inside AI Gateway are coming, with web search planned as an early built-in tool.

How to use Cloudflare Web Search API documentation graphic — Body image: How to use Web Search API artwork from Cloudflare Docs. Credit: Cloudflare.

BYOK and credit choices for client contracts

India and USA agencies often mix prepaid cloud credits with client-owned vendor keys. Cloudflare supports both paths.

Omit byokAlias: gateway uses a stored default key for that provider if present, otherwise bills AI Gateway credits.
Set byokAlias: gateway must find that alias or the call fails with HTTP 400. No silent credit fallback.
Keys stay encrypted in Secrets Store. The request body never carries the provider secret.

Put the billing mode in the SOW. Credit-funded pilots are easier for agencies. BYOK fits clients who already negotiated Exa or Linkup rates and want those invoices under their own accounts.

Agency delivery checklist for India and USA teams

You do not need a full production rewrite on day one. Prove grounding quality and spend on one workflow first.

Pick one agent that already fails on stale docs, such as a release-note summarizer or support triage bot.
Wire search through the existing AI Gateway so logs stay next to inference for India overnight and USA daytime reviews.
Run Ceramic for two weeks and log cost per successful task at $0.25 per 1,000 requests.
A/B five hard queries on Exa and Linkup before you change the default provider in production.
Decide credit versus BYOK with the client, and document who owns the search invoice.
Cite sources in user-facing answers using the result URLs, matching Cloudflare's source-link requirement.

If your agents also need typed decision scores on the hot path, see our Cloudflare Clef agency guide. For packing compute, inference, and tools into one monthly agent bill, our Agent Droplets agency guide covers DigitalOcean Managed Agents.

Pilot scope Debugged Pro uses with clients

At Debugged Pro, our software development consulting work with India and USA agencies treats search grounding as a delivery artifact, not a demo trick.

Week one: add Web Search API behind a read-only tool, cap limit at 5, and measure latencyMs plus cost per task on Ceramic.
Week two: compare Exa and Linkup on the same query set, then freeze one provider for the pilot SOW.
Exit criteria: grounded answers with clickable sources, a written billing mode, and a rollback path that disables the tool without redeploying the whole agent.

Cloudflare Web Search API will not fit every account. Teams locked into a single model vendor's native search tool may stay there for that model. Agencies that already standardize on Cloudflare AI Gateway gain the shared control plane Cloudflare describes.

Open beta also means you should state preview risk in client notes. Cloudflare marks the product Available in open beta on the docs overview. Put that sentence in the SOW so nobody expects GA SLAs yet.

Practical patterns for multi-region delivery

India and USA pods often share one agent stack across time zones. Gateway logs help both leads see the same search spend and failure modes.

Shared gateway, separate aliases: keep client BYOK keys under named aliases, not a single shared secret.
Cost notes in SOD and EOD: log search count and provider mix daily so India and USA leads see the same burn.
Provider neutrality: parse only url, title, and description so you can switch Ceramic, Exa, or Linkup without a schema rewrite.
Human review for high-risk answers: search grounding reduces cutoff errors, but people still approve legal, medical, or financial claims.

When a client asks why you chose Cloudflare Web Search API over raw crawl loops, show the 404 problem Cloudflare described and your measured cost per grounded task. Marketing pages do not replace your own two-week sample.

If Birthday Week docs keep moving, point the agent at Cloudflare's own search results first. That is the use case Cloudflare called out for builders who miss new product pages during launch week.

Also keep response shape boring on purpose. Cloudflare normalizes provider output into items with url, title, and optional description, image, favicon, and last-modified fields. Agency parsers should ignore optional fields they do not need so a provider swap does not break production.

Finally, teach support and delivery leads the same failure story. A missing gateway credit, a bad byokAlias, or a 1,024 character query that got truncated all look different in logs. Write those three cases into your runbook before the first client pilot goes live.

Key Takeaways

Cloudflare Web Search API launched October 2, 2026, in open beta through AI Gateway with Ceramic.ai, Exa, and Linkup.
List prices via gateway credits are $0.25, $7.00, and $5.00 per 1,000 requests, with no Cloudflare markup and Zero Data Retention on all three.
Call it over REST or Workers AI websearch(), with query max 1,024 characters and up to 10 results per request.
BYOK stores provider keys on the gateway. Setting byokAlias fails closed if the alias is missing.
India and USA agencies can pilot one grounded workflow, measure Ceramic spend, then lock billing mode and provider choice in the SOW.

Nitin Kumar is Lead Project Coordinator at Debugged Pro. He works with India and USA software agencies on practical AI delivery, agent workflows, and client-ready engineering process.