1. Observation boundary
An observed query enters the local trace only when a provider adapter finds it in an explicitly search-scoped transport field or recognized Google AI Overview element. Generic message fields and containers are ineligible. Chat messages, titles, account identity, conversation URLs and conversation IDs do not exist in the event schema.
If an adapter can no longer recognize that boundary, it fails closed. Estimation is a separate user-triggered action and never mutates an observed event into an estimate.
2. Controlled generation experiment
For a seed query , provider model and minimal versioned prompt , the model produces one structured vector of exactly 12 candidate queries:
Candidates are normalized with NFKC, whitespace normalization and exact case-folded deduplication. Unsafe strings are removed. No model is allowed to score another provider’s candidate set.
3. Native token log probabilities where exposed
GPT-5.6 Luna returns token log probabilities for the same structured output that contains the candidates. For a query , let be the set of output tokens whose UTF-8 byte interval overlaps that query’s JSON string content. Every token is included once; token length does not create extra weight.
The system fails closed if fewer than six candidates can be mapped to finite native token logprobs. It does not substitute another provider or an ordinal fallback. The inverse-perplexity score is a ranking statistic for one conditional generation—not an independent probability that the original assistant searched that query.
4. Google and Anthropic: empirical native sampling
The current Anthropic endpoint does not return output token logprobs for Claude. The configured Gemini 3.1 Flash-Lite Developer API endpoint rejects responseLogprobs. These are measured endpoint capabilities, not assumptions about every historic model or SDK. Open Queries therefore reports a different provider-native estimator instead of silently using GPT. Each provider model receives the same versioned prompt in 16 independent structured-output calls. At least 12 must succeed. Parallel transport changes wall-clock time, not the number or statistical independence of those model calls.
Exact normalized matches are counted once per sample. The score object exposes K, n and its Wilson 95% confidence interval, making the wider uncertainty at n ≤ 16 explicit.
5. Provenance and retention
Every estimate carries its provider model, method and prompt version. The side panel leads with ordinal rank and keeps the mathematical evidence behind an expandable detail control. It never formats these values as demand percentages.
Privacy starts unaccepted and is controllable during onboarding and in Settings. Once accepted, every observed query is automatically sent, whether or not its fan-outs are requested. The query trace and fan-out estimation are visible only while privacy is accepted. Raw events expire after 13 months. Estimated fan-outs are returned to the extension and never stored as observed queries.
6. Limits and interpretation
- Visible tool activity can be incomplete.
- Provider transport or UI changes can temporarily disable an adapter.
- Generation and sampling are stochastic and model-version specific.
- Tokenization makes scores comparable mainly within a provider run.
- Empirical Gemini and Claude intervals are deliberately wide at 12–16 samples.
- Observed query frequency is not population search volume.
For assumptions, derivations and alternatives, read the technical note: Estimating fan-out queries with log probabilities.