05
What this does not do
Every reading is a point in time. AI answers shift as the underlying models and their sources change, so a later scan can move for reasons unrelated to anything you did, which is why movement across scans matters more than any single reading. Our own reading of each answer is not assumed to be perfect.
06
Data sources
Every scan queries the developer APIs of OpenAI, Anthropic, Google and Perplexity directly, never scraped. Questions about your brand and its competitors are asked fresh on every scan; questions shared by every brand in a category may be reused for up to 12 hours. Some plans add sentiment from public platforms, reported as a separate, labelled signal and never blended into the AI-engine readings.
Findings are checked against official records rather than our own database: for medicines, the FDA's labels and the EU product information the EMA publishes for centrally authorised medicines, each deciding a claim only in the market its regulator governs; for other sectors, the authoritative public register, among them NHTSA safety ratings, EU Ecolabel and EU eAmbrosia. For supplements and packaged foods, the NIH Dietary Supplement Label Database holds labels transcribed by the NIH from dietary supplements sold in the US, including products no longer on the market, and USDA FoodData Central holds label data supplied by food industry data providers; a label on file in either is a record of what the label says, never a registration or a regulator's approval. A source that returns nothing is recorded as absence of confirmation, never as evidence of absence.
07
Controlled measurement environment
Measurement runs in a controlled, repeatable query environment against each provider's model interface. That is what makes like-for-like comparison possible: the same question design, the same reading and the same decision rule, cycle after cycle, with every question asked recorded verbatim, so a change in the reading is a change in the provider rather than a change in how we asked.
An individual consumer session can differ. Personalisation, interface-specific retrieval, search behaviour, model routing, account configuration and product-level system instructions all vary between users and between apps. Each measured response is therefore an observation within a defined test environment, not a claim that every result reproduces every possible consumer session. What the method is built to do is measure provider behaviour, and movement in it, repeatably over time.
08
Observed consumer surfaces
AlphaCitation captures Google AI Mode and AI Overview answers observed by people in their markets, under a pre-registered, timestamped protocol. These observations are analysed alongside API measurements, with consequential claims checked against the authoritative evidence applicable to each market. Model APIs tell us what AI systems return; Google AI Mode and AI Overviews are what people meet when they search. Each observation is preserved as it was shown, with its sources and context, and timestamped.
For the published study of 14 November 2026, the observer was in the United Arab Emirates, using US and Irish search settings. Observations are reported beside the API measurements and never pooled with them. An observation carries no confidence interval and is not continuous monitoring: it shows what a surface showed a person, at a stated time.
09
Asked and read in the market’s own language
An English answer translated afterwards is not the answer a clinician in that market reads. AlphaCitation asks in the market's language and reads the answer as written. Before a language is used, our reading of it is held to the same accuracy bar as English. Local languages, including Arabic, French, Spanish*, German and Asian languages. *In testing on live engine answers.
10
Verifying what we found
For medicines, Label Ledger checks claims about a medicine's approved uses and populations against the current label, dated, that governs the market: the FDA's in the US, the EU product information of centrally authorised medicines in the EU and EEA, and both as benchmarks elsewhere; findings that rest instead on claims the client registers itself are labelled as such. Which evidence can settle which kind of claim, for which market and as of which date, is set out in our open standard, Which Evidence Settles Which Claim (version 3.0, doi:10.5281/zenodo.23594909). The answers behind the findings are stored with a hash of their content, linked to the record before them, and once a day, if the record has changed since its last timestamp, its latest state is timestamped by an independent authority (RFC 3161). See Label Ledger.