Standing measurement · Edition 1
The AI Visibility Index
Which vendors an AI model names when buyers ask — counted, with the denominator attached. 466 recorded runs, 92 buying questions, 166 companies. It does not rank, and no position in it is for sale.
Of the 166 companies we measured, 140 were named in zero runs. That is the finding this index exists to report, because it is the one that reproduces. Everything else on this page is a count you should read with its denominator, not a ranking.
We did not build this dataset to publish it. Every company we consider contacting has its category’s buying question put to a model three times and the whole answer stored, so that we can say something true in one email. Six weeks of that is 466 runs and several hundred distinct vendor names — a measured record of who currently owns AI answers, produced entirely as a byproduct. Asked whether a public index like this already existed, the model told us there is no standardised one, and named four vendors that all sell per-brand tracking instead. So here is the record.
Two rules, stated before the numbers
1. No position in this index is for sale, at any price. Inclusion is determined by whether a model named a vendor in a recorded run and by nothing else. We do not sell placement, accept sponsored entries, or remove a vendor on request. This is as much self-interest as principle: an index whose entries can be bought is not worth citing, and an index nobody cites is worth nothing to us either.
2. This edition counts. It does not rank. We measured our own noise floor and it is loud — only about half of the vendor names in an answer survive a re-draw of the same question twenty minutes later, and two draws from the same morning differ about as much as draws three weeks apart. Three runs can establish that a company is absent. Three runs cannot tell second place from fifth. Ordering this data into a league table would be a confident ranking of noise.
The whole dataset, at the top
| Measure | Value |
|---|---|
| Recorded model runs (categorised) | 466 |
| Distinct buying questions | 92 |
| Companies measured | 166 |
| Named in at least one run | 26 |
| Named in zero runs | 140 |
| Records excluded as uncategorisable | 115 |
| Window | 2026-07-31 to 2026-09-13 |
| Model | gemini-flash-latest, training knowledge, no web search |
The 115 excluded records are not hidden failures — they are questions too idiosyncratic to group (“the best clipboard history manager for macOS”, “free 3D pose reference tools for artists”). A category appears below only if it has at least six recorded runs and at least two distinct questions. One question is a measurement of that question’s phrasing.
By category
Each number is how many recorded runs named that vendor. It is not a score, a share, or a position. The “absent” column is how many of the companies we measured in that category were named in zero runs — those are companies we chose to check, not a random sample, so read it as a property of our subjects rather than a rate for the category.
LLM gateways & agent infrastructure
| Vendor | Named in runs |
|---|---|
| Langfuse | 4 |
| Portkey | 4 |
| CrewAI | 3 |
| Helicone | 3 |
| E2B | 3 |
| Mem0 | 3 |
| Kong AI Gateway | 2 |
| Cloudflare AI Gateway | 2 |
| Claude Code | 2 |
| Cursor | 2 |
Databases & backend platforms
| Vendor | Named in runs |
|---|---|
| Supabase | 12 |
| Convex | 10 |
| Neon | 9 |
| Vercel | 7 |
| Modal | 7 |
| Databricks | 5 |
| Fly.io | 5 |
| Railway | 5 |
| Cloudflare Workers | 5 |
| Qdrant | 5 |
Observability & session replay
| Vendor | Named in runs |
|---|---|
| PostHog | 21 |
| LogRocket | 12 |
| FullStory | 10 |
| Smartlook | 10 |
| UXCam | 6 |
| Aptabase | 5 |
| Countly | 5 |
| Microsoft Clarity | 5 |
| Mouseflow | 5 |
| Crazy Egg | 5 |
Secrets & credentials
| Vendor | Named in runs |
|---|---|
| Infisical | 13 |
| Doppler | 10 |
| Phase | 10 |
| Bitwarden Secrets Manager | 5 |
| Dotenv Vault | 3 |
| HCP Vault Secrets | 2 |
| Mozilla SOPS | 2 |
| HCP Vault | 1 |
| Bitwarden | 1 |
| Composio | 1 |
Reading & research tools
| Vendor | Named in runs |
|---|---|
| Google NotebookLM | 6 |
| Readwise Reader | 5 |
| Elicit | 4 |
| Mem.ai | 3 |
| Reflect | 3 |
| SciSpace | 3 |
| Scholarcy | 3 |
| Matter | 3 |
| Instapaper | 3 |
| Snipd | 3 |
AI visibility & AEO services
Conflict of interest. We sell a service in this category, so the vendors counted here are our competitors. We have not touched these numbers, and we are not in them: Thicket was named in zero runs of every question we asked about this category, including our own. If you think a measured index should simply omit the category its publisher competes in, the argument is reasonable — we judged that disclosing it beats hiding it, and the raw counts are the same ones the generator produced.
| Vendor | Named in runs |
|---|---|
| Otterly.AI | 10 |
| Profound | 9 |
| Peec AI | 7 |
| Semrush | 5 |
| BrightEdge | 4 |
| Brand24 | 4 |
| Omniscient Digital | 3 |
| Yext | 2 |
| Conductor | 2 |
| NP Digital | 2 |
Consumer health & nutrition
| Vendor | Named in runs |
|---|---|
| SnapCalorie | 8 |
| Foodvisor | 8 |
| Lose It! | 8 |
| MacroFactor | 5 |
| Cal AI | 5 |
| MyFitnessPal | 4 |
| Lifesum | 4 |
| Cronometer | 2 |
| FatSecret | 2 |
| Carbon Diet Coach | 2 |
Scraping & web data
| Vendor | Named in runs |
|---|---|
| Bright Data | 2 |
| ZenRows | 2 |
| Apify | 2 |
| Coresignal | 1 |
| PredictLeads | 1 |
| Crustdata | 1 |
| People Data Labs | 1 |
| Clay | 1 |
| Proxycurl | 1 |
| Apollo.io | 1 |
Email & deliverability
| Vendor | Named in runs |
|---|---|
| Brevo | 2 |
| Hunter.io | 2 |
| Loops | 1 |
| Customer.io | 1 |
| Resend | 1 |
| Userlist | 1 |
| Postmark | 1 |
| Apollo.io API | 1 |
| IPinfo.io | 1 |
| Scaleway Transactional Email | 1 |
Feature flags
| Vendor | Named in runs |
|---|---|
| PostHog | 3 |
| Flagsmith | 3 |
| Statsig | 2 |
| Unleash | 2 |
| ConfigCat | 2 |
| DevCycle | 2 |
| GrowthBook | 1 |
| LaunchDarkly | 1 |
| Flipt | 1 |
Webhooks & event delivery
| Vendor | Named in runs |
|---|---|
| Svix | 2 |
| Convoy | 2 |
| Hookdeck | 2 |
| Postman | 1 |
| Webhook Relay | 1 |
Compliance & GRC
| Vendor | Named in runs |
|---|---|
| Credo AI | 1 |
| Trustible | 1 |
| Holistic AI | 1 |
| OneTrust | 1 |
| IBM watsonx.governance | 1 |
| Fairly AI | 1 |
| Monitaur | 1 |
| Drata | 1 |
| Vanta | 1 |
| Secureframe | 1 |
Storage & file infrastructure
| Vendor | Named in runs |
|---|---|
| Cloudflare R2 | 2 |
| DigitalOcean Spaces | 2 |
| MinIO | 1 |
| Backblaze B2 | 1 |
| Wasabi | 1 |
| Scaleway Object Storage | 1 |
| Storj | 1 |
| Bunny.net | 1 |
| Vercel Blob | 1 |
| Supabase Storage | 1 |
Security testing
| Vendor | Named in runs |
|---|---|
| NodeZero | 1 |
| Pentera | 1 |
| Hadrian | 1 |
| RidgeBot | 1 |
| BreachLock | 1 |
| Escape | 1 |
| XBOW | 1 |
| Bright Security | 1 |
| Astra Security | 1 |
| Veracode | 1 |
What this index cannot tell you
- ORDER. Three runs per question cannot separate second place from fifth.
- Anything about models other than the one named above.
- Anything about live web search — this is training-time knowledge.
- Whether a vendor is good. It measures recall, not quality.
- Whether the absent companies are absent because of anything they did or did not do. We selected companies we expected to be absent, so the absence rate above is a property of our selection, not of small companies in general.
What it can
ABSENCE. Of the 166 companies measured, 140 were named in ZERO runs, and a company absent from all three runs stays absent on re-draw. The two or three most-named vendors per category are also stable across draws; everything below them is not.
Method
One model (gemini-flash-latest), answering from training knowledge with live web search off, between 2026-07-31 and 2026-09-13. Each question asks for specific product recommendations with a one-line reason, and is run at least 3 times. We store runs attempted, runs that returned a usable answer, and runs that named the subject company separately, so that a failed request can never be silently recorded as an absence — a distinction we learned the expensive way, having once run a metric that reported 0% for three months off 280 consecutive failed API calls.
Vendor names are extracted from the stored answers by a lossy heuristic that also picks up headings and feature phrases; obvious non-vendors are filtered out, and some will have survived. Where a vendor appears under two spellings the counts are not merged. Treat a count of two or three as “named at least once,” nothing more.
How this index gets judged
We publish a falsifier with every measurement we make, so here is this one’s. The index exists on the bet that a measured, un-buyable public record is something AI assistants themselves will cite. On 27 October 2026 we will check whether any assistant names or links this page when asked which sources track what AI assistants recommend. If nothing cites it, the bet was wrong and we will say so on this page rather than quietly keep publishing editions.
A second one, because “nobody cited it” and “it was wrong” are different failures: if a vendor shows us that our count for them is materially wrong — a name we merged, split, or extracted from a heading — we will correct it on this page with the date of the correction visible, not silently. Corrections are the cheapest evidence that an index is real.
Frequently asked questions
What is the AI Visibility Index?
It is a dated public count of which vendors one AI model names when it is asked the questions buyers actually ask — 466 recorded runs across 92 distinct buying questions, covering 166 companies, between 31 July and 13 September 2026. For each category it reports how many recorded runs named each vendor, how many questions were asked, and how many of the companies we measured in that category were named in zero runs. It reports counts, never positions.
Why does the index refuse to rank vendors?
Because our own measurements say the data cannot support a ranking. We re-drew the same questions twenty minutes apart and only about half the vendor names survived the re-draw; two draws taken the same morning differed as much as draws taken three weeks apart. Three runs per question is enough to establish that a company is absent, and nowhere near enough to tell second place from fifth. A league table built on this data would be a confident ordering of noise, so we publish the counts and the denominator and let the reader see the resolution for themselves.
Can a company pay to be added to the index or moved up it?
No, at any price, and this is the one rule with no exception. Inclusion is determined by whether a model named the vendor in a recorded run — nothing else. We do not sell placement, we do not accept sponsored entries, and we do not remove a vendor on request. The reason is self-interested as much as principled: the moment a position in an index can be bought, the index stops being worth citing, and an index nobody cites is worth nothing to anybody including us.
What is the most reliable finding in this dataset?
Absence. Of the 166 companies measured, 140 were named in zero runs across every question we put to the model, and a company absent from all three runs of a question stays absent when the question is re-drawn or reworded. Absence reproduces; the tail of the name list does not. The two or three most-named vendors in a category are also stable between draws, so a very large count is meaningful — but the difference between a vendor named in three runs and one named in two is not.
Which model does the index measure, and does it apply to ChatGPT or Claude?
Every number here comes from a single model — a Gemini Flash release — answering from training knowledge with no live web search. Nothing in this index should be read as a claim about ChatGPT, Claude, Perplexity or any assistant we did not test. A different assistant ingested different material and will name different vendors, and the same assistant with web grounding switched on behaves differently again. Anyone extrapolating a single-model result to artificial intelligence in general is overreaching, and that includes us.
How was the data collected, and why is some of it excluded?
Each buying question is put to the model at least three times and the full answer is stored, along with runs attempted, runs that returned a usable answer, and runs that named the subject company. A failed request is recorded as an error and excluded from the denominator, never counted as an absence. Of 272 records, 115 asked questions too idiosyncratic to group into any category and are excluded from the category tables — reported here rather than quietly dropped. A category is published only if it has at least six recorded runs and at least two distinct questions, because a category resting on one question is measuring that question's phrasing.
Reproduce it
The generator and the underlying record live in our public workings alongside every other measurement we publish. The related write-ups: we checked 32 companies and 27 were never named once, why every visibility check needs a control, and our own audit of ourselves.