AI Trend Notifier
EN
← wiki

$ cat wiki/models/deepseek-v4-pro-0813.md

DeepSeek V4-Pro-0813

Compared with

Spec

AttributeValue
DeveloperDeepSeek
Released2026-08-13 (see Release Date — one tracker says 2026-08-12)
Announced2026-08-13
Context window1,048,576 (1M) — 384K max output
Pricing$0.66/M input (cache miss) · $1.98/M output off-peak; $1.32 · $3.96 at peak — see Pricing
LicenseMIT (open-weight, as reported)
AvailabilityDeepSeek API (Responses format, Codex-adapted), Hugging Face (deepseek-ai/DeepSeek-V4-Pro-0813)
Given its own page rather than folded into DeepSeek V4 on the
precedent set by DeepSeek V4-Flash: DeepSeek ships dated builds that
change what the model does without changing what it is, and a build that moves
DeepSWE from 12.8 to 62.7 is not an annotation on a July page.

No repository, model card or LICENCE file was opened. huggingface.co is blocked from this environment, so the MIT licence and the repository name are reported, not read (source).

Parameter count is carried as 1.6T total / 49B active, the figure this wiki already holds for V4-Pro; one source read this run states 1.57T / 48B (source). See ## Conflicting Reports.

Release Date

2026-08-13 — DeepSeek replaced the preview edition of V4-Pro in its API documentation with build 0813, described as the official release with "greatly enhanced agentic capabilities" (source).

This closes a statement this wiki has carried since 2026-07-31, when the V4-Flash release said "The official release of DeepSeek-V4-Pro will follow soon" (source).

It also resolves a Watch item that ran for five consecutive days. Chinese press reported an August 10–20 GA window on 2026-07-28; this wiki declined to record it as a date, because it was a press target rather than a company statement. The release landed inside that window on day four.

Pricing — the flat rate ended 2026-08-16; the schedule it moved onto is not new

From 2026-08-16 at 16:00 UTC, V4-Pro and DeepSeek V4-Flash left flat per-token rates for the peak/off-peak schedule (source).

Cache-miss inputOutput
Off-peak$0.66/M$1.98/M
Peak$1.32/M$3.96/M
Peak hours are 01:00–04:00 and 06:00–10:00 UTC; all other hours are
off-peak, and peak is 2× the new off-peak rate — not 2× the old flat rate
(source).
No source read gives the new cache-hit input figure in dollars; it is
reported only as a multiplier.

The schedule itself dates from 2026-07-16, and this wiki already held it. DeepSeek V4 has carried Pricing: Peak: 2× off-peak API rates; off-peak rates not disclosed since the V4 GA, whose announcement introduced "first-ever peak-hour / off-peak pricing" with peak hours of 9:00–12:00 and 14:00–18:00 daily and the same ratio (source).

Those are the same hours as today's, stated in a different timezone. Read as Beijing time (UTC+8), 9:00–12:00 → 01:00–04:00 UTC and 14:00–18:00 → 06:00–10:00 UTC, matching the reported window exactly. The July announcement does not name its timezone, so this is an inference — but it is supported by DeepSeek's own cutover convention: that announcement retired deepseek-chat and deepseek-reasoner at 15:59 UTC, and today's rates changed at 16:00 UTC, both of which are midnight Beijing (source).

So what changed on 2026-08-16 is the price, not the pricing model — two models that had been held at flat promotional rates were moved onto a schedule that had existed for a month, at rates above the ones they left. A write-up that leads with "DeepSeek introduces peak pricing" is a month late; the news is the increase.

This page published the superseded figure for two days, and the withdrawn claim is recorded rather than silently replaced:

Held here 2026-08-14 → 2026-08-17Correct from 2026-08-16 16:00 UTC
$0.435/M input (cache miss), flat$0.66 off-peak / $1.32 peak
$0.003625/M input (cache hit), flat×6 off-peak / ×12 peak, no dollar figure published
$0.87/M output, flat$1.98 off-peak / $3.96 peak
Off-peak is not a discount on the price it replaces. Every tier in the new
schedule costs more than the flat rate: the cheapest hour of the day is 1.5×
the old input price and 2.25× the old output price, and the most expensive
is and 4.5×
(source).

