Use one fixed representative configuration
Configurations are selected by a fixed reasoning-profile priority (Max, xHigh, High, Medium, Low), never by choosing whichever score looks best.
Compare current model capability, context, modalities, public preference and API economics in one continuously refreshed decision surface.
Direct 0–100 source scores remain unchanged. Other evaluations with incompatible units are standardized to a capability scale where 50 is the current reference-set average. The calculation runs locally from public third-party evidence.
Configurations are selected by a fixed reasoning-profile priority (Max, xHigh, High, Medium, Low), never by choosing whichever score looks best.
Published LiveBench and AIHOT scores already use a 0–100 scale and are used directly. Other incompatible raw metrics are standardized across the current model set.
Repeated runs of the same benchmark are grouped so one test cannot gain extra weight. Extreme readings are capped and missing evaluations add neither points nor penalties.
Overall score = Coding 40% + Research 20% + Professional work 20% + Knowledge 15% + Human preference 5%. Prices and speed never affect rank.
A numbered rank requires all four capability domains plus either at least six results from two independent institutions or one complete four-domain direct suite such as LiveBench. LMArena can preserve an overall human-preference rank while specialist evidence is still arriving. Models without enough breadth remain visible but are not numbered. Deprecated and retired releases never receive a current rank.
The reading estimates the capability needed to obtain that raw result on that benchmark. Thirty percent on a hard benchmark can carry more information than ninety percent on a saturated one.
Treat gaps below one point as effectively tied. A gap of roughly three points is usually stable when the evidence mix is resampled.
It has usable evidence but has not yet met the independent-institution and domain-breadth requirements above.
No. Cache, input and output prices are displayed for product decisions but never enter the capability calculation.
The last verified result remains visible with its verification time. A failed synchronization never replaces a valid result with an empty value.