Skip to main content

DeepSeek V4-Flash Beats Its Own Pro on Agent Benchmarks

By Upendra

A luminous fiber optic strand carrying a bright pulse of light beside a thick corroded copper bundle on a dark surface

DeepSeek released the official public beta of V4-Flash-0731 on July 31, and the benchmark numbers are worth a second look. Same 284B MoE architecture, same $0.14 per million input tokens, and a post-training rerun that pushed agent benchmark scores past DeepSeek's own V4-Pro-Preview on every metric the company published.

What Actually Changed

Nothing about the architecture or scale changed. DeepSeek ran a new round of post-training, the phase that shapes how a pre-trained model uses its knowledge, not what knowledge it holds. The underlying structure (284B total parameters, 13B active per token, with CSA and HCA sparse attention layers) is identical to the Flash-Preview build. DeepSeek just worked the behavioral layer on top again.

That alone shouldn't be remarkable. Except for how much it moved the needle.

The Benchmark Story

Here are the numbers DeepSeek published for Flash-0731 vs Flash-Preview vs V4-Pro-Preview:

  • DeepSWE: 7.3 (Flash-Preview) to 54.4 (0731). That's a 645% jump. V4-Pro-Preview sits lower.
  • Cybergym: 38.7 to 76.7.
  • Terminal Bench 2.1: 61.8 (Flash-Preview) to 82.7 (0731), vs 72.1 for V4-Pro-Preview.
  • DSBench-FullStack: 37.0 to 68.7.

All nine agent and coding benchmarks DeepSeek published follow the same pattern: Flash-0731 beats Flash-Preview by a wide margin, and beats V4-Pro-Preview too. That last part is the unusual bit.

I haven't run these myself yet. A DeepSWE jump from 7.3 to 54.4 is large enough that I'd want third-party replication before treating it as ground truth. That said, the direction is consistent across multiple independent reports. And separately reported SWE-bench numbers put Flash-Max at 79.0% versus Pro-Max at 80.6%, so the gap between the two tiers is real and narrow.

What This Means for Your Routing Logic

If you've been routing model calls with something like "use Flash for simple tasks, Pro for complex agent work," that heuristic is now wrong for DeepSeek.

The price difference makes this more than academic. V4-Flash is $0.14/$0.28 per million input/output tokens. V4-Pro runs at $0.435/$0.87. You're paying 3x more for a model that Flash-0731 now beats on the benchmarks that matter most for agents. If your routing logic sends planning loops, tool-calling chains, or multi-step code tasks to Pro, you're spending 3x for less performance on those specific workloads.

The practical move: run your agent evals against Flash-0731 this week. Not the synthetic benchmarks, your actual production tasks. If they hold, you can drop Pro from your routing tier for agent workloads.

One real caveat: instruction-following on broad knowledge and long-document reasoning may still favor Pro. The benchmark gap there is tighter, and 79.0% vs 80.6% on SWE-bench is a real difference even if it's narrow.

Zero Migration, Free Upgrade

Here's the part easy to miss. If you're already calling deepseek-v4-flash on the API, you're already on 0731. DeepSeek updated the model behind that API alias in place: same endpoint, same pricing, no version migration required. Your API calls from yesterday are now going to a model that scores 645% higher on DeepSWE than the model from the day before.

That's good if your tasks got harder to solve overnight. It's also a reason to rerun your regression evals now, because model behavior changed even if your code didn't.

I've hit this with other providers too. Model-in-place updates on stable aliases are common, but this one moved things far enough that treating it like a minor patch seems wrong. Log the model alias explicitly in your call records. Rerun evals any time a provider touches a stable alias. That applies here as much as anywhere.

What to Do This Week

  • Run your current agent tasks against Flash-0731 and compare outputs to your existing baseline.
  • If V4-Pro is in your routing stack, benchmark Flash-0731 against it on your actual workloads before assuming Pro is still earning its 3x price premium.
  • Log the model alias explicitly. "deepseek-v4-flash" now means something different than it did 48 hours ago.

The bigger point is this: post-training is increasingly where the real capability gains happen. Same architecture, very different behavior, depending on how the model was fine-tuned and reinforced after pre-training. Architecture announcements alone don't tell the whole story anymore.

Labels:

Comments

Post a Comment

Popular posts from this blog

AngularJs call one method of controller in another controller .

By Upendra
I have seen many question about calling one method of one controller in another controller or extending scope of one controller in another controller.so here are the ways. if you want to call one controller into another or extending scope of controllers there are four methods available $rootScope.$emit() and $rootScope.$broadcast() If Second controller is child ,you can use Parent child communication . Use Services Kind of hack - with the help of angular.element() 1. $rootScope.$emit() and $rootScope.$broadcast() Controller and its scope can get destroyed, but the $rootScope remains across the application, that's why we are taking $rootScope because $rootScope is parent of all scopes . If you are performing communication from parent to child and even child wants to communicate with its siblings, you can use $broadcast If you are performing communication from child to parent ,no siblings invovled then you can use $rootScope.$emit HTML <body ng-app = ...
7 comments
Read more

250,000 AI Agent Instances Exposed on the Internet — Is Yours One of Them?

By Upendra
If You're Running OpenClaw, You May Want to Read This A public watchboard has surfaced listing over 250,000 OpenClaw instances that are directly reachable from the internet. Some of these instances have leaked credentials. Many are running on infrastructure already flagged for known CVEs and threat actor activity. This isn't theoretical. It's happening right now. You can check the exposure list yourself at openclaw.allegro.earth . Why This Is a Big Deal OpenClaw is a powerful AI agent framework. That power comes with serious responsibility. A typical OpenClaw deployment runs with: Personal API keys — OpenAI, Anthropic, Google, cloud provider credentials Broad system permissions — file access, shell execution, network requests Autonomous execution capabilities — the agent can act without human approval Complex codebases — large attack surfaces that haven't been fully audited When one of these instances is publicly reachable without authentication...
Post a Comment
Read more

Closures in javascript and how do they work ?

By Upendra
JavaScript Closures for Dummies  Closures Are Not Magic This page explains closures so that a programmer can understand them — using working JavaScript code. It is not for gurus or functional programmers. Closures are  not hard  to understand once the core concept is grokked. However, they are impossible to understand by reading any academic papers or academically oriented information about them! This article is intended for programmers with some programming experience in a mainstream language, and who can read the following JavaScript function: function sayHello ( name ) { var text = 'Hello ' + name ; var sayAlert = function () { alert ( text ); } sayAlert (); } An Example of a Closure Two one sentence summaries: a closure is the local variables for a function — kept alive  after  the function has returned, or a closure is a stack-frame which is  not deallocated  when the function returns (as if a 'stack-fr...
Post a Comment
Read more