DeepSeek V4 Full Release (July 2026): Pricing, Benchmarks & How It Stacks Up Against GPT-5.6
Peak-Valley Pricing × 80.6% SWE-bench × API Migration Deadline July 24

If your production stack still calls deepseek-chat while DeepSeek V4 hits general availability today, you have four days before legacy endpoints go dark. The GA release adds peak-valley API pricing, agent and coding upgrades over the April preview, and an open-weight 80.6% SWE-bench Verified score that leads every MIT-licensed model. This guide is for API engineers and tech leads evaluating V4 against GPT-5.6 and Claude Fable 5. It covers the full release timeline, CSA/HCA/mHC/Muon architecture, benchmark tables, honest model comparison, complete pricing matrix, Python migration code, and a six-step cost playbook.

01

What's New in the GA Release vs. the April Preview?

After three months of preview access, DeepSeek V4 graduates to production today. The underlying MoE architecture is unchanged since the April drop — the GA build is about stability, optimization, and finally committing to a commercial pricing structure. Here is the timeline that got us here.

DateMilestone
Apr 24, 2026V4 preview + MIT open weights: V4-Pro (1.6T) and V4-Flash (284B)
May 2026Production-tuned V4-Flash and V4-Pro; API generally available
Jun 2026V4-Pro output permanently cut 75% to $0.87/M tokens
Jun 29, 2026Email to all API users: GA mid-July + first disclosure of peak-valley pricing
Jul 19, 2026Gray-test access for select developers; media reports "full release imminent"
Jul 20, 2026GA release — today
Jul 24, 2026deepseek-chat and deepseek-reasoner permanently sunset (15:59 UTC)

Why this matters if you are still on legacy endpoints

  1. 01

    Hard cutoff in four days: Any code calling deepseek-chat or deepseek-reasoner will fail after July 24, 15:59 UTC (23:59 Beijing).

  2. 02

    Peak pricing is live: Rates double during Beijing weekday business hours — batch jobs scheduled blindly will surprise finance.

  3. 03

    Agent performance improved: GA tuning targets multi-step agents, math reasoning, and code generation over the April baseline.

  4. 04

    Same model names, new billing: deepseek-v4-pro and deepseek-v4-flash persist; only pricing and legacy aliases change.

  5. 05

    Commercial maturity signal: DeepSeek moves from near-free preview to disciplined peak/off-peak billing — still aggressively cheap, but no longer "ignore the invoice."

  6. 06

    Open weights unchanged: MIT license from April still applies; self-host and hybrid routing remain valid strategies.

The preview was already strong. GA adds agent polish, formal pricing, and a hard migration deadline — not a new architecture.

02

How Does V4 Architecture Make 1M Context Actually Work?

Most LLMs advertise 1M-token windows but choke in production — KV cache memory grows linearly with context length. DeepSeek V4 solves this with a hybrid attention stack, deeper residual paths, and a different training optimizer. Both models in the family share the same design philosophy.

V4-Pro vs V4-Flash at a glance

SpecV4-ProV4-Flash
Total parameters1.6 trillion (1.6T)284 billion (284B)
Active per token49B (3% of total)13B (4.6% of total)
Transformer layers6143
Context window1,000,000 tokens1,000,000 tokens
Max output384K tokens384K tokens
PrecisionFP4 (MoE experts) + FP8 (rest)FP4 + FP8 mixed
Pretraining data33T+ tokens32T+ tokens
LicenseMITMIT

Compressed Sparse Attention (CSA) + Heavily Compressed Attention (HCA)

V4 replaces the Multi-head Latent Attention (MLA) from V2/V3 with two mechanisms that alternate across layers:

  • CSA (Compressed Sparse Attention): Softmax-gated pooling compresses the KV sequence . An FP4 "lightning indexer" selects top-k relevant blocks per query (top-1024 on Pro, top-512 on Flash). A 128-token sliding window preserves recent context.
  • HCA (Heavily Compressed Attention): Compresses tokens 128×, then runs dense global attention to capture long-range dependencies CSA might miss. V4-Flash uses HCA in the first 2 layers, then alternates CSA/HCA; V4-Pro follows a similar pattern.

At 1M tokens, V4-Pro needs only 27% of the inference FLOPs of DeepSeek V3.2. KV cache memory drops to 10% of V3.2 (V4-Flash: 7%). That efficiency gap is what makes million-token serving economically viable.

mHC and Muon: stability at 61 layers

  • mHC (Manifold-Constrained Hyper-Connections): Replaces standard x = x + f(x) residuals with a 4-channel residual stream governed by a doubly stochastic matrix on the Birkhoff polytope. Gradients stay stable through 61 deep layers without sacrificing expressivity.
  • Muon optimizer: Training uses Muon instead of AdamW, applying Newton-Schulz orthogonalization to condition gradient steps — faster convergence and more stable runs at this scale.

Three reasoning modes

ModeBehaviorBest for
Non-thinkNo chain of thought; fastest responseSimple Q&A, routing, classification
Think HighExplicit reasoning in <redacted_thinking> blocksMedium complexity, code debugging
Think MaxMaximum reasoning effort; needs 384K+ contextComplex math, long-chain agents

