Side-by-side comparison
R1 0528 vs Devstral Medium
Mistral
Devstral Medium
🔧 Tools
{} JSON
Input / 1M
$0.4000
Output / 1M
$2.0000
| R1 0528 | Devstral Medium | |
|---|---|---|
| Provider | DeepSeek | Mistral |
| Context window Maximum tokens (input + output) the model can process in a single request. Glossary → | 163,840 | 131,072 |
| 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.5000 | 0.4000 |
| Output $ / 1M tokens Cost for tokens the model generates. Output is normally 3–5× pricier than input. Glossary → | 2.1500 | 2.0000 |
Frequently asked questions
Which is cheaper, R1 0528 or Devstral Medium?
Devstral Medium is cheaper than R1 0528 on a 50/50 input/output blend by about $0.125 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, R1 0528 or Devstral Medium?
R1 0528 has the larger context window at 164k tokens versus 131k tokens for Devstral Medium. That means R1 0528 can ingest about 1.3x as much text per request.
What is the difference between R1 0528 and Devstral Medium?
R1 0528 comes from DeepSeek; Devstral Medium comes from Mistral. They differ in pricing, context window, and supported capabilities — see the side-by-side table on this page for the exact figures, refreshed nightly.