How each engine is actually measured
"10 engines tracked" is only honest with this page attached: capture methods differ per engine, and the differences matter more than the count.
A bare API model call, a search-grounded API call, and a real consumer session can return different answers to the same prompt. Tools that advertise one big platform number without saying which of these each “platform” really is are hiding the most important variable in the measurement. Below is our registry, generated from the same code that runs the captures.
A bare call to the provider’s model API without retrieval. It measures the model’s parametric answer — NOT what a consumer-app user sees, which may include search grounding and personalization.
The provider’s API with its search/grounding capability active, so answers draw on live retrieval. Closer to consumer behavior than a bare model call, but still an API capture, not the consumer UI.
Evidence entered from a real consumer surface (currently operator-seeded). Scheduled browser capture is policy- and spend-gated and is not running.
Google AI Overviews and AI Mode are tracked on the search-results lane (SERP snapshots with inline-citation extraction), not through an answer-engine adapter — counting them as an “engine” would double-dip the search lane. Populations are never pooled across capture modes: the grounded ChatGPT lane is a separate series from the bare-model ChatGPT lane, so a methodology change can never silently rewrite a trend.