AllocateDeepSeek R1 0528 NVFP4 vs DeepSeek V4
On provider list prices, DeepSeek V4 costs $1.74 per million input tokens against $3 for DeepSeek R1 0528 NVFP4: 1.7x apart. Output is $3.48 against $7 (2.0x). On Allocate both bill at list plus the 7% transaction fee.
DeepSeek R1 0528 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 $3,306 a month on DeepSeek V4 and $6,050 on DeepSeek R1 0528 NVFP4 at list: a gap of $2,744, or 1.8x.
DeepSeek V4 reads 512K tokens per request against 160K for DeepSeek R1 0528 NVFP4, 3.1x the window. That decides which one can take whole documents without splitting them.
Choose DeepSeek R1 0528 NVFP4 for
- 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 R1 0528 NVFP4 or DeepSeek V4?
DeepSeek V4, on this workload shape. At list prices it is $1.74/$3.48 per million tokens in and out against $3/$7 for DeepSeek R1 0528 NVFP4. Billed on Allocate: $1.86/$3.72 against $3.21/$7.49, list plus 7%.
Which has the bigger context window?
DeepSeek V4: 512,000 tokens (512K) against 163,840 (160K) for DeepSeek R1 0528 NVFP4.
Can I fine-tune DeepSeek R1 0528 NVFP4 or DeepSeek V4?
DeepSeek R1 0528 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.