RankingMethodology
Methodology
One overall ranking from comparable public benchmark results. Each entry identifies a model and effort setting, with its evidence available to inspect.
How the score works
- Match the setup. Compare results from the same benchmark version and test setup. Keep each model's measured effort separate.
- Balance the evidence. Split each configuration's comparison weight across original evaluators, then benchmark families. More rows do not automatically mean more influence. Reviewed lab reports can supplement independent evidence, capped at 25% of direct comparison weight.
- Account for opponents. Estimate relative strength from matched wins, ties and losses. Beating stronger opponents counts differently from beating weaker ones. The calculation uses result order, not the size of a score margin.
- Show a shared score. Express estimated strength as a 0–100 comparison score against a fixed reference panel. It is an experimental estimate, not an accuracy percentage.
Overall means consensus across the available evidence. Models can have different task mixes; the score does not establish equal strength in every area. Missing results stay unknown, and the overall score does not average the seven radar values.
Evaluator balancing does not give every benchmark family equal comparison weight. A source measuring one family can give it more influence than a source measuring many. Family-first and joint source-and-family budgets remain unpromoted. Inspect the dated allocation diagnostics.
Benchmark quality: original SciCode results remain visible but do not contribute to scores while grading defects are under review. Independent audit · Evaluator notice. Corrected datasets need a separate protocol review.
How the score is calculated
Checkpoints, thinking budgets, task sets and agent harnesses stay separate. A harness is the surrounding tools and agent software. Unknown efforts, conflicting values and incomplete runs remain visible but cannot enter the fit. "Best across efforts" is not Max. Scores are never copied between efforts.
Each setting divides its independent comparison budget across evaluators, each evaluator's families, each family's evaluations and opponent models. Several distinct settings for one opponent share that opponent's allocation. A pair receives the smaller offer from its two settings, so the resulting source shares can differ. Settings with identical evidence for the same model share weight. Related versions share a family budget; comparisons stay within each version and harness. Reviewed reprints keep the original evaluator's identity.
Bradley–Terry fits the matched comparisons jointly, with 10% neutral smoothing. Wins enter as 0.95, ties as 0.5 and losses as 0.05. Factual accuracy benchmarks use the share of correct answers; mixed-scorer summaries do not enter the rank.
The display score estimates win share against GPT-5.6 Sol High, Claude Opus 4.8 High and Gemini 3.1 Pro High. These fixed references set the scale. No connected comparison path to the complete panel means no score.
Reading the leaderboard
Highest-scoring effort selects the highest aggregate among supported settings for each model. It is not proof that this effort wins their shared tests. All efforts shows every measured setting.
Evidence breadth shows evaluator support and the measured task areas. An entry labeled "Reasoning only" does not establish all-round ability. A single independent evaluator can qualify; multiple evaluators can still disagree. Select the family count for sources and exclusions.
Capability score evidence, reached through the family count, explains disagreements when a matching audit finds that the aggregate order conflicts with shared benchmarks. Source-removal checks describe sensitivity, not statistical confidence. Switching to independent-only evidence can also change the leaders.
Evidence requirements
A rank needs 3 benchmark families, 1 reviewed independent evaluator, 3 opponent models and 2 independent families with 3 opponents each. Lab-only evidence cannot qualify. There is no requirement to cover every capability area.
Multiple independent sources means more than one reviewed independent evaluator contributes. It does not guarantee agreement. Matched provider reruns may contribute within their own test setup. Results using fallback models, unmatched settings or safety stress tests remain visible without entering the ranking. Source percentages describe direct comparison weight, not confidence or fractions of the final score. Family cells are descriptive matched win shares, not separate aggregate ratings.
Source weights and sensitivity checks
Source balancing does not prove independence: overlapping benchmarks may remain correlated. Leave-one-source-out ranks compare the same surviving configurations before and after removal, with lost comparison support counted separately. These diagnostic cohorts include separate effort settings; they are not the default leaderboard. Eligibility is not rechecked after removal.
Movement is a sensitivity diagnostic, not a spread of source-specific ranks or a confidence measure. Sensitivity values appear only when the dated audit matches the current inputs and scoring version.
Freshness: reviewed feeds are scheduled daily. Collection dates record retrieval, not new evaluations. Changed setups and unreviewed tables wait for review; failed checks retain the last accepted evidence.
Capability profiles
Seven areas show where the evidence is strong or missing. These are separate diagnostic estimates, not pieces that add up to the overall score. Gaps remain unknown and preliminary points stay labeled.
Task rankings use supported estimates for the selected area. Areas without enough independent evidence remain available to explore, without a ranked shortlist. Customize ranking combines supported areas using your chosen weights; it does not change the default overall calculation.
Profile calculation details
All capability axes use their own fixed panel: Sol High, Opus 4.7 Max and Gemini 3.5 Flash High, measured across the populated areas. Capability profiles retain 20% smoothing. The overall calibration review did not validate a change to each separate capability.
Limits and validation
Use the ranking as a shortlist. Coverage and opponent selection can change the order, and small score gaps are not statistical proof. Balancing evaluators does not establish equal reliability, remove correlation or give each task area equal weight.
What the ranking cannot establish
Effort labels do not establish equal compute. Settings can cover different tests: the highest aggregate is not proof that one effort beats another on shared tasks. Model pages flag aggregate orders that conflict with shared results across at least three benchmark families. These flags describe comparisons, not independent statistical trials.
Sources cover different models, tasks and setups. Only reviewed, comparable evidence enters the score; not every public result qualifies. A small benchmark lead and a large one both count as a win. Run variance and sample sizes are not modeled, so score gaps and sensitivity ranges do not establish statistical significance.
Validation results and alternative methods
The September 21 review reduced overall smoothing from 20% to 10%. Excluding Grok 4.7 from method selection, mean held-out log loss improved from 0.459 to 0.444 across sources and 0.431 to 0.411 across families, with unchanged coverage. Two additional unanimous shared-result reversals remained, both under 0.6 score points. This is reused-data method development, not prospective validation or proof of a definitive order. Calibration audit
The dated audit predicts 96.8% of held-out family comparisons and 79.4% of held-out source comparisons on average, including empty folds. It retains 13 consistent shared-benchmark reversals. This is reused-data diagnosis, not an untouched final test.
The source-budget policy, with the previous smoothing, was frozen before acquiring LiveBench and SWE-rebench results. On comparable predictions, accuracy rose from 68.4% to 69.3%, with lower probability error. This small gain does not establish statistical superiority. The results were newly acquired, not necessarily newly published. Earlier listwise and family-varying candidates remain unpromoted under their separate temporal gates.
A joint source-and-family budget remains unpromoted: it reduced effort-order reversals but worsened held-out probability error and source sensitivity. New independent Vals AI evidence also favored the then-deployed formula in a frozen prediction check; acquisition dates alone do not make this future-data validation.
Frozen external validation · Dated configuration audit, alternatives and coverage gaps · Candidate diagnostics and release status
Observation admission decisions · Scores and contributing evidence · Source measurements
Comparing value
Value finds the strongest supported configurations within your budget. Capability scores and evidence requirements stay unchanged. We do not divide scores by price: estimated win share does not count successful tasks.
Cost basis, coverage and limitations
The budget is applied before selecting the best effort per model; lower cost breaks exact, unrounded score ties. With no budget, higher Capability scores lead among priced configurations. A cost frontier shows configurations with no cheaper, equal-or-higher point estimate. Similar scores do not prove equivalent task performance or statistically proven winners.
Measured usage: the complete AA Intelligence Index v4.3 workload, priced from its reported tokens, including reasoning, cache treatment and reviewed per-evaluation fallback token fractions at the fallback model's prices. Missing families and unresolved fallback routing receive no task cost. This is one evaluator's workload, not a universal cost of quality.
Price scenario: fixed uncached input and total billable output tokens at AA's published rates. It cannot establish effort efficiency. Endpoint, context tier, tool charges and fallback costs are not verified in this estimate. Open weights are not treated as free inference.
Coverage and freshness: exact reviewed configurations only. Missing and over-budget costs do not receive a Value rank. Missing costs stay unknown; pricing older than 30 days is suspended from comparison. Source dates and skipped records are downloadable.
Why LLM leaderboards disagree
Different tests answer different questions. Measured task results, human preferences and API usage can put the same models in different orders. Check the underlying test, effort and agent setup before choosing a model for your task.
UnifyBench vs Arena vs Artificial Analysis
| UnifyBench | Artificial Analysis | Arena | |
|---|---|---|---|
| Answers | What do comparable public benchmarks collectively suggest? | How did models do on this independent suite? | Which answers do people prefer? |
| Type | Aggregate of reviewed comparisons | Independent measured index | Human preference |
| Best as | A shortlist to investigate | Independent validation | A check of answer preferences |
Use UnifyBench to find candidates, then inspect the original results from Artificial Analysis, LMArena and task-specific benchmarks. OpenRouter rankings show API usage, a separate signal from measured performance.
Agent results also depend on tools and the surrounding software. They describe a model in that setup, not model quality in isolation. No single leaderboard establishes the best model for every task and budget.
Arena and Artificial Analysis disagree. Which should I trust?
They answer different questions. Arena measures human preference on answers; Artificial Analysis runs one independent scoring suite. When they diverge, that is expected, not a bug. Use both for what they measure, not as a single crown.
I know nothing. Where do I start picking an LLM?
Start with a multi-source benchmark shortlist (UnifyBench) to get a first look with weights you control, then check Artificial Analysis for independent scores, Arena for answer preference, and task-specific benches for your workload. That path beats refreshing one chart.
Is OpenRouter a good "best model" ranking?
No for measured quality. OpenRouter ranks API usage / popularity, not benchmark performance. Useful for what people are calling, not for which model scores best. Treat it as a demand signal, not a leaderboard of capability.
Does Max / XHigh effort mean that model is best?
Max or XHigh is a measured configuration, not a crown. UnifyBench keeps each model+effort separate and builds a source-balanced shortlist across published benches. Use that shortlist, then check Artificial Analysis for independent scores and cost-per-task, Arena for human preference, and a task-specific bench for your job.
What's the best LLM for coding or agents?
There isn't one best coding LLM. Overall leaderboards, coding indexes, and agent harnesses often disagree, and the scaffold can move scores as much as the model. Shortlist with UnifyBench's Coding or Agentic weights, validate on Artificial Analysis (and FrontierCode for merge-quality), check Arena coding preference, then run your own harness on your repo.
What's the best open-weight (open source) LLM?
There is no single best open-weight LLM. Among open-weight models, Artificial Analysis currently ranks MiMo-V2.6-Pro first on its Intelligence Index, while Arena voters prefer Kimi K3. UnifyBench combines many sourced benchmarks into one open-weight shortlist; validate it on Artificial Analysis, check Arena, then test on your own task and hosting budget.
An open license isn't always open source, so check the terms.
Who is the best LLM right now?
For October 2026, compare these dated checks. UnifyBench's default Overall leader is GPT-6 Astra · XHigh (95.9; evidence published 22 Oct 2026; documented evidence). Artificial Analysis's leader is Claude Opus 5.5 (Max, Default Fallback) (Index 58; checked 28 Oct 2026). Arena's last known leader is Gemini 4 Argon · High (Elo 1525 ± 9; Preliminary; checked 7 Oct 2026, board updated 2 Oct 2026; stale check; refresh failed, last good check retained). The boards measure benchmark consensus, an independent suite, and human preference. The Intelligence Index, Arena Elo, and UnifyBench score use different scales and cannot be compared directly. Shortlist with UnifyBench, check Artificial Analysis for independent scores and cost per task, check Arena for preferences, then test your own tasks.
When Arena and Artificial Analysis disagree, they are answering different questions: human preference vs one independent suite. Start with a multi-source benchmark shortlist (UnifyBench), then check Artificial Analysis for independent scores, Arena for answer preference, and task-specific benches for your workload. OpenRouter ranks API usage, not measured quality.