Headline margin
The headline pools an equal one-million-token workload for every quoted model; it is not traffic-weighted because provider traffic shares are unavailable. A negative headline does not mean every model is negative.
margin = (API revenue − modeled GPU cost) ÷ API revenue
API revenue
OpenRouter uses the cheapest live endpoint with matching precision and at least 95% one-day uptime. Revenue blends standard input/output prices at the configured token mix. AIHubMix and SiliconFlow use their cheapest listed matching quote.
revenue = 80% input price + 20% output price
GPU cost
Each model gets its own capacity-weighted blend of qualified live rental stock. Eligible cards need a public price, measured Gn, compatible weights, and room for one full advertised-context KV/state cache.
cost = rent × 1.10 overhead ÷ throughput ÷ 70% billable utilization
Gn delivery gap
Calibrated capacity is the measured BF16 dense-compute reference for one H100-equivalent hour. Benchmark-realized work converts the matched model's best measured input/output serving rates into Gn using its 2 × active-parameter sticker and the declared token mix.
gap = 1 − benchmark-realized Gₙ/hour ÷ calibrated Gₙ/hourExample: an 84.27% gap means the benchmark delivered 15.73% of calibrated capacity as model-token work. The remainder reflects model/runtime delivery limits such as memory movement, attention, KV-cache traffic, kernel shapes, and serial decode. It is not 84.27% GPU idle time and does not measure production fleet utilization or idle lease time.
Prompt caching
Not included in the headline. The table compares published route-level input, cache-read, and cache-write prices. Missing cache prices stay unavailable, never zero. Hit-rate rows blend cold input and steady-state reads; they exclude initial writes, TTL/eviction, and reuse distribution because providers do not publish a traffic-wide hit share. Warm self-host cost appears only after the exact model, quantization, GPU, full context, repeated prefix, and vLLM cache counters are measured.
read discount = 1 − cache-read price ÷ input price
effective input = (1 − hit share) × input + hit share × cache read
Why API prices can be lower
Our cost basis is public on-demand rental economics. API providers may own or reserve hardware, use TPUs or undisclosed GPUs, batch more requests, sustain higher utilization, reuse prefixes, or price below public rental cost. This is not asserted to be like-for-like hardware.
Evidence and uncertainty
Loading benchmark coverage…
Full-context session counts are memory ceilings, not measured concurrency. Sensitivity ranges vary efficiency, utilization, and overhead; they are not confidence intervals. AIHubMix units remain unvalidated.