What is the AI Search API?

The AI Search API is a single endpoint for querying the major consumer AI search engines and getting back the answer users actually see, as clean JSON, with provenance on exactly how it was captured. Captures are browser-first: by default they come from a real browser driving the live AI apps, not the sanitized model API. So you get what a real person would read: the rendered answer and which model produced it.

The answer users see

The actual rendered response, as text, markdown, and structured blocks, from the live app rather than a model endpoint.

Provenance you can trust

How the answer was produced: which model, whether web search ran, the effective region, and the schema version.

Base URL and auth

Every request needs a bearer token and JSON content type:
New accounts start with 500 free credits, no card required. See Authentication to get your key.

One call, every surface

Send one request naming the surfaces you want. The API fans out — running each surface (and region) in parallel — and hands you the same Envelope shape for every one. Integrate the shape once, and every AI search engine looks the same to your code.
A multi-surface request like this returns a 202 with a parent job and one child per surface × region. Each child id records the surface and the region key:
Read each child with GET /v1/jobs/:id to get its Envelope, or register a webhook and skip polling entirely. A single-surface request with no webhook runs synchronously by default — one 200 with the finished result inline, no polling at all. See the Quickstart.

Why use it

Every AI search engine has a different UI, a different structure, and no clean way to read it programmatically. Building that yourself means N brittle integrations that break every time an app ships a redesign. The AI Search API collapses that into one contract: one request, one response shape, every surface. You skip the per-provider integrations and the maintenance that comes with them, and get straight to the answers and the data behind them.

Supported surfaces

Credits are charged only on a successful capture — an empty or failed capture costs nothing. Google Search and Google News each cost 3 credits per capture — see Credits.
Gemini (gemini) is a valid enum value but has no live capture path yet — submitting it returns 422 UNSUPPORTED_METHOD_FOR_SURFACE. It lands in phase 2, together with Meta AI, DeepSeek, Amazon Rufus, and Grok. GET /v1/surfaces returns the live capability matrix at any time.

Next steps

Quickstart

Your first search in a few minutes — from key to Envelope.

Authentication

Get an API key and send authenticated requests.

The Envelope

The canonical response shape: job, provenance, answer, and evidence — plus optional html and credits.

API Reference

Every endpoint, parameter, and field.

For AI agents

A single self-contained page to integrate end to end — built for machine consumption.