o10Last updated 2026-07-26

The Quality-Cost Frontier Index

What it actually costs, this month, to clear a quality bar — measured across real routed traffic and tune runs, per task type.

Research · As of July 2026

Dashboards observe.
o10 enforces.

Cost dashboards tell you what you spent. o10 sits in the request path and changes what you spend — shadow first, then enforce.

SummaryKey takeaways

What you need to know

Short, self-contained answers with cited stats — read the sections below for full context.

What does it cost to run AI at a given quality bar?

The Quality-Cost Frontier Index answers that per task type: the cheapest model that clears a stated quality bar (0.74 / 0.86 / 0.93) and its measured cost per 1K calls — with observation and org counts on every real row.

2 measured cells for July 2026.

What is never collected for this index?

Prompt content. The index is metrics-only with k-anonymity minimums on observations and orgs before a cell publishes.

No prompts · k-anonymity thresholds · public citation target

How does this relate to o10’s product?

o10 holds your quality floor in the request path and routes each call to the cheapest model that clears it. The index is the public, aggregatable expression of that underwriting — savings are the consequence of clearing the bar cheaper, not a claim without proof.

01Deep dive

Methodology

How a cell enters the index — and what never does.

Quality is holdout-scored on customer-supplied examples (Tune) and enforced via eval-gated live routing. A model is listed as cheapest-clearing only when it empirically clears the stated quality bar.

Publishing requires k-anonymity minimums: both observation_count and org_count must clear internal thresholds before a cell appears. Prompt content is never collected for this index.

Costs are reported as USD per 1K calls for the clearing model at that task type × quality bar. Periods are calendar months unless the API specifies otherwise.

  • Holdout-scored evals on customer-supplied examples
  • Eval-gated live routing receipts
  • K-anonymity: observation + org thresholds
  • No prompt content collected for the index
SourceMethodology

Source: https://app.o10.io/api/frontier-index. Page resolves live fetch → last cached period → ILLUSTRATIVE methodology preview. Never present sample rows as measured.

IndexAs of July 2026

Task type × quality bar

Cheapest clearing model and cost per 1K calls — measured aggregates. Every row shows observation_count and org_count.

Measured · July 2026 · quality bars 0.74 / 0.86 / 0.93
Task type Quality bar Cheapest clearing model $/1K calls n (obs) Orgs
classification 0.86 llama-3.1-8b $0.420 128 7
codegen 0.93 deepseek-v4-pro $1.15 64 5

How to cite: o10 Quality-Cost Frontier Index, July 2026. Canonical: www.o10.io/research/quality-cost-frontier-index. Distribution: https://app.o10.io/api/frontier-index.

FAQFrequently asked questions

Common questions

What is the Quality-Cost Frontier Index?

A privacy-safe monthly dataset from o10: for each task type and quality bar, the cheapest model that empirically clears the bar and its cost per 1K calls, with observation_count and org_count. It is designed to be cited — not a marketing estimate.

What data does o10 collect for the index?

Metrics only: task type, quality bar, clearing model, cost per 1K calls, and k-anonymized observation/org counts. No prompt content is collected for this index. Rows publish only when observation and org thresholds clear.

How does o10 measure quality for the index?

Holdout-scored evals on customer-supplied examples (Tune) and eval-gated live routing receipts. A model only appears as cheapest-clearing when it empirically clears the bar at that quality threshold.

Is this page showing live measured data?

Yes for period 2026-07 (As of July 2026). Every row shows observation_count and org_count. Source: live.

How should I cite the index?

Use: “o10 Quality-Cost Frontier Index, July 2026”. Canonical page: https://www.o10.io/research/quality-cost-frontier-index. Machine-readable distribution: https://app.o10.io/api/frontier-index.

o10Set the envelope. o10 holds it.

See what you're overpaying.

Paste a week of traffic. Get the number that books the audit.

See what you're overpaying
verified savings methodology · State of Inference Spend 2026