AI KNOWLEDGE DESK

Models · entities · concepts · comparisons · practical tools

GETLLMS.ORG
Why it matters

Existing evaluations and self-hosted deployments can still refer to the 0731 checkpoint, but the hosted legacy ID no longer identifies that model. That distinction matters for reproducibility: V4.1 Flash adds native image input, a different architecture, new prices, and a new open checkpoint.

Source-backed summary

Checked October 21, 2026 against the current linked primary source. Earlier release chapters retain their original scope; publisher changes are not independent runtime validation.

Primary use cases
  • Run cost-sensitive coding agents through the DeepSeek API.
  • Connect Codex clients to a Responses-compatible DeepSeek endpoint.
  • Build long-context text workflows with function calling or server-side web search.
  • Self-host the official MIT checkpoint with vLLM or SGLang on suitable multi-GPU hardware.
  • Compare Flash and the current V4 Pro 0813 hosted endpoint on the same tasks, budget, and harness.
The legacy API ID no longer pins this model

DeepSeek retired V4 Flash on September 10. The legacy `deepseek-v4-flash` name is still accepted for compatibility, but it routes to V4.1 Flash and uses V4.1 Flash pricing. Use the new `deepseek-flash` ID for current hosted work, and use the dated 0731 checkpoint only when you deliberately want the older open model.

  • DeepSeek

    The company behind the V4 model family, DeepSeek Chat, public APIs, and open-weight research releases.

What changed on July 31

The request model remains `deepseek-v4-flash`, but DeepSeek now identifies the backend version as `DeepSeek-V4-Flash-0731`. The company says it keeps the preview model's architecture and size and changes only post-training. The API remains in public beta, while an official MIT-licensed 0731 checkpoint now supersedes the preview weights. V4 Pro and the DeepSeek App/Web models were not upgraded by the API announcement.

  • Request model ID: `deepseek-v4-flash`.
  • Current API version and official checkpoint: `DeepSeek-V4-Flash-0731`.
  • Release status: official API release in public beta, not an unconditional general-availability claim.
Why attention surged after the 0731 update

The release joined three signals that developers could test immediately: DeepSeek reported a large coding-agent improvement without increasing the model size, Artificial Analysis measured the max-effort model among the leading open-weight models in its class, and existing agent products already exposed the stable V4 Flash endpoint. OpenCode reported V4 Flash as its top model in the latest weekly usage snapshot, but that is platform-specific usage for the V4 Flash line rather than global market share or a clean 0731-only cohort.

  • Artificial Analysis reported an Intelligence Index score of 50 and about 103 output tokens per second for the max-effort model on August 6.
  • OpenCode reported 58% of observed weekly Go usage for V4 Flash in its August 6 snapshot.
  • The stable API model ID and direct availability in coding-agent products reduced migration and trial friction.
Responses API and Codex support

Historical 0731 contract: V4 Flash supports the stateless `/responses` endpoint and DeepSeek publishes a Codex provider configuration using `wire_api = "responses"`. The text model accepts messages, reasoning items, function calls, function results, and server-side web-search calls, but not image inputs; multimodal requests require the separate `deepseek-v4-flash-vision-exp` model.

  • Responses conversations are stateless, so clients resend the full conversation history.
  • Reasoning effort maps to low, high, or max behavior; thinking is enabled by default.
  • Function tools and server-side web search are supported; image and file inputs are not.
Historical 0731 price versus the current alias

The 0731 model used off-peak rates of $0.007 cache-hit input, $0.22 cache-miss input, and $0.66 output per 1M tokens, with peak rates twice as high. The legacy API ID now routes to V4.1 Flash instead. Current V4.1 Flash rates are lower for cache hits and misses and slightly lower for output, so billing evidence after September 10 should not be attributed to the retired 0731 model.

Open weights do not mean lightweight local inference

DeepSeek publishes the official 0731 checkpoint under the MIT License with vLLM and SGLang serving instructions. The model is still large: its official high-performance vLLM example uses a four-GB300 node, so local deployment is primarily a multi-GPU or heavily quantized workflow rather than a routine laptop setup. Choose the hosted API when operational simplicity matters and self-host only when hardware, quantization quality, privacy, or sustained volume justify it.

Treat launch benchmarks as vendor-reported

DeepSeek reports large gains on agent benchmarks, including Terminal Bench 2.1, DeepSWE, Toolathlon verified, and internal DSBench sets. These are vendor-reported results, not independent proof. The public coding-agent runs used an unreleased DeepSeek Harness minimal mode with max effort, top-p 0.95, and temperature 1.0, while two DSBench sets are internal.

Current legacy-route destination

The 0731 checkpoint and the launch conditions described above are historical. Today the legacy text Flash ID is a compatibility route to DeepSeek-V4.1-Flash-1017 under deepseek-flash. The current Flash contract supports multimodal input and separate Search/Fetch billing. A successful call through the old ID therefore does not test the original 0731 weights, prices or text-only behavior. Use the current V4.1 guide for a new hosted integration.

DeepSeek V4 Flash FAQ

Common questions about DeepSeek V4 Flash.

Is DeepSeek V4 Flash generally available?+

The original V4 Flash hosted model is retired. Its legacy API ID is still accepted temporarily, but requests are served by V4.1 Flash. The dated 0731 checkpoint remains available for deliberate self-hosting or historical evaluation.

Does DeepSeek V4 Flash support the Responses API and Codex?+

The original V4 Flash supported the Responses API and Codex integrations, but the legacy hosted ID now routes to V4.1 Flash. Update integrations to `deepseek-flash` when you want the current model and revalidate behavior instead of relying on the old name.

Does DeepSeek V4 Flash accept images?+

The original 0731 checkpoint does not accept images. The hosted legacy ID now routes to multimodal V4.1 Flash, so request behavior has changed without the old name disappearing. Use `deepseek-flash` for the current hosted model and keep historical checkpoint claims separate.

Why did DeepSeek V4 Flash become popular after the 0731 update?+

The 0731 release combined a large vendor-reported coding-agent gain with very low API prices, independent evaluation, a stable request ID, direct coding-agent integrations, and official open weights. That made the model cheap and easy to test in real repositories instead of leaving interest at the benchmark-discussion stage.

Can DeepSeek V4 Flash 0731 run locally?+

Yes, DeepSeek publishes the official 0731 checkpoint under the MIT License with vLLM and SGLang instructions. It is not a lightweight local model: the official high-performance example uses four GB300 GPUs, so most individual users need substantial shared memory, aggressive quantization, or a hosted provider.

Is DeepSeek V4 Flash now better than V4 Pro?+

That is not established for every workload. DeepSeek reports much stronger agent benchmark scores for the updated Flash API, but the July 31 release did not update V4 Pro, some tests use an unreleased harness, and two DSBench sets are internal. Compare both endpoints on the same real tasks, tools, effort, latency, and budget.