DeepSeek: R1 (DeepSeek) ile DeepSeek: DeepSeek V3.2 (DeepSeek) modellerini fiyat, baglam, yetenekler ve gecikme acisindan karsilastirin.
Yan yana
Fiyat, saglayici, baglam, yetenekler, gecikme ve kaynak temelini karsilastirin.
| 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: DeepSeek V3.2deepseek/deepseek-v3.2 | DeepSeek | $0.043 / 1M tokens | $0.065 / 1M tokens | 163.8k | StreamingTool callingJSON modeLong context | Chinese Q&A, general chat | 1000-3000ms | Catalog | Platform curated |
FAQ
DeepSeek: DeepSeek V3.2, DeepSeek: R1 modeline gore daha ucuzdur ($0.043 / 1M tokens input / $0.065 / 1M tokens output vs $0.132 / 1M tokens input / $0.47 / 1M tokens output). Gercek maliyet, giris ve cikis token karisiminiza baglidir; bu nedenle fiyat hesaplayici ile gercek trafik uzerinden tahmin yapin.
Her iki model de ayni baglam penceresini sunar: 163.8k token.
Her iki model de Long context icin uygundur. Maliyet oncelikliyse DeepSeek: DeepSeek V3.2, daha genis baglam gerekiyorsa DeepSeek: R1 secin. Uretim trafigini yonlendirmeden once ikisini de gercek promptlarla test edin.