AI Visibility
Send one prompt to multiple AI engines and compare their answers side by side
AI Visibility fans a single prompt out to multiple AI engines (ChatGPT, Gemini, Google AI Overview) through Wire's catalogue and returns every engine's answer — full response payload, extracted summary, measured latency, and credit cost — for side-by-side comparison.
Searches run asynchronously: submitting returns a search_id immediately, each source's result lands the moment its engine answers, and you poll (or receive a webhook) for completion.
Endpoints
/v1/ai-visibility/searchSubmit Search — fan a prompt out to the selected AI sources
/v1/ai-visibility/search/{id}Get Search — poll status and per-source results
/v1/ai-visibility/searchesList Searches — your 20 most recent runs
/v1/ai-visibility/search/{id}/retryRetry Source — re-run one failed source
/v1/ai-visibility/sourcesList Sources — the AI engines available to query
Authentication
All endpoints require your API key in the X-API-Key header. See Error Responses for the full list of accepted auth headers.
Search geography
Each search runs from a caller-chosen country (country on Submit Search, 2-letter ISO code, default us) — the same geo targeting the URL scraper offers. AI engine answers are region-dependent, and Google AI Overview in particular may not be served at all for some query/region combinations, so results reflect what a user in that country would see.
Credits
Each source that completes bills its Wire action's per-call rate, snapshotted at execution time. The per-source cost is returned as credits_used on every result, and failed sources cost nothing. Results are never cached — AI engine answers change constantly, so every submit queries the engines fresh (and bills accordingly).
Webhooks
Instead of polling, subscribe an endpoint to the ai.search.completed / ai.search.failed events — a signed delivery fires the moment a search settles, carrying per-source statuses, latencies, credits, and bounded answer previews.
Note — webhook deliveries never contain the full answers. Engine answers routinely run to hundreds of KB, so each
sources[]entry inlines only asummarypreview (≤ 500 chars). The event'sdata.result_url— always present — is the authenticated endpoint for the complete results:curl "https://api.anakin.io/v1/ai-visibility/search/{searchId}" \ -H "X-API-Key: your_api_key"
ai.search.* events are delivered to registered endpoints only (the submit endpoint takes no per-request webhook_url). See Event Types & Payloads for the full payload schema and Webhooks for signatures and endpoint management.