Official recommended sampling for all modes: temperature=1.0, top_p=1.0.

  • KV cache at 1M: 10% of V3.2 memory on Pro, 7% on Flash — the headline efficiency number.
  • Inference FLOPs at 1M: 27% of V3.2 — not a marginal gain; it changes unit economics.
  • Training corpus: 33T+ tokens (Pro) / 32T+ (Flash) per DeepSeek technical report (arXiv:2606.19348).
03

What Do the Benchmark Numbers Actually Show?

Benchmarks are not destiny, but they frame where V4-Pro wins, where closed models still lead, and where cost changes the decision. SWE-bench Verified tests real GitHub bug fixes — the metric most relevant to coding agents.

BenchmarkDeepSeek V4-ProClaude Fable 5GPT-5.6 UltraClaude Opus 4.8
SWE-bench Verified80.6% (open-weight record)96.0%N/A (not published)~69%
SWE-bench Pro55.4%80.3%78.1%69.2%
LiveCodeBench (Pass@1)93.5%88.1%87.4%83.2%
Codeforces Elo3,206
Terminal-Bench 2.183.9%88.0%85.1%82.7%

80.6% on SWE-bench Verified ties Gemini 3.1 Pro for the best open-weight score — real GitHub repo fixes, not synthetic puzzles. Claude Fable 5 still leads overall at 96% Verified and 80.3% on the harder SWE-bench Pro. V4-Pro owns LiveCodeBench and Codeforces Elo if competitive programming is your workload.

Cost-performance reality check (Artificial Analysis)

On the Strategy & Operations industry index:

  • Claude Fable 5: 50 points, $3.48 per task
  • DeepSeek V4-Pro: 38 points, $0.03 per task
  • DeepSeek V4-Flash: all six index task types stay below $0.04 per task

That is 116× cheaper than Fable 5 for a 24% score gap on that index. Fable 5 costs 116× more but scores only ~31% higher in relative terms. For high-volume production, the math is hard to ignore.

04

DeepSeek V4 vs GPT-5.6 vs Claude Fable 5: Which Should You Pick?

No single model wins every task. Here is an honest positioning map for developers making routing decisions in July 2026.

DimensionDeepSeek V4-ProGPT-5.6 SolClaude Fable 5
Open weights / self-hostYes (MIT)NoNo
1M contextYesNot confirmedYes
Best overall coding (SWE-bench Pro)Second tier (55.4%)Second tier (78.1%)Leads (80.3%)
Best algorithms / mathLiveCodeBench leaderStrong
Output cost (off-peak)$0.87/M tokens~$15/M~$50/M
Output cost (peak)$1.74/M tokens
Data sovereigntyYes (self-host possible)NoNo
Agent orchestrationStrongStrongStrongest

Scenario picker

  • Budget-limited / high-volume / private deploy: V4-Pro or V4-Flash — MIT weights, 1M context, lowest API cost.
  • Absolute best multi-file repo work: Claude Fable 5 — SWE-bench Pro leader; cost is secondary.
  • Complex algorithms + math: GPT-5.6 Sol / Ultra — or V4-Pro if LiveCodeBench leadership matters more than ecosystem lock-in.
  • Terminal / shell agents: GPT-5.6 Sol (85.1% Terminal-Bench 2.1) — also the M365 Copilot default as of July 9.
  • Massive log / document ingestion on a budget: V4-Flash with cache hits at $0.0028/M input.
05

How Does Peak-Valley Pricing Work — and How Do You Cut Your Bill?

The most debated GA change: time-based pricing. Rates double during Beijing weekday peak hours (09:00–12:00 and 14:00–18:00). Off-peak rates match or beat the June permanent price cut.

ModelItemOff-peakPeak
V4-ProInput (cache hit)$0.0035 / 1M tokens
Input (cache miss)$0.435 / 1M tokens$0.87 / 1M
Output$0.87 / 1M tokens$1.74 / 1M
V4-FlashInput (cache hit)$0.0028 / 1M tokens
Input (cache miss)$0.14 / 1M tokens$0.28 / 1M
Output$0.28 / 1M tokens$0.56 / 1M

Even at peak, V4-Pro output at $1.74/M is roughly 8.6× cheaper than Claude Opus 4.8 ($15/M) and GPT-5.6 Sol (~$15/M). Peak surcharges are real; the baseline remains the best value in the market.

Six-step cost playbook

  1. 01

    Schedule batch jobs off-peak: Document processing, labeling, code review pipelines, and nightly reports should run after 18:00 or before 09:00 Beijing time — cut the bill in half.

  2. 02

    Maximize prompt cache hits: Put static system prompts first. V4-Flash cache-hit input is $0.0028/M — effectively free for repeated prefixes.

  3. 03

    Route simple work to Flash: Intent classification, entity extraction, and FAQ routing on V4-Flash; escalate only hard reasoning to V4-Pro. Typical savings: 60–80%.

  4. 04

    Watch billing emails: DeepSeek commits to 24-hour advance notice on pricing changes — keep the account email monitored.

  5. 05

    Compare hybrid stacks: API for peaks plus a fixed execution node often beats API-only at scale. See current tiers on Mac Mini rental rates.

  6. 06

    Finish migration before July 24: Legacy aliases may still route today but will 404 in days — update model strings in CI and staging now.

