← Back to Blog
August 2, 2026 6 min read

DeepSeek-V4-Flash-0731 posts an open weight model at the top of the intelligence ranking

For most of 2026 the open weight story in large language models has been "good enough, cheaper, and you can run it yourself." GPT-5 and Claude still sit comfortably ahead on raw intelligence, the story went, but you pay 20x more for that gap and you cannot audit the model. DeepSeek's V4-Flash-0731 release on July 31 is one of the data points that makes the gap harder to defend. According to the Artificial Analysis Intelligence Index v4.1, an independent benchmark, V4-Flash-0731 in reasoning max-effort mode scores 50 out of 100, placing it third of 101 ranked models. The median model in that set scores 25.

That number is the part that caught my attention. An open weight model, MIT licensed, sitting at number three on a benchmark that includes every frontier proprietary model running today. The two names above it are not a mystery. The interesting question is whether the gap to number one is still wide enough to justify the closed model pricing, or whether DeepSeek just printed a number that says the answer is no.

What changed on July 31

The DeepSeek changelog is unusually specific about what this release is and is not. V4-Flash first appeared in April as part of the V4 launch, alongside V4-Pro. The 0731 update is V4-Flash going from private preview to public beta through DeepSeek's API. You set the model name to deepseek-v4-flash and the rest of the call signature is unchanged.

The line that jumped out at me from the changelog is this one: "DeepSeek-V4-Flash-0731 keeps the same model architecture and size as DeepSeek-V4-Flash-Preview, and was only re-post-trained." Same 284B total parameters, same 13B active per token, same MoE layout. The gains announced this week are not from a new base model. They are from a new round of instruction tuning, RL, and whatever else goes into post-training.

That is a strange thing to brag about until you read the benchmark list. The model jumped substantially on agent evaluations versus the previous V4-Pro preview, which was the larger model in the family. Terminal Bench 2.1 went from a previously reported number in the high 60s to 82.7. Cybergym to 76.7. DeepSWE to 54.4. If you can move Terminal Bench 2.1 by that much with post-training alone on the same weights, it tells you that the model already had the capability, and the previous post-training pipeline was leaving it on the table.

The intelligence numbers, sourced

Two posts hit the front page of Hacker News within hours of each other. One from the DeepSeek docs, one from Artificial Analysis. The Artificial Analysis page is the one worth reading carefully, because it is independent of DeepSeek and run against every model in their index.

For DeepSeek V4 Flash 0731 in reasoning max-effort mode, Artificial Analysis reports: an Intelligence Index of 50, ranked 3 of 101 models. Median for the comparison class is 25. Pricing is $0.14 per million input tokens and $0.28 per million output tokens, against a class median of $0.58 input and $2.20 output. The total cost to run the full Intelligence Index evaluation on the model was $72.

Intelligence Index
50
#3 of 101 · median 25
Input price
$0.14 /1M
class median $0.58
Output price
$0.28 /1M
class median $2.20
Cache hit price
$0.003 /1M
#1 of 101, 98% off input
Context window
1M tokens
roughly 1,500 A4 pages
Parameters
284B / 13B active
MoE, MIT license

The cache hit price is the one I keep coming back to. Three thousandths of a cent per million cached tokens, ranked first of 101. That is the kind of number that matters when your workload is agentic and you fire the same system prompt and the same tool definitions at the model a thousand times an hour. Most of the cost in those workloads is in the cached prefix, and DeepSeek just made that prefix nearly free.

The agent benchmarks DeepSeek published itself

The DeepSeek changelog claims agent benchmarks "far exceeding V4-Pro-Preview," with V4-Pro being the larger sibling that has not had its GA release yet. I parsed out the numbers they listed. Two are described as internal test sets, the rest are public.

Benchmark
Score
What it measures
Terminal Bench 2.1
82.7
Real shell tasks, terminal navigation
Cybergym
76.7
Offensive security CTF-style evaluation
DSBench-FullStack
68.7
Internal full-stack dev test set
Toolathlon verified
70.3
Multi-tool orchestration across steps
DSBench-Hard
59.6
Internal hard coding agent problems
DeepSWE
54.4
Software engineering agent eval
NL2Repo
54.2
Natural language to repository changes
Agent Last Exam
25.2
Graduate-level agent reasoning
Automation Bench (Public)
25.1
End-to-end browser automation

