Skip to content

Models and Prices

github-actions[bot] edited this page Nov 18, 2026 · 1 revision

Generated from README.md by scripts/build-wiki.mjs. Edit that file, not this page: an edit here is overwritten by the next build, and a wiki that has drifted from the repository is worse than no wiki.

Every model you pay for by the token

Trazum prices Anthropic, OpenAI, Google, Moonshot, DeepSeek, xAI and Mistral:

Every report says how old the prices are — the date the table was checked and how many days ago that was — because every dollar figure descends from that list, and a date on its own makes you subtract against today to learn whether to trust it. Past 45 days the report says so in a sentence, rather than leaving the reader to decide what "old" means.

The 7 providers publish independently, so each carries its own review date and trazum models prints them; the headline figure above is the oldest of the seven, because the question "how old is this table" is about its worst part.

trazum optimize prompt.txt --model gpt-5 --calls 50000
trazum optimize prompt.txt --model kimi-k3
trazum models                      # the whole table, with each provider's terms

Everything that reads the prompt is provider-agnostic already — the rules, the protection pass, --reorder, the contradiction and example detectors all operate on text. What differs is the money, and that is not one set of numbers:

Cache read 10% of input on OpenAI (5% on GPT-6.1 Sol), Google up to Gemini 3.8 (5% on Gemini 4), Mistral, Moonshot's Kimi K3 and Anthropic up to Opus 5 and Sonnet 5; 17% to 20% on Moonshot's K2 series; per model on xAI, 15% on Grok 4.5, 16% on 4.3 and the 4.20 family, 20% on Build 0.1 and 25% on 4.6 and 4.7. Two providers changed it between generations: Anthropic's Opus 5.5 and Sonnet 5.5 read at 5% and Fable 5.2, Fable 5.1 and their Mythos twins at 2.5%, and DeepSeek V4.1 Flash reads at 2% and V4 Pro at about 3% where V3 read at 10%
Cache write 125% of input on Anthropic and on OpenAI's GPT-5.6 and later, whose entry lives at least 30 minutes; Kimi K3 bills it as its own line by TTL like Anthropic, 100% for five minutes and 200% for an hour; 100% on earlier OpenAI models, Google, Kimi's K2 series, DeepSeek and xAI; Mistral publishes no write price and reports no write tokens
Cache minimum Per model, not per provider. Anthropic alone spans 512 to 4,096; 1,024 on OpenAI and DeepSeek; 4,096 on Gemini 4, Gemini 3.6 Flash, 3.8 Flash and 3.1 Pro and 2,048 on the retired Gemini 2.5 models; Moonshot, xAI and Mistral publish none, nor does Google for Gemini 3.5 Flash-Lite, so their cache is priced from your log and the advice that needs a minimum stays quiet
How caching starts You mark the prefix on Anthropic; it is automatic on OpenAI, Google, Moonshot, DeepSeek and xAI; Mistral does not say, so Trazum gives no caching advice for it
Batch API 50% on Anthropic, OpenAI, Google and Mistral; 40% off on Kimi K2.7 Code and K2.6; 20% off on Grok 4.3 and the 4.20 family; none at all on DeepSeek, Kimi K3 and the rest of xAI
Not one price Claude Haiku 5.5, Gemini 3.1 Pro Preview, OpenAI's GPT-5.6 and later and every current Grok charge each request by its prompt length, dearer over 100,000, 200,000 and 272,000 tokens, and on xAI from exactly 200,000; DeepSeek V4 charges by the clock, half price off-peak. A call is billed in its own band; a usage report's summed row is billed at the dearer rate with the cheaper figure printed beside it. grok-4, retired on 2026-05-15, has billed at Grok 4.3's prices since, and gemini-2.5-pro bills at Gemini 3.8 Flash's from 2026-12-01, when Google routes it there; a log spanning either date is billed both ways

The cache minimum is the row to read twice, and it used to be wrong here. This table said "512 on Anthropic" flatly. Anthropic's floor is a property of the model: 512 on Fable 5.2, Fable 5.1, Fable 5, Mythos 5.2, Mythos 5.1, Mythos 5, Opus 5.5, Opus 5, Sonnet 5.5 and Haiku 5.5; 1,024 on Opus 4.8, Sonnet 5 and Sonnet 4.6; 2,048 on Opus 4.7; 4,096 on Opus 4.6, Opus 4.5 and Haiku 4.5. A reader on Haiku 4.5 who trusted "512" would have built a prefix eight times too short and been told caching would save money that could never arrive — the one direction this tool must never be wrong in. trazum models prints the real figure per model, and every cache advisory has always used it; only this table was wrong.

