Side-by-side comparison
DeepSeek V3.2 vs Command R (08-2024)
Cohere
Command R (08-2024)
🔧 Tools
{} JSON
Input / 1M
$0.1500
Output / 1M
$0.6000
| DeepSeek V3.2 | Command R (08-2024) | |
|---|---|---|
| Provider | DeepSeek | Cohere |
| Context window Maximum tokens (input + output) the model can process in a single request. Glossary → | 131,072 | 128,000 |
| Capabilities Optional capabilities the model advertises: vision (images), tools (function calling), json_mode (structured output). | tools, json_mode | tools, json_mode |
| Input $ / 1M tokens Cost for tokens you send (prompt + context). Cheaper side highlighted. Glossary → | 0.2520 | 0.1500 |
| Output $ / 1M tokens Cost for tokens the model generates. Output is normally 3–5× pricier than input. Glossary → | 0.3780 | 0.6000 |
Frequently asked questions
Which is cheaper, DeepSeek V3.2 or Command R (08-2024)?
DeepSeek V3.2 is cheaper than Command R (08-2024) on a 50/50 input/output blend by about $0.06 per 1M tokens. Exact savings depend on your input-vs-output ratio — use the cost calculator on this page for a workload-specific estimate.
Which has a larger context window, DeepSeek V3.2 or Command R (08-2024)?
DeepSeek V3.2 has the larger context window at 131k tokens versus 128k tokens for Command R (08-2024). That means DeepSeek V3.2 can ingest about 1.0x as much text per request.
What is the difference between DeepSeek V3.2 and Command R (08-2024)?
DeepSeek V3.2 comes from DeepSeek; Command R (08-2024) comes from Cohere. They differ in pricing, context window, and supported capabilities — see the side-by-side table on this page for the exact figures, refreshed nightly.