Costra

AI Cost Navigator

Describe a use case, size the tokens, rank the models and see cost per outcome — one flow, one login.

Costra AI Cost Navigator

Size your AI workload, we'll guide you through

Describe the use case, size the tokens, weigh what matters, pick a model and see cost per outcome — low / base / high — with the tuning levers that decide what a successful outcome really costs.

1 · Use case2 · Priorities 3 · Model & volume4 · Business case5 · Export
1

Describe the use case

NameiShort working name; appears in the BOM and the architecture document.
ArchetypeiPick the shape of the workload. Each archetype has its own questions, formulas and components — and its own Big-T class (how cost scales).
Outcome unitiThe thing the business gets. Cost is reported per unit of this — not per token.
Where is it counted?iThe system that counts outcomes. No count source, no unit economics.
Quality floor (what counts as a valued outcome)iWhen does an output count? Without a floor you count attempts, and cost per outcome looks better while quality drops.

Parameters

2

Priorities

What matters for this workload. Starts from the archetype's usual profile — override anything. Every weighted category below drives which model gets priced (step 3), not just the table's sort order.

Priority preset

Weights

3

Model & volume

Size the tokens, then the best fit for this workload is ranked and priced automatically below — click any row to price that model instead.

Token profile — low / base / high vary tokens-per-word, retries and cache hit. Click one to make it the active scenario — it drives everything below.

Filters

Hard floor from step 2's priorities — can't go lower. Slide up to require a smarter (usually pricier) model.

Ceiling at today's token volume. Leave blank for no ceiling.

Pick 1–3 providers for a head-to-head. no model data
Fit score vs. monthly cost (chart)

Top-left is the sweet spot. Cost axis is logarithmic.

How the fit score works
  • Each metric is scaled to 0–100 across all models that report it. Indices are scaled linearly; price, cost per task, speed and latency span orders of magnitude and are scaled on a log basis.
  • Fit score = weighted average of the scaled metrics. With "only complete data" off, missing metrics are skipped and remaining weights re-normalized (marked "partial").
  • Monthly cost here uses this use case's own sized tokens above, not a generic workload.
Or set a price manually
input $/1M
output $/1M
cached input $/1M
4

Business case

Sizing → model → what it's worth. Model + embeddings only — infra via the Azure estimator, labour via the ledger.

Model

Bill of materials (base scenario)

ComponentRoleSKU hintQuantityUnitSource

Business case — before vs. after the optimization levers below

Before tuning vs. the manual baseline from step 1

After tuning with the levers below applied

Optimization levers — what-ifs on top of the priced model above

What if more of the repeated prompt came from cache?

What if each call sent less history or fewer documents?

What if answers were shorter?

Agentic archetype only — stops runaway loops.

Total cost of AI includes infra, tooling and people around the model call — tokens are typically only 10–25% of it. Replace with your own figures when known. Only fill in "extra value" if AI creates value beyond replacing the manual baseline above (e.g. it does more, or faster than the business case above already counts) — otherwise leave it blank.

Unit economics: today vs. optimized

5

Export

The full business case — use case, model, BOM, KPIs before/after tuning, unit economics and assumptions.
More export options
Data: Artificial Analysis · free tier, refreshed every 6 hours · formulas: Costra spec v0.1 COSTRA