06

How Do You Migrate Before the July 24 API Deadline?

warning

Deadline: July 24, 2026, 15:59 UTC (23:59 Beijing). Legacy names deepseek-chat and deepseek-reasoner will be permanently disabled.

Old model nameNew equivalentNotes
deepseek-chatdeepseek-v4-flash (non-thinking)Drop-in for most chat workloads
deepseek-reasonerdeepseek-v4-flash (thinking) or deepseek-v4-proUpgrade to Pro for stronger reasoning

OpenAI SDK (Python)

python
# Old (stops working July 24)
response = client.chat.completions.create(
    model="deepseek-chat",
    messages=[{"role": "user", "content": "Hello"}]
)

# New — works now and after July 24
response = client.chat.completions.create(
    model="deepseek-v4-flash",   # or "deepseek-v4-pro"
    messages=[{"role": "user", "content": "Hello"}]
)

# Enable thinking mode (replaces deepseek-reasoner)
response = client.chat.completions.create(
    model="deepseek-v4-pro",
    messages=[{"role": "user", "content": "Solve this step by step..."}],
    extra_body={
        "thinking": {"type": "enabled", "budget_tokens": 8000}
    }
)

Anthropic SDK

V4 supports both OpenAI ChatCompletions and Anthropic Messages formats. base_url stays https://api.deepseek.com — update only the model parameter.

python
import anthropic

client = anthropic.Anthropic(
    api_key="your-deepseek-api-key",
    base_url="https://api.deepseek.com"
)

message = client.messages.create(
    model="deepseek-v4-pro",
    max_tokens=4096,
    messages=[{"role": "user", "content": "What changed in the V4 GA release?"}]
)

Migration checklist

  • Search codebase for deepseek-chat and deepseek-reasoner
  • Update to deepseek-v4-flash or deepseek-v4-pro
  • Choose non-thinking vs thinking mode per use case
  • Test in staging before July 24
  • For Think Max, ensure context window is set to 384K+
info

Bottom line: V4 GA does not need to beat Claude Fable 5 or GPT-5.6 on every benchmark. It delivers open-weight leadership at 1/10 to 1/100 the cost of closed frontier models — the strongest MIT-licensed coding model on SWE-bench Verified, 1M context that actually works, and pricing that wins even at peak hour.

Teams wiring V4 into Cursor, Claude Code, or OpenClaw agent pipelines often hit a second bottleneck: laptops sleep, shared VPS nodes contend for GPU/CPU, and pure Linux hosts lack Apple toolchain affordances for iOS builds. Running long-session CLI agents on a flaky local machine bleeds time across session drops, config drift, and signing queue blocks. For production environments that need stable SSH access, predictable tiers, and reproducible Mac profiles while you swap API keys or model endpoints, NodeMini Mac Mini cloud rental is usually the better fit than API-only stacks or ad hoc hardware. Compare specs on Mac Mini rental rates and provisioning steps in the help center.

Sources: DeepSeek official docs, arXiv:2606.19348, HuggingFace Model Hub, LLMReference, Artificial Analysis, MangoMind Blog, TechNode, Zaobao.

FAQ

Frequently Asked Questions

It depends on the workload. V4-Pro leads LiveCodeBench and Codeforces Elo among open-weight models and costs roughly 17× less on output than GPT-5.6 Sol. GPT-5.6 still leads Terminal-Bench 2.1 (85.1%) for shell-based agents. Route by task, not by hype. Compare hybrid execution costs on rental rates if you run agents 24/7.

Rates double during Beijing weekday peak hours (09:00–12:00 and 14:00–18:00). Off-peak V4-Pro output is $0.87/M; peak is $1.74/M. V4-Flash cache-hit input can drop to $0.0028/M off-peak. Schedule batch jobs outside peak windows to halve spend.

Replace deepseek-chat with deepseek-v4-flash (non-thinking) and deepseek-reasoner with Flash thinking mode or deepseek-v4-pro. Grep your repos, update env vars and CI configs, test in staging, deploy before July 24, 15:59 UTC. Access setup for agent nodes: help center.

V4-Pro: 1.6T total / 49B active, 61 layers, stronger reasoning. V4-Flash: 284B total / 13B active, 43 layers, faster and cheaper. Both support 1M context and MIT license. Use Flash for routing and volume; Pro for complex agents and math.

Yes — both models shipped under MIT since the April 24 preview. Pro self-hosting needs serious GPU infrastructure; many teams use API for peaks and a dedicated cloud Mac for local routing, OpenClaw gateways, and long-session CLI agents. See help center for SSH and node setup.

Yes. Peak V4-Pro output at $1.74/M is about 8.6× cheaper than Claude Opus 4.8 ($15/M) and GPT-5.6 Sol (~$15/M). Peak surcharges add ops complexity, not a price parity with closed frontier models.