Those last two rows are why the multipliers had to move onto the model. As global constants they offered a batch discount to providers that do not sell one and a caching saving to a model that has no cache — invented savings, which is the one thing this tool must not print. A provider with no batch API now gets no batch advisory, and no discount even if you tick the box: batchEligible describes the work, not what the provider sells.

A cheaper model means a cheaper model, not a different supplier. The downgrade advisory only ever suggests models from the provider you are already on. Dropping a tier is a one-line change; switching vendor is a migration, and this advisory is a keyword heuristic — it has no business recommending that you change supplier.

Not covered: subscription invoices. API token prices cannot establish how much a subscription bill will change. Claude Code, Codex and Cursor identify the tool, not its payment mode; Trazum defaults to token figures in those hosts. An explicit --cost requests an API-price scenario, not guaranteed invoice savings.

Optimising a prompt that lives in code

trazum optimize src/prompts.ts --prompt support --diff

It reads the marked prompt and leaves the file alone. Pointed at an unmarked source file it refuses, because optimising TypeScript as if it were prose does not produce a worse prompt — it produces broken code, and -o would write that back over your file. When a file holds several marked prompts it asks which one rather than taking the first.

The model comes from the code too, so a file calling OpenAI is priced against OpenAI. --model and trazum.config.json still win: flags beat config, config beats detection, detection beats a built-in default that has no idea which provider you use.

Which provider is this prompt even going to?

Since Trazum prices 7 providers, defaulting to Claude became a wrong number: a file calling OpenAI was billed against Claude Opus 5 without comment. trazum where reads what the code already says.

trazum where src/prompts.ts
Running inside
  Claude Code (CLAUDECODE)
  Claude Code identifies the execution host only. Payment mode is unknown;
  token prices do not establish invoice savings.

Prompts in src/prompts.ts go to
  anthropic · Claude Sonnet 5
    line 2  model-literal: claude-sonnet-5
    line 1  sdk-import: @anthropic-ai/sdk

Priced as
  Claude Sonnet 5 (read from the source)

Every answer names the line it came from. Four kinds of evidence, strongest first: model= on a trazum:prompt marker, a quoted model id, a base URL, an SDK import — and a base URL beats the SDK it was pointed at, because Moonshot, DeepSeek, xAI and Groq are all called through the OpenAI SDK with a different base_url. It refuses when a file names two providers: picking silently is how somebody budgets against the wrong provider for a month. Detection sits in the usual layering — a flag beats config, config beats detection, detection beats the built-in default.

With no file it reports only the host. Environment variables identify the tool, not whether a workload uses an API, a subscription, credits or a local model:

Host Payment mode inferred from environment
Claude Code, Codex, Cursor unknown
GitHub Actions, CI unknown
VS Code, plain terminal unknown

Agent harnesses default to tokens, not invoice savings

Inside Claude Code, Codex or Cursor, Trazum conservatively defaults to token figures. This is a display policy, not a claim about your payment arrangement. Use --cost to request the API-price scenario; it is not a subscription invoice:

What this buys on Claude Code
  Claude Code identifies the tool, not your payment mode. Tokens are shown
  by default; invoice savings are unknown.

  1,001 tokens back, every call.
  Context window: 12.4% → 2.1% of Claude Opus 5's 1,000,000 tokens — room the
  conversation gets instead.
  Pass --cost if this prompt is bound for a metered API.

The context window is the real currency in an agent: every token the system prompt holds is one the conversation cannot.

Advisories whose only pitch is money are hidden in this view. Whether they reduce your invoice depends on your payment arrangement. model-downgrade, batch-api, output-dominated and promo-pricing are dropped; caching, context overflow, contradictions and redundant examples stay, because latency, headroom and correctness are still real.

The escape hatch matters. The host says where Trazum runs, not where your prompt goes — somebody editing a production prompt inside Cursor wants the dollars, and --cost gives them back without leaving the editor. --tokens-only forces the other direction anywhere.

Generated from README.md by scripts/build-wiki.mjs. Edit that file, not this page: an edit here is overwritten by the next build, and a wiki that has drifted from the repository is worse than no wiki.

Trazum

Clone this wiki locally