AiCoN

Home / Posts / Cloudflare Web Search API: access, billing and limits

DEVELOPER TOOLS

Cloudflare Web Search API: access, billing and limits

By AiCoN | Published 7 October 2026 | Sources checked 7 October 2026

Cloudflare's Web Search API gives AI apps live web results through AI Gateway. The launch names Ceramic.ai, Exa and Linkup. It is a developer API with usage billing, not a free consumer search app.

Official publisher artwork; independent guide, not sponsored

Official publisher artwork hosted by its publisher. Official source. Independent guide, not affiliated or sponsored. Artwork and trademarks belong to their owners.

What does it add?

An AI app can request web results instead of guessing a page address or relying only on old training data. Cloudflare describes fresh, structured snippets and links that can be passed into the app's context.

A search result is still a lead, not proof. Your app should open useful sources, check dates and keep citations with the answer. This matters for Indian prices, government rules and product availability.

How billing works

Cloudflare says requests can draw from AI Gateway credits. It also offers partner list API prices without extra markup, plus Bring Your Own Key for an existing provider account. Credits are not unlimited free calls.

No single per-query rupee price is established in the launch article. Providers and options differ. Check the chosen provider's current rate, any currency conversion, tax and your own account limits before putting a loop into production.

How a developer can start

  1. Read the official launch article and follow its link to the current developer docs.
  2. Set up the intended Cloudflare account and AI Gateway. Check who will pay and which provider is allowed.
  3. Choose a search provider and either Gateway billing or a supported existing provider key.
  4. Create a narrowly scoped API token. Keep tokens on your server, not inside a public website or shared screenshot.
  5. Try one non-sensitive query through the documented REST route or Workers binding.
  6. Read the returned source links. Verify a claim against the source page before using it.
  7. Check Gateway logs and credit use. Set budgets and error handling before allowing repeated calls.

Privacy and source limits

Cloudflare says requests appear in Gateway logs, and it will identify providers supporting zero data retention. That does not mean every provider has zero retention. Read both Gateway and provider terms before sending customer names, documents or secrets.

The company says launch partners committed to its verified-bot crawling requirements and that results must include source locations. Those are provider commitments, not an independent audit of every indexed page.

What changed since the original post?

The launch claims remain supported. We separated API-credit billing from a free allowance and made the zero-retention caveat explicit. Native server tools are described as coming soon, not an available feature in this guide. No API call was made.

Frequently asked questions

Is this a replacement for Google Search?

It is an API for developers building AI apps, not a consumer search interface.

Does it make every AI answer correct?

No. The app still needs to read and check sources.

Can I reuse my provider account?

The launch supports Bring Your Own Key. Check the current provider-specific setup.

Is every provider zero-retention?

No such claim is made. Check the provider's stated policy.

Sources: Cloudflare official launch. Checked 7 October 2026.