OpenRouter-style public rankings are useful because they are visible and model-specific. The risk is scope: a router ranking is not a claim about global usage unless the source explicitly says so.
What the data can show
Public router rankings can show which models are popular on that routing surface and how usage shifts alongside pricing, context, latency, and availability. That is useful directional signal.
- Use it to compare model momentum on the router.
- Use it to notice changes worth investigating.
What the data cannot prove
Router rankings are not global model usage unless the source explicitly makes that claim. Treat them as a public slice, not the whole market, and keep the scope visible anywhere the ranking is reused in a model, cost, or adoption argument.
- Avoid phrases like total global token burn unless sourced.
- Keep source URL and checked date next to derived claims.
Why pricing matters
A model can be popular because it is cheap enough, fast enough, available through a preferred API, or good enough for a specific workload. Ranking without pricing context can mislead.
- Compare input and output price separately.
- Look at context window and provider availability together.
Best use
Use the rankings to compare model cost and router momentum, then validate model choice against your own quality, latency, and acceptance metrics. Public rankings are a map, not your destination.
- Let public rankings suggest tests.
- Let your evals and traces decide production routes.
