DeepSeek V4-Flash
DeepSeek V4-Flash is the smaller of the two large language models in the DeepSeek V4 family, a 284-billion-parameter Mixture of Experts model with 13 billion active parameters and a one-million-token context window, developed by the Hangzhou lab DeepSeek.[19][20] It first shipped on April 24, 2026 as a preview, alongside the larger V4-Pro variant of the same DeepSeek V4 release. On July 31, 2026 DeepSeek put the official build, DeepSeek-V4-Flash-0731, into public beta on its API, keeping the same architecture, the same parameter count, and the same prices as the preview while reporting much higher scores on agent benchmarks.[1][2] The 0731 release also added native support for OpenAI's Responses API wire format and a documented configuration for OpenAI Codex.[1][5] Later the same day DeepSeek published the checkpoint as open weights under the MIT License in a new Hugging Face repository, deepseek-ai/DeepSeek-V4-Flash-0731, shipped with the DSpark speculative decoding module attached.[29][31]
| Field | Value |
|---|---|
| Developer | DeepSeek |
| API model id | deepseek-v4-flash |
| Model version | DeepSeek-V4-Flash-0731 |
| Public beta date | July 31, 2026 |
| Open weights published | July 31, 2026, at deepseek-ai/DeepSeek-V4-Flash-0731 |
| Architecture | Mixture of Experts, 284B total parameters, 13B activated |
| Context length | 1,048,576 tokens (1M) |
| Maximum output | 384K tokens |
| Reasoning effort levels | low, high (default), max |
| Input modalities | Text only |
| Wire formats | OpenAI Chat Completions, Anthropic Messages, OpenAI Responses |
| Concurrency limit | 2,500 concurrent requests per account |
| Price (per 1M tokens) | $0.0028 cache-hit input, $0.14 cache-miss input, $0.28 output |
| Checkpoint precision | FP4 experts, FP8 elsewhere; 48 safetensors shards, about 167 GB |
| Speculative decoding | DSpark draft module included in the released checkpoint |
| Weights license | MIT |
Background
DeepSeek released the V4 series in preview on April 24, 2026, following DeepSeek-V3 in December 2024 and DeepSeek-R1 in January 2025, the two releases that made the lab internationally known. The series has two members: V4-Pro at 1.6 trillion total parameters with 49 billion activated, and V4-Flash at 284 billion total with 13 billion activated. Both support a one-million-token context and both were published as open weights under the MIT License.[19][20]
At the same launch, DeepSeek pointed the two legacy API names, deepseek-chat and deepseek-reasoner, at V4-Flash in non-thinking and thinking mode respectively, and gave them a three-month retirement window ending July 24, 2026.[1] That retirement took effect one week before the 0731 build shipped, so by the end of July the DeepSeek API exposed only two model ids: deepseek-v4-flash and deepseek-v4-pro.[3]
Through the second quarter of 2026 the models on the API remained the April preview builds. DeepSeek's own July comparison chart labels them DeepSeek-V4-Flash-Preview and DeepSeek-V4-Pro-Preview.[2]
What changed in the 0731 build
DeepSeek was unusually explicit about the scope of the update. According to the API change log, "DeepSeek-V4-Flash-0731 keeps the same model architecture and size as DeepSeek-V4-Flash-Preview, and was only re-post-trained."[1] Nothing about the pre-trained backbone, the parameter count, the context length, or the price changed. The API calling method is unchanged as well: requests that already set model to deepseek-v4-flash picked up the new build automatically.[1][9]
DeepSeek also scoped the update tightly in the other direction. The change log states that only the V4-Flash API was upgraded, and that the V4-Pro API and the models behind the DeepSeek app and website were left as they were, with the official V4-Pro release to "follow soon."[1] Chinese-language coverage from IT之家 and TechNode reported the same split on the day.[14][17]
Because the release is a post-training change rather than a new model, the practical effect for callers was a silent swap: the same model id returned different behavior from July 31 onward. That is worth knowing for anyone comparing evaluation runs across the boundary.
The model card published later that day with the weights adds one structural detail the change log left out. It describes DeepSeek-V4-Flash-0731 as "the official release of DeepSeek-V4-Flash, superseding the preview version, with substantially enhanced agentic capabilities," and states that "it has the same model structure as DeepSeek-V4-Flash-DSpark, i.e. it comes with a speculative decoding module attached."[29] That module, DSpark, is a draft model bolted onto the checkpoint to speed up decoding rather than a change to the language model itself, and the shipped config.json carries its settings alongside the V4 architecture fields.[29][30]
Benchmark results reported by DeepSeek
DeepSeek published nine agent-oriented scores in the change log and in a chart attached to its announcement post, and republished the same nine rows unchanged on the Hugging Face model card when the weights went up. The company's framing is that the new Flash build now beats the larger V4-Pro-Preview across the board, "despite its far smaller activated parameter count."[1][2][29]
| Benchmark | V4-Flash-0731 | V4-Flash-Preview | V4-Pro-Preview | GLM-5.2 | Opus-4.8 |
|---|---|---|---|---|---|
| Terminal Bench 2.1 | 82.7 | 61.8 | 72.1 | 81.0 | 85.0 |
| NL2Repo | 54.2 | 39.4 | 38.5 | 48.9 | 69.7 |
| Cybergym | 76.7 | 38.7 | 52.7 | not reported | 83.1 |
| DeepSWE | 54.4 | 7.3 | 12.8 | 46.2 | 58.0 |
| Toolathlon-Verified | 70.3 | 49.7 | 55.9 | 59.9 | 76.2 |
| Agents' Last Exam | 25.2 | 15.8 | 16.5 | 23.8 | 25.7 |
| AutomationBench Public | 25.1 | 10.8 | 12.8 | 12.9 | 27.2 |
| DSBench-FullStack | 68.7 | 37.0 | 41.8 | 61.8 | 71.6 |
| DSBench-Hard | 59.6 | 25.8 | 31.1 | 54.5 | 71.7 |
All of these are vendor-reported figures. Two footnotes, carried identically on DeepSeek's launch chart and on the model card, matter for reading them. First, "for the Code Agent tasks among the public benchmarks above, DeepSeek-V4-Flash-0731 is evaluated with the minimal mode of DeepSeek Harness (to be released) as the agent framework, using the max reasoning effort level with temperature = 1.0, top_p = 0.95."[1][2][29] A model's score on agent benchmarks depends heavily on the harness driving it, so results measured with an unreleased first-party scaffold are not directly comparable to leaderboard entries produced with a public one. The parenthetical "to be released" still stood on the model card that shipped with the open weights, which means the checkpoint being public does not by itself make these numbers reproducible.[29] 36Kr noted that the announcement was the first time DeepSeek's in-house harness had appeared under an official name.[16] Second, the dagger on the last two rows marks them as DeepSeek's own internal test sets: "DSBench-FullStack is an internal full-stack development test set; DSBench-Hard is an internal test set of difficult coding-agent problems." No outside party can reproduce those two rows at all.[1][29]
What the benchmarks measure
Four of the public benchmarks have published documentation. Terminal-Bench 2.1 is an 89-task suite for coding agents working in a command-line environment, released on May 6, 2026 as a revision of Terminal-Bench 2.0 that repaired 28 tasks and added continuous validation of the task set.[21] Toolathlon (the Tool Decathlon) covers 32 applications and 604 tools across 108 verified tasks that typically take around 20 turns, and its authors reported that the best model they tested reached 38.6 percent.[22] CyberGym has 1,507 real vulnerabilities from 188 software projects and asks an agent to write a proof-of-concept test that reproduces each one from a text description plus source code.[23] NL2Repo-Bench hands an agent a requirements document and an empty workspace and grades the Python library it produces against the original project's test suite, a setting in which the paper's authors found that even the strongest agents stayed below a 40 percent average pass rate.[24] DeepSeek's rows are not directly comparable with the figures in those papers: its Toolathlon row is labelled "Toolathlon-Verified" rather than the full set, and every public code-agent run went through its own harness.
Independent evaluation
Artificial Analysis ran the model on the same day and published a breakdown that broadly supported DeepSeek's claim while trimming some of the numbers.[10][11]
On the Artificial Analysis Intelligence Index v4.1, which aggregates nine evaluations (GDPval-AA v2, tau-cubed Banking, Terminal-Bench v2.1, SciCode, Humanity's Last Exam, GPQA Diamond, CritPt, AA-Omniscience and AA-LCR), DeepSeek V4 Flash 0731 in max reasoning effort scored 50, up from 40 for the April build and six points ahead of V4-Pro at 44.[10][12] That put it level with Google's Gemini 3.6 Flash at 50 and one point behind GPT-5.6 Luna, Z.ai's GLM-5.2 and Meta's Muse Spark 1.1, all at 51. It remained seven points behind Kimi K3 from Moonshot AI at 57, which Artificial Analysis described as the open-weights frontier.[10]
The agentic gains were the largest. Artificial Analysis measured GDPval-AA v2 at an Elo rating of 1559, up from 1189 for the preview, and its own Terminal-Bench 2.1 run at 79 percent, a 17-point rise but roughly four points below DeepSeek's reported 82.7. Its tau-cubed Banking score rose eight points to 31 percent. Every evaluation in the index improved: CritPt up nine points to 17 percent, SciCode up five to 50 percent, Humanity's Last Exam up five to 37 percent, AA-LCR up three to 66 percent and GPQA Diamond up one to 91 percent.[10]
Two findings cut against a simple "it got smarter" reading. The AA-Omniscience result, an index score of -16 that Artificial Analysis called a 7-point improvement on the preview, came entirely from a lower hallucination rate rather than higher accuracy: the share of answers that were correct did not move, while the hallucination rate fell 12 points to 84 percent, which Artificial Analysis put in the same range as GPT-5.6 Terra at 85 percent.[10] Separately, the model is verbose. It burned roughly 206 million output tokens as first reported on July 31 (Artificial Analysis's model page later showed 210 million) to complete the index, which is 12 percent fewer than the 234 million the April build needed but still far above the 62 million median across models.[10][11]
The cost picture was the headline for Artificial Analysis. It placed V4 Flash 0731 on its Pareto frontier for intelligence against cost per task and calculated that, even after OpenAI cut GPT-5.6 Luna prices by 80 percent the day before, running the index on DeepSeek's first-party API cost about 60 percent less than on the comparably scoring OpenAI model. The firm attributed much of that to DeepSeek's roughly 98 percent cache-hit discount, against the 90 percent that most of the industry offers.[10]
All of this was measured against DeepSeek's own hosted API rather than against the released checkpoint. As of August 1, 2026 no independent re-measurement of the open weights, run on someone else's hardware, had been published.
Responses API support and Codex compatibility
The 0731 release added a third wire protocol to the DeepSeek API, and for developers this may matter more than any of the benchmark rows. The Responses API is the request and response format OpenAI introduced for stateful, tool-using agentic work, and it is the protocol OpenAI's Codex clients speak. A provider that implements the same shapes can be dropped in behind a Codex install without patching the client. DeepSeek did exactly that at https://api.deepseek.com, and documents a ~/.codex/config.toml that sets wire_api = "responses" under a [model_providers.deepseek] block, plus a models.json catalog declaring the model's context window and reasoning levels to Codex.[5][6] A one-line setup script is offered for macOS, Linux and Windows; DeepSeek says it backs up the existing configuration first and validates the files before writing.[5] The same configuration serves the Codex CLI, the ChatGPT desktop app and the Codex extension for Visual Studio Code.[5]
Support is still limited to Flash. As of August 1, 2026 DeepSeek's pricing page continued to read: "The Responses API currently only supports the deepseek-v4-flash model, and does not yet support the deepseek-v4-pro model. We will add support for the deepseek-v4-pro model in early August 2026." The Codex integration page and the Responses API guide carry the same restriction.[3][5][6]
Compatibility limits
DeepSeek's implementation is a stateless subset. previous_response_id and conversation are not supported, store always returns false, and background, metadata, include, prompt and service_tier are not implemented. Requests that exceed the context window return HTTP 400 rather than truncating, because truncation is unsupported. prompt_cache_key and prompt_cache_retention are not accepted either, since DeepSeek manages context caching automatically. Unsupported parameters are silently ignored so that existing clients connect without modification. Among tools, function and web_search work, custom is accepted only for the apply_patch name that Codex needs, and file_search, code_interpreter, computer_use and MCP tools are ignored. Image and file inputs are not supported: an input_image part does not raise an error but is replaced with placeholder text.[6]
DeepSeek documents a separate integration for Anthropic's Claude Code through https://api.deepseek.com/anthropic, in which V4-Pro fills the Opus and Sonnet roles and V4-Flash is mapped to the Haiku and subagent roles.[8]
Architecture and specifications
Because the 0731 build reuses the preview's network unchanged, its architecture is the V4 architecture described in DeepSeek's technical report, "DeepSeek-V4: Towards Highly Efficient Million-Token Context Intelligence," submitted to arXiv on April 26, 2026.[20] The three changes the paper foregrounds are a hybrid attention design that pairs Compressed Sparse Attention with Heavily Compressed Attention, Manifold-Constrained Hyper-Connections (mHC) in place of ordinary residual connections, and the Muon optimizer. The paper reports that at a one-million-token context, V4-Pro needs 27 percent of the per-token inference FLOPs and 10 percent of the KV cache of DeepSeek V3.2.[19][20] Both models were pre-trained on more than 32 trillion tokens. The DeepSeek V4 article covers the architecture in detail.
The config.json shipped with the 0731 weights puts numbers on parts of that description. It declares 43 hidden layers, a hidden size of 4,096, 64 attention heads with a head dimension of 512, LoRA-style query and output projections at rank 1,024, 256 routed experts plus one shared expert with six routed experts activated per token, an expert intermediate size of 2,048, a vocabulary of 129,280 tokens, and YaRN rope scaling by a factor of 16 from an original 65,536-token window up to the full 1,048,576. Expert tensors are marked "expert_dtype": "fp4" while the quantisation block declares FP8 E4M3 weights in 128 by 128 blocks with UE8M0 scales, which matches the "FP4 + FP8 Mixed" precision label on DeepSeek's V4 model cards: MoE expert parameters in FP4, most other parameters in FP8.[30][35] Four dspark_ fields configure the attached draft module (block size 5, Markov rank 256, a dedicated noise token id, and target layer ids 40, 41 and 42), and num_nextn_predict_layers is set to 1.[30]
Codex-facing metadata in DeepSeek's models.json fills in a few operational numbers that the model card does not: the declared context window is 1,048,576 tokens, Codex is told to treat 95 percent of that as effectively usable, parallel tool calls are always on, and the three reasoning levels are low ("Fast responses with lighter reasoning"), high ("Extra high reasoning depth for complex problems") and max ("Maximum reasoning depth for the hardest problems"), with high as the default.[5]
Availability, pricing, and rate limits
V4-Flash is served from DeepSeek's first-party API at https://api.deepseek.com for OpenAI-format and Responses-format calls, and at https://api.deepseek.com/anthropic for Anthropic-format calls.[3] Prices did not change with the 0731 build.[3][10]
| Model | Input, cache hit | Input, cache miss | Output | Concurrency |
|---|---|---|---|---|
deepseek-v4-flash | $0.0028 / 1M | $0.14 / 1M | $0.28 / 1M | 2,500 |
deepseek-v4-pro | $0.003625 / 1M | $0.435 / 1M | $0.87 / 1M | 500 |
DeepSeek's Chinese-language pricing page lists the same rates in yuan: 0.02, 1 and 2 yuan per million tokens for Flash, and 0.025, 3 and 6 yuan for Pro.[4] The Pro figures reflect steep cuts made in late April 2026, when DeepSeek reduced cache-hit input prices across the API to one tenth of launch levels and discounted V4-Pro by 75 percent, taking output from 24 yuan to 6 yuan per million tokens; announced as a limited-time promotion through early May, the reduced rates remain the listed prices.[15][3] Both models are capped at 384K output tokens.[3] Concurrency is counted per account across all API keys, and exceeding it returns HTTP 429; DeepSeek offers free capacity expansion on request and supports a user_id parameter for per-tenant KV-cache isolation, scheduling isolation and content-safety separation.[7] For a broader view of how these rates sit against other vendors, see LLM API pricing comparison.
Peak and off-peak pricing
A footnote on the pricing page states that DeepSeek "will soon adopt a peak/off-peak pricing policy," under which prices during peak hours will be twice the regular prices and the change will apply to all billing items. Peak hours are defined as 9:00 to 12:00 and 14:00 to 18:00 Beijing time (UTC+8) daily, and the effective date is left to a future official announcement.[3] The identical note appears on the Chinese version of the page.[4] As of August 1, 2026 the policy had not taken effect and no start date had been published, so the rates in the table above are the ones actually charged.
Doubling would put V4-Flash output at 4 yuan per million tokens and V4-Pro output at 12 yuan during working hours.[28] The scheme reverses the direction of DeepSeek's earlier experiment with time-based pricing: from February 26, 2025 the company ran off-peak discounts instead, cutting DeepSeek-V3 by 50 percent and DeepSeek-R1 by 75 percent between 16:30 and 00:30 UTC, a program it wound down the following September.[27] The plan was first communicated in an upgrade notice emailed to users on June 29, 2026, which tied the change to the V4 official release, then planned for mid July, and said users would be given 24 hours notice by email before any billing adjustment took effect.[28]
Weights and licensing
The open weights landed the same day as the API beta, in a new repository rather than as a revision of the existing one. deepseek-ai/DeepSeek-V4-Flash-0731 was created on Hugging Face at 07:30 UTC on July 31, 2026, roughly half an hour after DeepSeek announced the API on X. The shards went up under a commit titled "Add files using upload-large-folder tool" at 09:54 UTC, and the commit titled "Release DeepSeek-V4-Flash-0731" landed at 12:02 UTC. A fourth commit, "add sglang cookbook to model card," followed at 03:07 UTC on August 1. The first three are attributed to the DeepSeek account msr2000; the August 1 model-card commit adds zjxia.[31][32]
The repository holds 48 safetensors shards, with Hugging Face reporting 166,886,535,336 bytes of storage, about 167 GB. Alongside them sit config.json, generation_config.json, model.safetensors.index.json, the tokenizer files, LICENSE, README.md, and two directories. encoding/ carries Python scripts and test cases rather than a Jinja chat template, because this release ships no Jinja template at all: callers are expected to use the provided encode_messages and parse_message_from_completion_text helpers to turn OpenAI-format messages into input strings and to parse the model's output. inference/ holds a minimal local runner with a weight-conversion script.[29][32][40] The license is MIT, the same as the preview.[29]
The older deepseek-ai/DeepSeek-V4-Flash repository was left alone. It was last modified on June 22, 2026 and still opens with "We present a preview version of DeepSeek-V4 series," so anyone who had pinned that repository did not silently receive the new checkpoint.[19][34] The preview weights remain there under the MIT License in FP4-plus-FP8 mixed precision, along with a base checkpoint, and are mirrored on ModelScope.[19]
Artificial Analysis had written on launch day that DeepSeek "is expected to release the model's full weights in the coming weeks," and noted that on its GDPval-AA v2 result the model would then rank second among open-weights models behind Kimi K3.[10] In the event the release commit landed the same day, and the firm's model page now lists the model as open weights under MIT with the checkpoint on Hugging Face.[11]
Reading the parameter count
The figure Hugging Face displays beside a repository is derived automatically: its model API publishes a safetensors block that counts tensor elements per data type, and the sidebar shows that total.[32] For the V4 checkpoints, whose experts are stored in packed FP4 and which ship a draft module in the same repository, that derived total is not the model's parameter count, and it is not even consistent between two repositories that DeepSeek says hold the same structure.
| Repository | Contents | Shards | Storage | Hugging Face tensor total |
|---|---|---|---|---|
DeepSeek-V4-Flash | April preview checkpoint | 46 | about 160 GB | 158.1B |
DeepSeek-V4-Flash-DSpark | preview checkpoint plus DSpark | 48 | about 167 GB | 165.3B |
DeepSeek-V4-Flash-0731 | July checkpoint plus DSpark | 48 | about 167 GB | 304.2B |
Two things fall out of that table. The step from 46 shards and about 160 GB to 48 shards and about 167 GB is what attaching the DSpark draft module costs; the 0731 repository sits on the larger side of that step because it ships the module.[32][33][34] And the two 48-shard repositories report the same file list, a byte-identical config.json and exactly the same total storage of 166,886,535,336 bytes, yet Hugging Face reports 165.3 billion tensor elements for one and 304.2 billion for the other. The entire gap sits in the data-type breakdown the API returns: the 0731 repository declares 296,352,743,424 INT8 elements and no E8M0 tensors, while the DSpark repository declares exactly half that many INT8 elements, 148,176,371,712, plus 9,261,408,000 E8M0 tensors, which the shared config.json identifies as quantisation scales ("scale_fmt": "ue8m0") rather than weights.[30][32][33] Neither number can be read as a parameter count.
DeepSeek's own figure has not moved, and it is 284B total with 13B activated. The V4 model cards give that figure for DeepSeek-V4-Flash, the DSpark card repeats it for what DeepSeek says is the same checkpoint, and the July 31 change log says the 0731 build "keeps the same model architecture and size" as the preview.[1][19][35][36] Third parties serving the released weights agree: vLLM's deployment recipe describes the 0731 variant as 284B total and 13B active, with MoE expert weights stored in FP4 and the remaining attention, normalisation and router parameters in FP8, and Baseten, which hosts the checkpoint, lists it as "284B total parameters and 13B activated per token."[38][41] The 304.2B figure is therefore an accounting artifact of how the 0731 repository declares its FP4 expert elements and quantisation scales, not a parameter count and not the size of the DSpark module, which the shard and storage step puts nearer 7 billion. DeepSeek's own figure, corroborated by Artificial Analysis, vLLM and Baseten, remains 284B total and 13B activated per token. DeepSeek has published no statement addressing the discrepancy.
DSpark
DSpark is not a separate model. The model card for DeepSeek-V4-Pro-DSpark says so directly: the repository "is not a new model. It is the same checkpoint with an additional speculative decoding module attached." The Flash-DSpark card carries the identical note.[35][36] Both point at DeepSpec, DeepSeek's MIT-licensed "full-stack codebase for training and evaluating draft models for speculative decoding," in which DSpark is one of three draft algorithms alongside DFlash and EAGLE-3 and is described as confidence-scheduled speculative decoding with semi-autoregressive generation.[37] DeepSeek published DSpark variants of both V4 models on June 27, 2026, two months after the preview, and a set of small DSpark, DFlash and EAGLE-3 draft models trained on Qwen3 and Gemma 4 targets the following day.[43] With the 0731 release the module stopped being an optional side repository and became part of the shipped checkpoint.[29]
Running the weights
The model card documents two server stacks. Under vLLM, DSpark is switched on with a single flag, --speculative-config '{"method":"dspark","num_speculative_tokens":7,"draft_sample_method":"greedy"}', in a launch line that also sets an FP8 KV cache, a block size of 256, data-parallel size 4 with expert parallelism, the deep_gemm_mega_moe MoE backend and an FP4 indexer cache.[29] Under SGLang, DSpark is enabled with --speculative-algorithm DSPARK and, the card notes, no separate --speculative-draft-model-path, alongside --moe-runner-backend flashinfer_mxfp4 and tensor-parallel size 4.[29] The SGLang cookbook page for DeepSeek V4, added to the model card on August 1, generates launch commands across NVIDIA B200, B300, GB200 and GB300 configurations and warns that enabling speculative decoding makes SGLang reset --max-running-requests to 48.[39] The vLLM recipe covers the same ground for NVIDIA hardware and adds AMD MI325X and MI355X configurations plus disaggregated prefill and decode setups.[38]
For running without a server, the inference/ directory documents converting the Hugging Face checkpoint with convert.py and launching with torchrun across a model-parallel group. To run the experts in FP8 instead of FP4, DeepSeek instructs users to remove "expert_dtype": "fp4" from config.json and pass --expert-dtype fp8 to the converter.[40] For local deployment the card recommends temperature = 1.0 with top_p = 0.95 in agentic scenarios and top_p = 1.0 otherwise, and a maximum output length of 384K tokens at the high and max reasoning effort levels, matching the cap on the hosted API.[29][3]
Third-party redistribution
Community conversions appeared within a day. A Hugging Face search on the model name returns GGUF builds from Unsloth, bartowski, ggml-org and lmstudio-community, NVFP4 and MXFP4 quantisations, MLX conversions for Apple silicon, and EXL3 builds at 2.0, 2.5 and 3.0 bits per weight.[42] Baseten added the checkpoint to its model library and serves it behind an OpenAI-compatible endpoint.[41] OpenRouter, which on August 1, 2026 was routing V4 Flash at discounted prices of $0.0896 per million input tokens and $0.1792 per million output tokens,[25] lists the 0731 build as a separate entry, deepseek/deepseek-v4-flash-0731, whose catalog record carries a creation timestamp of July 31, 2026. As of August 5, 2026 that listing aggregated more than a dozen hosting providers, with routed prices starting at $0.09 per million input tokens and $0.18 per million output tokens at the cheapest host and DeepSeek's list rates of $0.14 and $0.28 at most others, including DeepSeek's own first-party endpoint; OpenRouter's original deepseek/deepseek-v4-flash slug is now labelled "DeepSeek V4 Flash 0423" and points at the April preview at the same $0.14 and $0.28 rates.[46][47] Nous Research also offers the model through its Nous Portal subscription platform in partnership with GPU cloud provider Novita AI: the preview build was free for a limited period from May 14, 2026, and on August 2, 2026 Nous announced a seven-day 90 percent discount on the 0731 build.[44][45] For readers comparing terms across labs, see open-weight license comparison and open source AI.
Reception and adoption
Coverage on launch day concentrated on the inversion of DeepSeek's own product ladder: a 13-billion-active-parameter model outscoring the lab's 49-billion-active flagship preview on agent work. The Chinese outlet 智东西 ran the story under a headline calling it "倒反天罡" (roughly, the natural order turned upside down) and argued that the release shows low price does not imply low capability.[18] 36Kr reported DeepSeek's framing that for specific tasks, model scale is not the decisive factor once post-training optimization is applied properly.[16] OfficeChai's write-up compared the reported scores against Opus 4.8 and against GPT-5.6 Sol, Claude Fable 5 and Claude Sonnet 5 list prices, all of which V4-Flash undercuts by a wide margin.[13] Mainstream business coverage followed with the next wave of Chinese releases. In an August 4, 2026 story on China's model blitz, Bloomberg reported that a so-called DeepSeek death zone had emerged on a widely shared Artificial Analysis benchmark chart, for rivals that charge more for the same capability or deliver less for the same price. The story called V4-Flash "a breakthrough model in terms of pricing" and cited Artificial Analysis benchmark testing in which executing a complex real-world workload cost $0.03 with V4-Flash against $3.15 with Anthropic's Claude Fable 5.[48]
Third-party coding agent products moved quickly. The agent tool Command Code announced support the same morning, saying the model was live on all of its plans with tool calls and cache repairs.[26] Within a day of the weights going up the repository had gathered more than a thousand likes on Hugging Face and had been re-quantised into a dozen community formats.[32][42]
Limitations
The model is text-only in and text-only out; DeepSeek's Responses API documentation confirms that image and file inputs are dropped.[6][10] The Responses implementation is stateless, so applications that rely on server-side conversation threading through previous_response_id need to manage history themselves.[6] Verbosity is a real cost driver despite the low per-token price: Artificial Analysis measured roughly 206 million output tokens to complete its index, more than three times the median.[10] The AA-Omniscience result shows an 84 percent hallucination rate, improved but still high, and factual accuracy did not move between builds.[10]
Vendor benchmark numbers were produced with an in-house harness that the model card still marks "to be released," two of the nine reported benchmarks are internal and unreproducible, and the one directly comparable public figure, Terminal-Bench 2.1, came in about four points lower when measured independently. Publishing the weights does not fix that: without the harness, the headline agent scores cannot be reproduced from the checkpoint.[1][10][29]
Finally, the API is still in public beta. As of August 1, 2026 the official V4-Pro build had not appeared, neither in the API change log nor as a new repository in DeepSeek's Hugging Face organisation, and Responses API support for deepseek-v4-pro was still listed as coming in early August.[1][3][43] The weights that did ship are heavy for self-hosting: 48 shards and about 167 GB, with DeepSeek's own reference configurations assuming four datacentre GPUs.[29][32][38]
Significance
The 0731 release is a data point about where capability gains were coming from in mid-2026. DeepSeek changed no architecture, added no parameters and raised no prices, yet the model moved from 40 to 50 on an independent aggregate index and from 7.3 to 54.4 on one vendor-reported coding benchmark. DeepSeek attributes the change entirely to redone post-training, and reported its public code-agent scores using a first-party harness, so part of the measured gain belongs to the scaffold rather than the weights. The lab has not published a technical description of the 0731 post-training run.[1]
Publishing the checkpoint under MIT on the day of the API beta closes part of that gap without closing all of it. Anyone can now run the model, fine-tune it or serve it themselves, which is what separates this release from a closed frontier model at a similar index score. But the scaffold that produced the headline agent numbers is still unreleased, so the claims that made the announcement newsworthy remain unverifiable even with the weights in hand.[29]
The protocol work carries its own weight. By implementing OpenAI's Responses API and publishing a Codex configuration, DeepSeek made its model a drop-in backend for tooling that developers outside China already run, which lowers switching costs in a way a benchmark table does not. Paired with a 98 percent cache-hit discount and per-token prices roughly an order of magnitude below comparably scoring closed models, that combination, rather than a frontier score, is the competitive position the release stakes out.[5][10]
See also
- DeepSeek V4
- DeepSeek
- DeepSeek V3.2
- OpenAI Codex
- OpenAI Responses API
- Kimi K3
- Speculative decoding
- Open weights
- vLLM
- SGLang
- Context caching
- LLM API pricing comparison
References
- ^Change Log (entry dated 2026-07-31), DeepSeek API Docs
- ^DeepSeek-V4-Flash Official API is now LIVE in public beta, @deepseek_ai on X, July 31, 2026
- ^Models & Pricing, DeepSeek API Docs (accessed August 1, 2026)
- ^模型 & 价格, DeepSeek API 文档 (accessed July 31, 2026)
- ^Integrate with Codex, DeepSeek API Docs
- ^Using the Responses API, DeepSeek API Docs
- ^Rate Limit & Isolation, DeepSeek API Docs
- ^Integrate with Claude Code, DeepSeek API Docs
- ^Your First API Call, DeepSeek API Docs
- ^DeepSeek V4 Flash 0731 scores 50 on the Artificial Analysis Intelligence Index, @ArtificialAnlys on X, July 31, 2026
- ^DeepSeek V4 Flash: Intelligence, Performance & Price Analysis, Artificial Analysis (accessed August 1, 2026)
- ^DeepSeek-v4-Flash-0731 Scores 50 On Artificial Analysis Intelligence Index, Creates Big Spike On Pareto Frontier, OfficeChai, July 31, 2026
- ^DeepSeek Releases DeepSeek-V4-Flash-0731, Gives Opus 4.8-Level Performance At A Fraction Of The Price, OfficeChai, July 31, 2026
- ^DeepSeek puts V4-Flash API into public beta, TechNode, July 31, 2026
- ^DeepSeek-V4-Pro 开启 API 限时 2.5 折优惠,活动持续至 5 月 6 日前 (DeepSeek-V4-Pro opens limited-time 75 percent API discount through May 6), IT之家, April 25, 2026
- ^DeepSeek V4 Official Version Released, 36Kr, July 31, 2026
- ^DeepSeek-V4-Flash 正式版 API 上线公测,V4-Pro 正式版将"尽快"发布, IT之家, July 31, 2026
- ^倒反天罡?DeepSeek-V4-Flash 正式版上线,干翻自家先发的 Pro 版, 智东西, July 31, 2026
- ^deepseek-ai/DeepSeek-V4-Flash model card, Hugging Face
- ^DeepSeek-V4: Towards Highly Efficient Million-Token Context Intelligence, arXiv:2606.19348 (April 26, 2026)
- ^Terminal-Bench 2.1, tbench.ai (May 6, 2026)
- ^The Tool Decathlon: Benchmarking Language Agents for Diverse, Realistic, and Long-Horizon Task Execution, arXiv:2510.25726
- ^CyberGym: Evaluating AI Agents' Real-World Cybersecurity Capabilities at Scale, arXiv:2506.02548
- ^NL2Repo-Bench: Towards Long-Horizon Repository Generation Evaluation of Coding Agents, arXiv:2512.12730
- ^DeepSeek: DeepSeek V4 Flash, OpenRouter (accessed August 1, 2026)
- ^DeepSeek V4 Flash 0731 now live in Command Code, @CommandCodeAI on X, July 31, 2026
- ^Off-Peak Discounts Alert, @deepseek_ai on X, February 26, 2025
- ^DeepSeek V4正式版要来了,API高峰时段价格翻倍 (DeepSeek V4 official release coming, API prices double at peak hours), Jiemian News via Sina Technology, June 29, 2026
- ^deepseek-ai/DeepSeek-V4-Flash-0731 model card, Hugging Face
- ^DeepSeek-V4-Flash-0731 config.json, Hugging Face
- ^DeepSeek-V4-Flash-0731 commit history, Hugging Face API
- ^Model record for deepseek-ai/DeepSeek-V4-Flash-0731, Hugging Face API
- ^Model record for deepseek-ai/DeepSeek-V4-Flash-DSpark, Hugging Face API
- ^Model record for deepseek-ai/DeepSeek-V4-Flash, Hugging Face API
- ^deepseek-ai/DeepSeek-V4-Pro-DSpark model card (README.md), Hugging Face
- ^deepseek-ai/DeepSeek-V4-Flash-DSpark model card (README.md), Hugging Face
- ^deepseek-ai/DeepSpec, GitHub
- ^DeepSeek-V4-Flash-0731 deployment recipe, vLLM Recipes
- ^DeepSeek-V4 cookbook, SGLang documentation
- ^DeepSeek-V4-Flash-0731 inference/README.md, Hugging Face
- ^DeepSeek-V4-Flash-0731, Baseten Model Library (accessed August 1, 2026)
- ^Hugging Face model search for DeepSeek-V4-Flash-0731 (accessed August 1, 2026)
- ^deepseek-ai models sorted by creation date, Hugging Face API (accessed August 1, 2026)
- ^Deepseek V4 Flash is now free via Nous Portal for a limited time thanks to @novita_labs, @NousResearch on X, May 14, 2026
- ^DeepSeek V4 Flash 0731 is now 90% off on Nous Portal, @NousResearch on X, August 2, 2026
- ^DeepSeek: DeepSeek V4 Flash 0731, OpenRouter (accessed August 5, 2026)
- ^Model list entry and per-provider endpoints for deepseek/deepseek-v4-flash-0731, OpenRouter API (accessed August 5, 2026)
- ^China's AI Blitz Creates 'Death Zone' for Rival US Model Makers, Bloomberg News (Zheping Huang, Nectar Gan and Saritha Rai), August 4, 2026
Improve this article
Add missing citations, update stale details, or suggest a clearer explanation. Every suggestion is reviewed for sourcing before it goes live.
6 revisions · v7 · 5,712 words · full history
Fact-checks are independent of edits: a reviewer re-verifies the article against its sources and stamps the date. How we verify
Research and drafting on this wiki are AI-assisted, under named human editorial standards. How AI is used here
Reviewer note: Bloomberg death-zone coverage and OpenRouter 0731 listing verified against the Financial Post syndication and the live OpenRouter API; two references to an excluded source found during review were replaced with IT之家 and Jiemian coverage, correcting the price-cut timeline to late April 2026.
Cite this page: AI Wiki. "DeepSeek V4-Flash." aiwiki.ai, updated 1 Aug 2026, fact-checked 4 Aug 2026. CC BY 4.0. https://aiwiki.ai/wiki/deepseek_v4_flash