Skip to main content
idapt
HomeAI ModelsPricing
Sign inStart free
Blog

How We Rank 250+ Models

Richard Morel· Founder·July 16, 2026

Model rankings are easy to fake and easy to fudge, so ours follow rules designed to survive skeptical reading. This post is the methodology behind the rankings, stated plainly enough to be checked.

Named benchmarks, never invented composites

The benchmark lanes are raw, named, public benchmarks: LiveCodeBench and SciCode for coding, AIME and MATH-500 for math, GPQA, MMLU-Pro, and HLE for knowledge and reasoning, among others. Each lane shows the benchmark's own scores with provenance. What you will not find is a proprietary mega-score that blends unlike things into one unfalsifiable number and quietly encodes editorial choices.

The capability index is rescaled, and says so

For an overall view, we use a capability index derived from the Epoch Capabilities Index: openly published data and methodology, re-fit by us for models Epoch has not scored. Where a model lacks a score, the index shows nothing: an omitted number is missing, never silently zero, because "no data" and "scored terribly" are different facts.

The second plane: how models actually behave here

Benchmarks are the lab; production is the field. A separate telemetry plane tracks what our own traffic observes: speed, reliability, uptime, and realized cost per model and provider. That plane feeds routing and failover and gives the rankings a reality check benchmarks cannot: a model that aces a leaderboard and times out at dinner hour is both of those things, visibly.

Where the rankings flow

The same data backs the model pages, the compare surfaces, and the methodology bands on every best-of roundup: when a roundup says a pick follows the coding lane, that lane is one click away, with the same numbers. One data plane, several views, no private arithmetic.

The standing invitation

The strongest check on any ranking is your own prompt: run it across the contenders in parallel tabs and see whether our numbers predicted your result. When they do not, that is signal (benchmarks measure benchmarks), and it is why the rankings link the evidence instead of asking for trust.

EngineeringModelsBenchmarks

Found this helpful? Share it:

  • Named benchmarks, never invented composites
  • The capability index is rescaled, and says so
  • The second plane: how models actually behave here
  • Where the rankings flow
  • The standing invitation

Continue reading

  • How Model Failover Works in idapt

    The routing engineering behind 200+ models: cheapest-first provider selection, automatic failover, sticky conversation pinning, and visible attribution.

  • Real Receipts: How Model Outputs Are Captured

    Why idapt's model showcases are captured from real production runs with cost and latency attached, and why staged demos are banned from proof surfaces.

  • Capability-Matched Cost Cutting: Pay for the Ceiling You Use

    Most AI spend goes to flagship models doing non-flagship work. How to match benchmark tier to task tier, verify the swap, and keep quality where it matters.

  • Bring Your Own Keys: BYOK in Practice

    How BYOK works in idapt: connect provider API keys, route matching models on your accounts, and mix BYOK with platform billing and local inference.

Explore idapt

  • Best of: the picks by job

    Data-backed model picks for coding, writing, research, and media.

  • The live rankings

    Named public benchmarks and the capability index, per model.

  • One chat. Every model.

    GPT, Claude, Gemini, Grok, Llama: pick mid-conversation, cheapest-first.

  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Voice Mode
  • Voice HUD
  • Web Search
  • Image Generation
  • Video Generation
  • Audio Generation
  • Transcription
  • Drive
  • Secrets
  • Sharing
  • Workspaces
  • Tasks
  • Memory
  • Agents
  • Subagents
  • Automations
  • Skills
  • Code Execution
  • Computers
  • Computer Use
  • Cloud Computers
  • Local AI
  • AI Gateway
  • API & SDK
  • CLI
  • MCP
  • Tunnels
  • All features →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Learn
  • Free tools
  • Prompts
  • Templates
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)