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 — plus the structured evidence behind it — as clean JSON. Every capture comes 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, the sources it cited, the follow-up queries it ran, the brands it named, and which model produced it.The answer users see
The actual rendered response — as
text and markdown — from the live app, not a model endpoint.The evidence behind it
Cited sources with character ranges, follow-up queries, brand mentions, shopping, and ads.
Base URL and auth
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.202 with a parent job and one child per surface × region:
?mode=sync for a 200 with the result in the response.
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 evidence.Supported surfaces
| Surface | Enum value | Credits |
|---|---|---|
| ChatGPT | chatgpt | 5 |
| Claude | claude | 6 |
| Perplexity | perplexity | 3 |
| Gemini | gemini | 4 |
| Copilot | copilot | 5 |
| Google AI Overview | google_ai_overview | 5 |
| Google AI Mode | google_ai_mode | 4 |
On the roadmap, not yet requestable: Meta AI, DeepSeek, Amazon Rufus, and Grok.
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: answer, evidence, and provenance.
API Reference
Every endpoint, parameter, and field.