AI search visibility APIs
Whether AI assistants name your domain when your buyers ask. 1 endpoint here answered a real call on 19 November 2026, covering Geo. You send domain and get structured fields back, with one key for all of them. A call costs 30 credits, which is about $294 per 1,000 calls at the smallest paid plan's rate.Formula A call that comes back empty is not charged.
What you can build with ai search visibility data
- Check how AI assistants show your domain. 2 working calls, 32 credits per run, real responses from 19 November 2026, code you can run.
Every ai search visibility endpoint side by side
What you send, the first fields that come back in the sample, the credits per call, the price of 1,000 calls and the response time at the last nightly check.
| Endpoint | You send | You get | Credits | Per 1,000 calls | Last nightly check |
|---|---|---|---|---|---|
| AI search visibility check | domain | domain, mode, cached, score, total, score_percent | 30 | $294 | 1183 ms |
Each row links to its page with the full sample response and code in curl, Python, JavaScript and n8n.
One real answer: AI search visibility check
Captured 19 November 2026: the fields of the answer with the value each had, shortened for display (long text cut, lists cut to three items); it is not invented. You send domain and it came back in 2342 ms. This call needs a key: 100 free credits, no card.
{
"domain": "stripe.com",
"mode": "regular",
"cached": true,
"score": 5,
"total": 5,
"score_percent": 100,
"cited": true,
"visibility_label": "strong",
"competitors_mentioned": "a list of 2",
"cta_branch": "monitor",
"gated": true
}Free to start: 100 credits, no card. Then from $10. Credits you buy never expire.
Get my free keyLive state of every endpoint: status · platforms · pricing
How we calculate
- Price of one call and of 1,000 calls: The credits per call times the smallest paid plan's price per credit (its monthly price divided by its monthly credits), times 1,000 for the larger figure.
Data: scripts/data/endpoint-credits.json and plans.json, 2026-11-20. Every other figure on this page is copied from the record, not calculated by us.