AllocateDeepseek V3.1 NVFP4 vs DeepSeek V4
On provider list prices, Deepseek V3.1 NVFP4 costs $0.60 per million input tokens against $1.74 for DeepSeek V4: 2.9x apart. Output is $1.70 against $3.48 (2.0x). On Allocate both bill at list plus the 7% transaction fee.
Deepseek V3.1 NVFP4 DeepSeek V4Specifications and provider list prices from the Allocate catalog, checked 2026-07-08. Billed price is list plus the 7% transaction fee.
What the numbers say
Take 1,000,000 requests a month at 1,200 input and 350 output tokens each. That workload costs $1,315 a month on Deepseek V3.1 NVFP4 and $3,306 on DeepSeek V4 at list: a gap of $1,991, or 2.5x.
DeepSeek V4 reads 512K tokens per request against 128K for Deepseek V3.1 NVFP4, 3.9x the window. That decides which one can take whole documents without splitting them.
Choose Deepseek V3.1 NVFP4 for
- The lower list price ($0.60 in / $1.70 out per M tokens)
- Open weights you can fine-tune and own
- Fine-tuning under a permissive license (MIT)
Choose DeepSeek V4 for
- Reasoning-heavy agents
- Long-document analysis
- Cost-sensitive production routes
Common questions
Which is cheaper, Deepseek V3.1 NVFP4 or DeepSeek V4?
Deepseek V3.1 NVFP4, on this workload shape. At list prices it is $0.60/$1.70 per million tokens in and out against $1.74/$3.48 for DeepSeek V4. Billed on Allocate: $0.64/$1.82 against $1.86/$3.72, list plus 7%.
Which has the bigger context window?
DeepSeek V4: 512,000 tokens (512K) against 131,072 (128K) for Deepseek V3.1 NVFP4.
Can I fine-tune Deepseek V3.1 NVFP4 or DeepSeek V4?
Deepseek V3.1 NVFP4 publishes open weights (MIT) and can be fine-tuned on your own data. DeepSeek V4 is a closed model served over API; its weights are not available.
Related comparisons
Run the numbers on your workload
Or don’t choose. On Allocate a route name is the contract: point yours at one model today, swap to the other tomorrow, and compare them on your live traffic with per-token metering.