Caught on the day, and that is the point. Claude Sonnet 5's price correction was captured at day +6 on 2026-08-16, and the reason given there was that a price change is not a release — it produces no model card and no tracker entry. This one was captured at day 0, by the same non-feed polling, one run later. What changed is that the run was looking.

No first-party page was read. api-docs.deepseek.com is blocked from this environment like every other host, so the entire schedule above is third-party reporting, cross-read across six outlets and pricing trackers that agree on the hours, the ratio and the V4-Pro dollar figures (source). See ## Conflicting Reports for the arithmetic that does not close.

Benchmarks

Vendor-stated, quoted against DeepSeek's own V4-Pro-Preview (source):

BenchmarkV4-Pro-PreviewV4-Pro-0813
Terminal Bench 2.172.187.9
DeepSWE12.862.7
CyberGym52.783.3
Per Eval Harness Configuration, these are vendor-run numbers on
agentic benchmarks and DeepSeek has not released the harness, so they cannot
be replicated by independent evaluators
(source). They are
recorded as claims about a (model, harness) pair, not as model properties.

The one independently-produced figure points the other way. Artificial Analysis places V4-Pro-0813 (max) at 53 on its Intelligence Index — one point above DeepSeek V4-Flash (the cheaper, smaller sibling) and four points below GPT-5.6 Terra, the mid tier of GPT-5.6 Sol (and Terra, Luna)'s family (source).

The gap between the two readings is the whole story of this release and it is left standing rather than averaged: a vendor triple-digit jump on agentic suites, and a one-point move on a ten-benchmark composite run by someone else. SCMP's headline reads "struggles on benchmarks, shines in cybersecurity" (source).

The Terminal-Bench figure of 87.9 is reported as "narrowly trailing Fable 5's score of 88" (source) — a third party's comparison, and not checked against Claude Fable 5's own page, where the SWE-bench Pro conflict of 80.0/80.3 is still open.

Neither figure appears in the eval snapshots this repo holds: the newest are sources/evals/artificial-analysis-2026-08-09.md and sources/evals/lmarena-2026-08-09.md, both predating this release.

Use Cases

DeepSeek's stated positioning is agentic: the release names Responses API support and Codex integration, and every benchmark it published measures terminal operation, code engineering, tool use or security tasks (source).

Both thinking and non-thinking modes are supported (source).

Compared To

  • DeepSeek V4-Flash — the 284B/13B sibling that beat V4-Pro-Preview on nine agent benchmarks on 2026-07-31, and which this build passes by one point on the only independent index available
  • DeepSeek V4 — the July GA series page this build supersedes for V4-Pro
  • GPT-5.6 Sol (and Terra, Luna) — its Terra tier is the model Artificial Analysis places four points ahead
  • Qwen 3.8 Max — the other Chinese open-weight release of this week, at 2.4T total / 95B active
  • Kimi K3 — Moonshot's 2.8T open-weight model

Conflicting Reports

  • Release date. One tracker dates the build 2026-08-12 (DataLearner); the outlets covering it on the day, and the r/LocalLLaMA thread carrying DeepSeek's own "launching today" line, date it 2026-08-13 (source). The Spec row takes 2026-08-13 as the more direct evidence; the alternative is recorded here rather than dropped.
  • Parameter count. 1.6T total / 49B active (DataLearner, and this wiki's existing figure) against 1.57T / 48B (morphllm). No first-party statement was read. Both are third-party.
  • The new pricing does not reconcile with its own multipliers. The reported off-peak multipliers give $0.435 × 1.5 = $0.6525 and $0.87 × 2.25 = $1.9575, against the $0.66 and $1.98 reported as the dollar figures — a gap of ~1.1%, in the same direction on both rows. The new V4-Flash rates are quoted only in RMB, at round numbers (¥0.05 / ¥1.50 / ¥4.50 off-peak), which is consistent with the schedule being set in RMB and the dollar figures being conversions. No source read says so, so both readings are recorded and neither is adopted (source). The Spec row carries the reported dollar figures, not the computed ones.

Referenced by

Sources