CodeSmart

Methodology

Every number on this site is derived from independently published data — Artificial Analysis benchmarks, provider pricing pages, and disclosed usage limits. Code Smart computes none of the source inputs; it normalizes and combines them, and labels every estimate with a confidence level. Last regenerated 2026-06-23 (methodology v3.2).

Intelligence Score

Each model's quality is a weighted blend of three Artificial Analysis indices, all on a 0–100 scale:

  • 50% Agentic Index — multi-step autonomous task completion (the highest-value capability).
  • 40% Coding Index — code generation, debugging and refactoring quality.
  • 10% Speed Score — normalized output tokens/second; secondary to quality.
Intelligence = 0.50 × Agentic
           + 0.40 × Coding
           + 0.10 × Speed

AA Speed is not exported as a standalone column in the static dataset; it is folded into WMQ at the weight above. Where AA has no profile for a model, Intelligence Score cannot be computed and the Value per Intelligence per Task shows "—".

Value per Intelligence per Task

The Value per Intelligence per Task answers one question: how much intelligence are you getting per cost per one task?

QAMU = estimatedTokens1mo × (WMQ / 100); score = QAMU × efficiencyMultiplier / price → 0–100

Normalized against a reference of 1M quality-adjusted tokens at $20/mo. A free plan has no price denominator, so it carries no normalized Value per Intelligence per Task.

Efficiency multiplier

Two models can post the same quality score yet differ sharply in how much compute they burn to finish real work. Artificial Analysis publishes a cost-per-task figure — the dollar cost to run its standardized agentic task — and Code Smart folds it into the Value per Intelligence per Task as a bounded multiplier. Cheaper-per-task nudges value up; pricier nudges it down. It rides on top of quality and price rather than replacing either, so it can never dominate them.

reference   = median cost-per-task across models with data
eff         = clamp(0, 100, reference / costPerTask × 50)   // median model → 50
multiplier  = 0.85 + (eff / 100) × 0.30                     // bounded [0.85, 1.15]
Value per Intelligence per Task = Intelligence-adjusted capacity × multiplier / price → normalized 0–100

The reference is self-calibrating: the median model sits at a neutral 1.0×, cheaper models reach up to 1.15×, pricier ones down to 0.85×. When a model has no published cost-per-task — the current state for every model — the multiplier is exactly 1.0 and the Value per Intelligence per Task is unchanged. Cost-per-task and the active multiplier surface on each ranking card ("—" until a value is sourced).

Model Efficiency Index

A separate ranking that answers: which model delivers the most intelligence and throughput per dollar spent on API calls? Three inputs from Artificial Analysis and OpenRouter combine into a single composite.

Cost model — $/Task

Assumes 10,000 input tokens per agentic request (70% fresh, 30% cached):

$/Task =
  ( 7,000 × OR_In$/1M
  + 3,000 × OR_CH$/1M
  + Tok/Task × OR_Out$/1M
  ) ÷ 1,000,000

Composite — Intel·t/s/$100T

Rewards models that are simultaneously smart, fast, and cheap:

(Intel × t/s) ÷ $/100T

Doubling speed at constant cost
and intelligence doubles the score.
Doubling cost halves it.

Intel = AA Intelligence Index (0–100). t/s = AA median output tokens/sec. $/100T = cost to run 100 representative agentic tasks at OpenRouter pricing. Full model rankings →

Token estimation

Providers disclose limits in many units — messages, requests, credits, compute units, or raw tokens. The normalization engine converts each into per-window token estimates using an 8-layer priority dispatch (one layer per limit type); the first matching layer wins. These are estimates, not guarantees.

#TriggerMethodConfidence
1Limit unit is tokensUse the value directly; apply model multiplier if configured.observed
2Message limitsMonthly messages × tokens per coding message (low/base/high).inferred
3Request / call limitsMonthly requests × tokens per agentic request (low/base/high).inferred
4Credit limitsCredits × provider-specific or default credit-to-token mapping.inferred / assumed
5USD credit budgetMonthly dollar budget ÷ published model API output rate ($/MTok). Outputs a base estimate plus a low–high range spanning the cheapest to most expensive model available on the plan.inferred
6Compute unitsUnits × provider-specific or default compute-unit-to-token mapping.inferred / assumed
7Time-window catch-all (1h, 3h, 5h, 1d, 1w, 1mo, 1y)Extrapolate proportionally across the reset window; apply model multiplier. 3h windows use active-hours scaling (working days × coding hours / 3).window-dependent
8Unknown / vagueAll estimates null — rendered as "—", never 0. "Unlimited"/fair-use claims are treated as unknown — never a synthetic estimate.unknown

Per-window estimates (5h / 24h / 1w / 1mo) are extrapolated proportionally with confidence decay. A vague or undisclosed limit yields null — shown as "—", never a misleading 0.

Confidence levels

Every figure carries one of five confidence levels. Confidence is never upgraded — a derived value can be no more certain than its weakest input.

observed
Read directly from the provider's official page or API.
inferred
Mathematically derived from observed figures (e.g. annual ÷ 12).
assumed
A reasonable assumption, not yet verified from an official source.
stale
Was observed, but the source is now more than 90 days old.
unknown
Could not be determined; the value is null and displays as "—".

Price bands

  • free$0/mo
  • low$0.01–$30/mo
  • mid$30.01–$80/mo
  • high$80.01+/mo

Limitations

  • Usage limits are estimates derived from disclosed plan terms — not guaranteed allowances. Real-world usage varies with prompt size and task type.
  • AA benchmark snapshots are fetched weekly; a snapshot older than 14 days is flagged on the model card.
  • Models without an AA profile have no Intelligence Score and no Value per Intelligence per Task (shown as "—").
  • Pricing is manually verified per provider; see each plan's source link and verification date.

See the data freshness page for source dates and stale-data warnings.