
DeepSeek V4 went officially GA on July 13, 2026. If you've been running DeepSeek V4-Pro or V4-Flash in production, your costs just became time-of-day dependent — and if you haven't structured your batch workloads around that, you're probably overpaying by 50% right now.
The GA isn't a new model. V4-Pro and V4-Flash have been available via API since the April 2026 preview launch. What shipped on July 13 is the official production pricing, a deprecation notice for legacy model names (deepseek-chat and deepseek-reasoner go dark July 24), and a new tiered rate structure that charges by the hour.
The peak/off-peak structure:
| Period | Rate Multiplier | V4-Pro input | V4-Pro output |
|---|---|---|---|
| Peak (9–12am, 2–6pm Beijing) | 2x | $0.87/M tokens | $1.74/M tokens |
| Off-peak | 1x | $0.435/M tokens | $0.87/M tokens |
V4-Flash sits at $0.14/M input off-peak and $0.28/M peak. The gap is real and it's not cosmetic.
Here's the number that matters: DeepSeek V4-Pro at off-peak rates does about 90% of everyday tasks at roughly 1.5% of Anthropic Claude Fable 5's cost. That's not a discount. That's a different pricing tier.
Run that through a calculator for a moderate-size production workload — 10 million input tokens and 2 million output tokens per day, all during business hours:
# Daily cost at peak rates (worst case)
peak_input_cost = 10_000_000 * (0.87 / 1_000_000) # $8.70
peak_output_cost = 2_000_000 * (1.74 / 1_000_000) # $3.48
print(f"Peak: ${peak_input_cost + peak_output_cost:.2f}/day")
# Peak: $12.18/day
# Same tokens, all off-peak
offpeak_input_cost = 10_000_000 * (0.435 / 1_000_000) # $4.35
offpeak_output_cost = 2_000_000 * (0.87 / 1_000_000) # $1.74
print(f"Off-peak: ${offpeak_input_cost + offpeak_output_cost:.2f}/day")
# Off-peak: $6.09/day
# Claude Fable 5 equivalent (~$10/M in, ~$15/M out)
fable_input = 10_000_000 * (10 / 1_000_000) # $100
fable_output = 2_000_000 * (15 / 1_000_000) # $30
print(f"Fable 5 equivalent: ${fable_input + fable_output:.2f}/day")
# Fable 5 equivalent: $130.00/dayDeepSeek V4-Pro off-peak is 21x cheaper than Fable 5 for equivalent token volumes. At peak rates, it's still 10x cheaper.
Before you restructure your entire inference pipeline around off-peak scheduling, note this: alongside the GA, DeepSeek shipped DSpark — their speculative decoding framework that boosts V4-Flash generation speed by up to 85% without any hardware changes. DSpark is available now and it matters because it effectively reduces output token costs per useful response, not just per token.
For agentic coding workflows that burn through output tokens (each tool call cycle is a new output token batch), a 85% generation speedup on V4-Flash changes the cost-per-solved-task calculus further in DeepSeek's favor.
Every major LLM API vendor has been selling compute at flat rates. That's unusual for cloud infrastructure — AWS, GCP, and Azure have had tiered compute pricing for decades based on time-of-day demand. LLMs have been insulated from this because the GPU cluster economics didn't map neatly to demand curves. DeepSeek is the first frontier-model provider to explicitly say: we have more demand than compute capacity during business hours in Beijing, and we're going to price it accordingly.
This is the beginning of the end for flat-rate LLM pricing. If DeepSeek's peak/off-peak structure holds and competitors don't match it, two things will happen:
1. Production workloads will route to off-peak windows — which means the highest-value, most latency-sensitive traffic stays on peak, and the economics of batch processing migrate. This is rational but it changes who pays what.
2. Reseller intermediaries will offer flat-rate wrappers — services that aggregate DeepSeek API capacity and sell flat-rate access with no time multiplier. AiCredits and similar already do this. They'll capture margin on peak-hour users who don't want bill variability.
The DeepSeek V4 model itself is not news — it's been available since April and it's been strong. The GA is notable for exactly one reason: the pricing model. And it's a genuinely important move.
We spent two years treating LLM API pricing as a solved problem. Pick a model, pay per token, done. DeepSeek just introduced the thing that every cloud infrastructure team already knows: demand curves are real, and compute has peak hours. Whether you think this is fair depends on whether you think GPU clusters should behave like AWS instances.
The practical advice is simpler than the debate: if you're running batch workloads on DeepSeek V4 and you're not scheduling them for off-peak windows, you're lighting money on fire. The savings are material — 50% of your API bill, in some architectures. Move the work, or find a reseller with flat rates.
The deeper signal is that the LLM API market is maturing fast. Flat rates were a feature of an immature market. They're going away.
Model: DeepSeek V4-Pro and DeepSeek V4-Flash (GA, July 13, 2026) Pricing: V4-Pro: $0.435/$0.87 per 1M tokens (off-peak/peak input/output). V4-Flash: $0.14/$0.28 per 1M tokens. Peak hours: 9–12am and 2–6pm Beijing time (UTC+8), 2x multiplier. Context window: 1M tokens Key additions: Peak/off-peak pricing, DSpark speculative decoding (up to 85% generation speedup on V4-Flash), legacy model deprecation path Legacy deprecation: July 24, 2026 (deepseek-chat and deepseek-reasoner sunset) Cost comparison: V4-Pro off-peak ≈ 1.5% of Claude Fable 5 cost per equivalent task; V4-Pro peak ≈ 3%