Models and prices
The models Orbital suggests for each agent, their reference prices, and how to set your own
Look up the models Orbital suggests for each harness and the reference price it uses for each. The model picker offers these models, and the run’s Cost tab uses the prices to estimate what a run cost. A model on this list is only a suggestion: your harness and your plan decide whether it runs.
Suggested models and reference prices
Section titled “Suggested models and reference prices”Prices are USD per million standard input and output tokens. The list was checked on 29 September 2026. OpenCode model names start with the provider, such as anthropic/. Run /models in OpenCode to see the models you have set up.
| Harness | Exact model name | Input | Output |
|---|---|---|---|
| claude | claude-fable-5-1 |
$10 | $50 |
| claude | claude-mythos-5-1 |
$10 | $50 |
| claude | claude-fable-5 |
$10 | $50 |
| claude | claude-mythos-5 |
$10 | $50 |
| claude | claude-opus-5-5 |
$4 | $20 |
| claude | claude-opus-5 |
$5 | $25 |
| claude | claude-opus-4-8 |
$5 | $25 |
| claude | claude-opus-4-7 |
$5 | $25 |
| claude | claude-opus-4-6 |
$5 | $25 |
| claude | claude-sonnet-5-5 |
$2 | $10 |
| claude | claude-sonnet-5 |
$2 | $10 |
| claude | claude-sonnet-4-6 |
$3 | $15 |
| claude | claude-haiku-5-5 |
$0.10 | $0.50 |
| claude | claude-haiku-4-5-20251001 |
$1 | $5 |
| codex | gpt-6-astra |
$10 | $50 |
| codex | gpt-6-sol |
$2 | $10 |
| codex | gpt-6-luna |
$0.10 | $0.50 |
| codex | gpt-5.6-sol |
$4 | $20 |
| codex | gpt-5.6-terra |
$2 | $12 |
| codex | gpt-5.6-luna |
$0.20 | $1.20 |
| codex | gpt-5.5 |
$5 | $30 |
| codex | gpt-5.5-pro |
$30 | $180 |
| codex | gpt-5.4 |
$2.50 | $15 |
| codex | gpt-5.4-mini |
$0.75 | $4.50 |
| codex | gpt-5.4-nano |
$0.20 | $1.25 |
| codex | gpt-5.4-pro |
$30 | $180 |
| codex | gpt-5.3-codex |
$1.75 | $14 |
| codex | gpt-5.3-codex-spark |
Unknown | Unknown |
| codex | gpt-5.2 |
$1.75 | $14 |
| codex | gpt-5.2-pro |
$21 | $168 |
| codex | gpt-5.1 |
$1.25 | $10 |
| codex | gpt-5 |
$1.25 | $10 |
| codex | gpt-5-mini |
$0.25 | $2 |
| codex | gpt-5-nano |
$0.05 | $0.40 |
| codex | gpt-5-pro |
$15 | $120 |
| opencode | anthropic/claude-sonnet-4-5-20250929 |
$3 | $15 |
| opencode | lmstudio/google/gemma-3n-e4b |
Unknown | Unknown |
Sources: Claude model names, Claude prices, Sonnet 5.5 announcement, OpenAI models, OpenAI prices, Codex models and OpenCode model configuration. Sonnet 5.5 cache reads cost $0.20 and 5-minute cache writes cost $2.50 per million tokens. Spark has no published price we could check. The local LM Studio model runs on your own machine, so it has no hosted price.
Who can use which model
Section titled “Who can use which model”A price does not mean you can use the model. Claude Mythos 5.1 and Claude Mythos 5 are open only to organisations approved for Project Glasswing. Codex lists GPT-6 Astra, GPT-6 Sol, GPT-6 Luna, the GPT-5.6 models, Spark and GPT-5.5. GPT-5.5 leaves Codex on 14 October 2026. GPT-5.4 and GPT-5.4 mini left Codex for ChatGPT sign-in on 31 August 2026, and Codex has deprecated GPT-5.2 and GPT-5.3 Codex. The other GPT-5 models have prices on the OpenAI API but are not on the Codex models page, so whether they run depends on your Codex. Anthropic keeps Claude Haiku 4.5 available until at least 15 October 2026.
How Orbital prices a run
Section titled “How Orbital prices a run”Orbital prices each turn by the model the harness reported it ran on. That is the full model name an alias such as opus stood for, or the harness’s own default when nothing chose a model. When a harness reported no model, as in turns recorded before harnesses reported one, Orbital uses the model the turn asked for and marks it (configured). The Tokens by model table on the run’s Cost tab keeps those configured models in rows of their own. A turn with neither model shows as Unknown model and has no price. A step that ran no agent turn, such as a command, shows no model.
Orbital needs separate input and output token counts to work out a cost. A model with no known price stays unpriced; Orbital does not count it as free.
How sub-agents count
Section titled “How sub-agents count”Orbital counts a sub-agent’s tokens once, priced by the model the sub-agent ran on. Each harness reports sub-agent usage differently:
- Codex reports each thread’s usage separately, so a thread’s totals leave out its sub-agents. Orbital adds the usage of every thread the turn’s thread spawned or works with through a collaboration call, including nested sub-agents and ones a later turn resumes. It counts a sub-agent’s usage only for the turns it runs while Orbital watches; usage Codex replays from earlier turns only moves its running total on, and a running total the same turn reports again counts once. It ignores other threads on the same Codex server.
- OpenCode runs each sub-agent in a child session that reports its own steps. Orbital adds the steps of every session the turn’s session created or named in a
taskcall, including nested sub-agents and ones a later turn resumes. It prices each step by the model its start named, matched by the step’s message, so a step OpenCode replays neither changes another step’s model nor settles its work. It ignores other sessions on the same OpenCode server. - Claude Code reports the main agent’s usage on its own. Each result also gives the session’s running total for every model, sub-agents included. Orbital counts what each result adds to the session’s previous totals, beyond the main agent’s own usage, under the model that spent it, and counts a result the CLI sends again once. Claude Code does not split those tokens into 5-minute and 1-hour cache writes. A model priced only by those two rates therefore shows that part of the cost as incomplete.
The Cost tab marks a step’s cost incomplete, rather than leaving sub-agent spend out without saying so, when:
- a Codex sub-agent has not said all it spent by the time the turn ends, because it is still running, was interrupted, reported no usage, or a collaboration call set it working but Codex never said its turn started;
- a Codex sub-agent’s first report gives a running total Orbital has no earlier total for, or its total falls. Orbital counts only the latest call it reports;
- an OpenCode sub-agent that a
taskcall named, or one of its steps, has not said what it spent by the time the turn ends, including a latertaskcall that works in a session whose earlier work Orbital already counted and only replays that earlier work; - a Claude turn started sub-agents but Orbital does not know the session’s earlier totals, which happens when a turn resumes a session that Orbital has not run since it last started;
- a sub-agent did not say which model it ran on. Its tokens still count, but Orbital does not price them as the turn’s model.
Set your own prices
Section titled “Set your own prices”Open Settings > Costs to price a model yourself. Your price replaces the reference price for that exact model name. You can price a model that is not on the list above. Orbital stores only your own prices, so removing one brings back the reference price, if the model has one.
A model name with a provider in front, such as anthropic/claude-sonnet-4-5-20250929, does not share a price with the same model without it. Price each name you use.
What the estimate leaves out
Section titled “What the estimate leaves out”The cost is an estimate, not your provider’s bill. Subscriptions, prompt caching, service tiers, provider routing and long-context rates can all change what you pay. Orbital does not store prices with each run, so a new release with new prices changes the estimates for your old runs too.
Related
Section titled “Related”- Use different models: give each step the model it needs
- Harnesses and models: the coding agents that run each model
- Settings: the Settings > Costs fields and the
modelPriceskey - Watch a run: where the Cost tab shows a run’s estimate