- Estimated capacity / month
- 2.2B
- CP value
- 27.1
Works well?
Use in calculator ↗Read the limits in order
Read the windows before the model table
Token capacity in each model row is a conversion. What you can actually use is first shaped by these three windows and the plan allowance.
- 01 $12
Rolling 5 hours
A rolling five-hour window; concentrated usage can reach this ceiling first.
- 02 $30
Rolling week
A rolling weekly window with its own ceiling; concentrated usage may reach it before the monthly allowance.
- 03 $60
Monthly plan limit
The plan monthly ceiling; each model’s usage-equivalent follows its own reference row.
- Model options
- 29
- Free models
- 2
02Complete model index
Every model, in one working table
All 29 options are listed here. Search, calculate the same workload, or open a model detail page.
Current comparison
Same workload · 12,000 tokens/request · 83% cache readHigher CP means more Coding score for the same cost.
| Select | Works well? | Next | ||||
|---|---|---|---|---|---|---|
| 2.2B | 27.1 | 72.2 | Calculate ↗ | |||
| 2.2B | 28.6 | 76.3 | Calculate ↗ | |||
| 1.6B | 15.2 | 56.8 | Calculate ↗ | |||
| 1.6B | — | — | Calculate ↗ | |||
| 1.2B | — | — | Calculate ↗ | |||
| 757.9M | 9.0 | 71.5 | Calculate ↗ | |||
| 672.9M | 6.6 | 58.8 | Calculate ↗ | |||
| 461.5M | 3.5 | 45.3 | Calculate ↗ | |||
| 461.5M | — | — | Calculate ↗ | |||
| 342.9M | 3.3 | 58.6 | Calculate ↗ | |||
| 300.0M | 2.8 | 55.9 | Calculate ↗ | |||
| 266.7M | — | — | Calculate ↗ | |||
| 257.1M | — | — | Calculate ↗ | |||
| 257.1M | — | — | Calculate ↗ | |||
| 134.2M | 5.4 | 60.2 | Calculate ↗ | |||
| 134.2M | — | — | Calculate ↗ | |||
| 112.5M | 5.4 | 71.4 | Calculate ↗ | |||
| 105.1M | 1.1 | 60.8 | Calculate ↗ | |||
| 95.9M | — | — | Calculate ↗ | |||
| 85.7M | 1.0 | 68.8 | Calculate ↗ | |||
| 62.9M | 2.9 | 68.8 | Calculate ↗ | |||
| 38.3M | — | — | Calculate ↗ | |||
| 21.4M | 1.1 | 74.8 | Calculate ↗ | |||
| 17.1M | 0.8 | 71.8 | Calculate ↗ | |||
| 13.8M | — | — | Calculate ↗ | |||
| 13.8M | — | — | Calculate ↗ | |||
| 8.6M | 0.4 | 76.2 | Calculate ↗ | |||
| — | — | — | Calculate ↗ | |||
| — | — | — | Calculate ↗ |
- Estimated capacity / month
- 2.2B
- CP value
- 28.6
Works well?
Use in calculator ↗- Estimated capacity / month
- 1.6B
- CP value
- 15.2
Works well?
Use in calculator ↗- Estimated capacity / month
- 1.6B
- CP value
- —
Works well?
Use in calculator ↗- Estimated capacity / month
- 1.2B
- CP value
- —
Works well?
Use in calculator ↗- Estimated capacity / month
- 757.9M
- CP value
- 9.0
Works well?
Use in calculator ↗03Free models
Free access still has conditions
Free models do not consume model allowance, but start-up credits and plan or capacity conditions may still apply; see the official plan document. Official source ↗
Free for a limited time.
Free for a limited time; unavailable in some regions. The provider does not train on your data and retains it for 30 days for safety.
04Billing conditions
Conditions to read with the plan limits
These conditions affect plan choice and usage estimates.
- 01
How model allowances and shared plan pools work
Command Code GOAT uses one shared credit pool; OpenCode Go lists a usage equivalent for each model. Model allowances cannot be added together as plan capacity.
- 02
Per-request usage changes the available count
The reference request is an estimate basis. Five-hour and weekly windows limit concentrated use; Command Code GOAT rolls its window from the first request.
- 03
Peak windows and context tiers change the cost
DeepSeek has UTC peak pricing, and some OpenCode models switch to another price set above a context threshold. The reference profile sits in ordinary short context and does not blend every context branch into one number.
- 04
Included capacity and purchased credits
Command pay-as-you-go credits are not bound by the windows, and OpenCode's Use balance may fall back to Zen balance after the Go limits. Both are listed separately from included capacity.
- 05
Model lists and prices are updated
Official documentation can change its model list or prices. This page shows the current data date; comparable later snapshots will be listed in the update history.