Compare DeepSeek: R1 (DeepSeek) and DeepSeek: R1 0528 (DeepSeek) by price, context, capabilities, and latency.
Lado a lado
Compara precio, proveedor, contexto, capacidades, latencia y base de la fuente.
| Model | Provider | Input | Output | Context | Capabilities | Best for | Latency | Status | Source |
|---|---|---|---|---|---|---|---|---|---|
| DeepSeek: R1deepseek/deepseek-r1 | DeepSeek | $0.132 / 1M tokens | $0.47 / 1M tokens | 163.8k | StreamingTool callingJSON modeLong context | Chinese Q&A, general chat | 1000-3000ms | Catalog | Platform curated |
| DeepSeek: R1 0528deepseek/deepseek-r1-0528 | DeepSeek | $0.094 / 1M tokens | $0.405 / 1M tokens | 163.8k | StreamingTool callingJSON modeLong context | Chinese Q&A, general chat | 1000-3000ms | Catalog | Platform curated |
FAQ
DeepSeek: R1 0528 is cheaper ($0.094 / 1M tokens input / $0.405 / 1M tokens output) vs DeepSeek: R1 ($0.132 / 1M tokens input / $0.47 / 1M tokens output). Actual cost depends on your input/output token mix — estimate it with the pricing calculator.
Both offer the same context window: 163.8k tokens.
Both target Long context. Pick DeepSeek: R1 0528 to optimize cost, or DeepSeek: R1 for the longer context window. Test both on real prompts before committing production traffic.