Legacy compatibility id mapping to DeepSeek V4 Flash thinking mode (per DeepSeek pricing notes).
Model details →DeepSeek Reasoner (legacy id) vs o1
DeepSeek Reasoner (legacy id) wins on 1 of 6 axes — pricing and capability skew in its favour for most workloads.
Reasoning-focused model for complex planning and math tasks.
Model details →Side-by-side comparison
| Capability | DeepSeek Reasoner (legacy id) | o1 | Winner |
|---|---|---|---|
| Context window Maximum number of input tokens the model can attend to in a single request. | 1M | 200K | 🏆 DeepSeek Reasoner (legacy id) |
| Input price (per 1M) Cost per million input tokens billed by the provider. | Custom | Custom | — |
| Output price (per 1M) Cost per million output tokens billed by the provider. | Custom | Custom | — |
| Tool / function calling First-class support for emitting structured tool calls. | — | — | Tie |
| Vision input Accepts image inputs alongside text. | — | — | Tie |
| Reasoning mode Internal chain-of-thought / extended-thinking support. | — | — | Tie |
Frequently asked questions
Is DeepSeek Reasoner (legacy id) better than o1?
DeepSeek Reasoner (legacy id) wins on 1 of 6 axes — pricing and capability skew in its favour for most workloads.
What's the price difference between DeepSeek Reasoner (legacy id) and o1?
Input: Custom vs Custom per 1M tokens. Output: Custom vs Custom per 1M tokens.
What context windows do DeepSeek Reasoner (legacy id) and o1 support?
DeepSeek Reasoner (legacy id) supports up to 1M tokens. o1 supports up to 200K tokens.
Do both DeepSeek Reasoner (legacy id) and o1 support tool calling?
DeepSeek Reasoner (legacy id): not advertised. o1: not advertised.