The DeepSeek note is honest that the public benchmark runs were done with their own harness in minimal mode, with the max effort level, topp 0.95, temperature 1.0. That is the sensible configuration for getting the best number out of a reasoning model on agent tasks, and I appreciate that they disclose it instead of pretending the runs were model-only. The two internal test sets, DSBench-FullStack and DSBench-Hard, you cannot reproduce from outside the company, so the numbers there are claims rather than verified. Everything else, if you have the budget, you can rerun.

What is annoying and worth saying out loud

A few things about this release bug me. The first is the naming. "V4-Flash" is the cheaper, smaller tier of the V4 family. "V4-Pro" is the higher-capability tier. As of this writing V4-Pro is still in preview, and the changelog says the "official release of DeepSeek-V4-Pro will follow soon." So the cheaper model is the one being released, the more capable one is still in preview, and the cheaper one just posted numbers that beat the more capable one's preview. Read that twice. Either V4-Pro is going to come out shortly and post numbers meaningfully higher than 50, in which case this Flash release is a setup for that, or V4-Pro's preview already lost the agent race to its own smaller sibling and the "Pro" label is going to be doing some heavy lifting.

The second is verbosity. The Artificial Analysis page notes V4-Flash-0731 generated 210M output tokens while running the Intelligence Index, against a class median of 100M. That is a reasoning model running in max-effort mode, so of course it emits more thinking tokens. But "twice the tokens per task" is also twice the wall-clock latency and roughly twice the per-task bill even at the cheap pricing. The headline price is great. The realized price on a reasoning workload is "great divided by however verbose your model decides to be," and 2x median verbosity cuts into the savings more than the marketing bullets suggest.

The third is that the Artificial Analysis speed number is "N/A." Output tokens per second is listed as unknown. For a reasoning model on agentic workloads, throughput matters. I would rather know the number and have to interpret it than have it missing.

One thing that genuinely is a big deal

The V4-Flash release notes say the model "natively supports the Responses API format and is specifically adapted for Codex." Codex here means OpenAI's coding agent client, the one that ships with the Codex CLI and is the primary way people interact with the OpenAI coding model on the bench. The fact that DeepSeek explicitly tuned for and tested against that client says something about where the demand is. The coding agent ecosystem is consolidating around a small number of wire formats, and a model that wants adoption from people who do not want to write a custom harness benefits from speaking the wire format the tool already expects.

Earlier in 2026 DeepSeek added an Anthropic-compatible API endpoint alongside the OpenAI ChatCompletions endpoint. They are now also supporting OpenAI's newer Responses API. Two of the three major API shapes a model can speak today, in one vendor. For anyone who has tried to port a tool from one provider to another and hit a wire format mismatch, that is a real feature, not a bullet point on a slide.

How I read this

Open weight models have been closing the gap to closed models in 2026, in the way that a slow train closes distance. V4-Flash-0731 looks like the point where you stop calling it closing and start calling it closed for a lot of practical cases. The third slot on a 101-model leaderboard is not number one, and the two names above it are not trivial to displace on the evals where they still win. But the gap is now small enough that a price difference of 4x to 8x on output tokens is hard to justify for any workload where you are not paying specifically for the marginal intelligence point.

What I do not know from a benchmark number is whether V4-Flash-0731 is robust enough that I would hand it a credential and walk away. The agent benchmark scores are good. The coding harness story is good. The price is excellent. None of that is the same as "I have run this model for a month in production and here is what it breaks on." I treat benchmark scores as a screen, not a verdict. The screen just got a lot more interesting.

If you are picking a model right now for a coding agent or a tool-using agent workload and your previous short list was all proprietary, V4-Flash-0731 is the open weight model worth adding to the short list this week. The Artificial Analysis page is the place to read the independent data, the DeepSeek changelog is the place to read the vendor claims, and you should probably run both against your own workload before you decide which one to believe.

DeepSeek Open Weights LLM AI Agents Coding Agents Benchmark