The short answer, up front: in the last week of July and the first of August 2026, the floor price of usable coding intelligence fell off a shelf. DeepSeek shipped V4 Flash at $0.14 / $0.28 per million tokens — the cheapest well-known model to run — while it scores 79.0 on SWE-bench Verified, about ten points under a frontier model that costs 30 to 90 times more. Days earlier, OpenAI cut GPT-5.6 Luna's price 80%. Days later, Alibaba shipped Qwen3.8-Max. The leaderboard didn't move much. The price did.

If you buy tokens to write code, the compare table above is the whole decision: match the row to the job, and route accordingly.

What actually shipped#

DeepSeek V4 Flash (July 31). This is the headline. At $0.14 per million input tokens and $0.28 output, the independent index Artificial Analysis clocked it at roughly three cents per benchmark test — the lowest of any major model it tracks. It is not a frontier coder: 79.0 on SWE-bench Verified and 91.6 on LiveCodeBench Pass@1 put it firmly in the top quartile but below the leaders. It also ships a 1M-token context window. For the tokens you spend on agent inner loops, test generation, and bulk edits, that price-to-capability ratio is the new baseline everyone else is now measured against.

GPT-5.6 Luna, cut 80% (July 30). OpenAI dropped Luna from $1/$6 to $0.20/$1.20 barely three weeks after the GPT-5.6 family launched — a defensive move that fast is a tell. The reported cause: Chinese open-weight models had taken 46% of US enterprise token usage on OpenRouter, and enterprise buyers had shifted from chasing the top of the leaderboard to chasing cost-per-task. GPT-5.6 Terra got a smaller trim to $2/$12. This is the same commoditization current we covered when OpenAI made unlimited text chat free — the moat is moving from capability to price, and it's moving fast.

Qwen3.8-Max (August 3). Alibaba's most capable model yet: 2.4 trillion parameters with 95 billion active per token (sparse MoE), a 1M-token context, and multimodal text/image/video input, priced at $2/$6. The caveat matters: most of its headline scores are self-reported, with independent verification still thin as of this writing. It's a real contender, but treat the numbers as claims until a neutral index confirms them — the discipline we lay out in how to read a coding-agent benchmark.

Why this is one story, not three#

Read together, the three moves say the same thing: the coding-model market has crossed from a capability race into a price war. The top of the SWE-bench Verified board — Claude Opus 4.8 at 88.6, GPT-5.6 Sol nearby — barely moved this quarter. What moved is the cost of getting most of the way there. A model that scores 79 for 14 cents a million tokens changes the math for every founder who was quietly paying frontier rates to do work that never needed a frontier model.

The leaderboard stopped being the buying decision. When "good enough" costs one-thirtieth of "best," the decision is a routing problem, not a ranking one.

What a founder should do this week#

1. Put the model behind an environment variable. If you can't swap models with a config change, that's the first bug to fix — because the right model is now going to change on you monthly. Our walkthrough of why the best coding model is half a harness makes the case that the scaffolding matters more than the pick.

2. Split your traffic by task. Send high-volume, lower-stakes work — agent loops, CI, first-pass edits — to a cheap floor model like DeepSeek V4 Flash or post-cut Luna. Keep a frontier model on call for the small share of tasks where ten SWE-bench points decide between a clean merge and a rollback. The running-cost math for this split is in what it actually costs to run a coding agent this month, and if you want to self-host the floor, DeepSeek V4 vs GLM-5.2 vs Qwen is the pick-by-license guide.

3. Don't trust the switch until you've measured it. A 79 on a public benchmark is not a 79 on your repository. Before you move production traffic to a cheaper model, run a private eval on your real tasks — here's how to build one. The whole point of a swappable market is that you can afford to test, and the whole risk is assuming the leaderboard transfers to your codebase.

4. Re-price your own product. If your unit economics were drawn against $5/$25 tokens, the floor just dropped under you — and under every competitor. That's either a margin gift or a pricing-pressure warning, depending on whether you pass it on. Decide on purpose, before the market decides for you.

The one rule under all of it#

Prices this volatile are a feature, not a crisis — if your architecture treats the model as swappable. The founders who win the next quarter aren't the ones who guessed which model would be cheapest in August; they're the ones who built so that the answer doesn't matter. Keep the model behind a variable, route by task, verify on your own data, and let the price war happen to your bill in your favor.