Evidence reference
Methods and evidence limits
This page explains how the dashboard measures demand, model size, attention cache, and current supply. Missing evidence stays missing.
Optional live context
Current public data times
- Demand data through
- Unavailable
- Supply collection ended
- Unavailable
These values appear after each public response passes the complete schema check. They do not change the methods below.
01 / Scope
What this dashboard can answer
It can compare observed OpenRouter demand and checked public model size. It can also compare current model supply and supply history. These measurements are separate.
What this dashboard cannot answer
It cannot measure all market demand or prove that supply is short. It cannot select hardware, predict unit economics, or calculate the exact memory of a serving deployment. The short supply window does not measure long-term reliability.
02 / Demand
Observed OpenRouter demand
- Window
- The latest 30 completed UTC days.
- Published rows
- OpenRouter publishes the top 50 public models each day. It can also publish an
othergroup for the remaining models. - Excluded traffic
- OpenRouter excludes private models, private endpoints, and requests that a user or app keeps private. The source does not state that it excludes zero-data-retention traffic.
A model that is absent from a daily top-50 row has no separate detail. The dashboard does not convert that absence to zero demand. Visible demand is OpenRouter demand under these source limits. It is not total market demand.
03 / Facts
Checked model-fact states
available- The field has a checked public value.
not_publicly_cleared- No public evidence is cleared for this export.
not_available- The checked public model source does not supply the fact. This state also applies when an architecture value is not supported. Use the reason code to identify the condition.
not_found_under_policy- The bounded checkpoint search did not find the fact. This does not mean that no matching checkpoint exists.
Missing values stay missing. They do not become zero. An older value does not replace a failed current check. The public reason states why the value is missing.
04 / Memory
Weights and sequence state
- Theoretical BF16 weights only
- The value is the checked total parameter count multiplied by two bytes. It estimates complete-model weights. It does not show placement on each GPU.
- Smallest reviewed exact quantized checkpoint
- This is the smallest stored size from the reviewed exact quantized checkpoints. Each checkpoint passed the bounded search and a human relationship review.
Neither number is the complete loaded GPU memory. A stored checkpoint size is not the loaded quantized memory. Both numbers exclude engine, allocator, activation, temporary tensor, cache, concurrency, and workspace overhead.
16-bit attention cache
The dashboard calculates theoretical attention-cache bytes for a batch size of one and a generic 16-bit data type. It uses the stated calculation sequence length. The record gives the basis, formula, included bytes, and excluded bytes. Nonstandard attention needs a reviewed architecture resolver.
Recurrent or linear-attention state stays separate. A result is unavailable when required architecture fields are missing, unsupported, or in conflict. The record gives the exact reason. Weight quantization does not imply attention-cache quantization.
05 / Supply
Current supply snapshot
The current snapshot calculates provider and endpoint counts. It also calculates default prices, p50 latency, throughput, uptime, token limits, quantization, tool support, and implicit caching. It uses current OpenRouter rows. Null source values stay unavailable.
It shows minimum, median, and maximum values for price, p50 latency, output throughput, and one-day uptime. Each calculation uses the current endpoint rows that report the value.
Zero Data Retention coverage separates exact provider matches from unknown and ambiguous matches. Field coverage gives the number of current endpoint rows that report each field.
A route quantization label is not a reviewed Hugging Face checkpoint. Conditional price overrides are counted but are not converted into the default-condition price.
Public history fields
listed_provider_count- Distinct listed-provider count at the observation time.
latency_p50_ms_median- Median of reported endpoint p50 time to first token.
throughput_p50_tokens_per_second_median- Median of reported endpoint p50 output throughput.
uptime_1d_percent_median- Median of reported endpoint 1-day uptime.
Price is a current snapshot because the public history record has no price field. Provider rows are private. The public output contains calculated model values only.
06 / Readiness
History and underserved labels
Supply history is sufficient after three distinct UTC observation days across seven calendar days. OpenRouter does not provide earlier endpoint-quality snapshots through this source. Thus, the collector cannot backfill these snapshots.
Underserved labels are not enabled. Demand alone does not prove insufficient supply. The project has no approved gap rule, business threshold, or named workload requirement for this conclusion.
07 / Sources
Public sources and terms
The browser gets the optional times from this site's two public exports. It does not get external research sources. It does not add a new API contract.