deepseek-v4-flash-ga-260731) corresponds to DeepSeek-V4-Flash-0731,
the open-source checkpoint DeepSeek promoted to general availability on July 31, 2026. The
architecture matches the April preview (284B total / 13B activated MoE, 1M context) and
DeepSeek states only the post-training stage was redone — yet agent benchmarks improved
sharply. APIYI has completed 21 test cases plus a dedicated dual-endpoint retest;
both Chat Completions and Responses are callable directly.
APIYI has launched DeepSeek V4 Flash GA: model name
deepseek-v4-flash-ga-260731,
available on the default / svip groups. Note that this model thinks a lot by default —
pass thinking: {"type": "disabled"} explicitly for simple tasks (see “Thinking control” below).Key Advantages
1M context that holds up
Hard input ceiling of 1,048,570 tokens. A 322K-token needle-in-a-haystack test returned in 14.77s with a correct hit; max output is 393,216 tokens.
Two caching layers
Implicit cache needs no configuration and hits 99.9% on round two; Responses adds chained explicit caching that hits the entire prior context.
Concurrency without throttling
All 20 parallel requests returned 200, with wall-clock only 1.3s above a single call — suited to high-concurrency agents and batch text jobs.
Pricing
$0.44 input / $1.32 output per 1M tokens, with cache hits as low as $0.0136. DeepSeek moved to two-tier peak/off-peak billing on 17 August 2026; APIYI bills the peak tier at all times.
Model Information
Measured Capability Matrix
Results from APIYI testing on August 5, 2026 (official claims vs actual behavior):Thinking Control
This model thinks a lot by default — a one-line question like “is 9.11 bigger than 9.9” consumed 263 reasoning tokens in our tests (the siblingdeepseek-v4-flash used only 44).
Disable it explicitly for simple tasks:
Caching
Implicit cache (automatic on both endpoints)
For APIYI’s OpenAI-compatible/v1/chat/completions endpoint, the default group already supports cache billing; you do not need to select ClaudeCode.
Actual cache hits depend on the request context and are not guaranteed.
In our tests, an identical long prefix hit on the second request: a 15,634-token prefix matched 15,616
tokens (99.9%), billed at $0.028 per million tokens.
Explicit cache (Responses, requires chaining)
Common mistake: resending the same long prefix twice withcaching set leaves
cached_tokens at 0. The correct pattern is to write on the first call, then chain with
previous_response_id:
Quick Start
Need structured output? Use Function Call
response_format has no effect on this model and raises no error — the easiest trap to fall
into. Tool arguments are what actually get constrained:
Pricing
DeepSeek switched to two-tier billing at 00:00 on 17 August 2026 (UTC+8), with off-peak at half
the peak rate. APIYI bills the peak tier at all times, with no time-of-day variation — see
the DeepSeek price change notice. Stacks with
top-up promotions to reduce your effective cost further.
On “less than 1/10th of the flagship”: the vendor’s marketing compares against V4-Pro’s
preview-era $1.74 / $3.48. Against V4-Pro’s current price ($1.32 / $3.96),
this model is roughly 1/3, not 1/10.
Related Pages
Chat Completions
OpenAI-compatible chat endpoint with an interactive playground
Responses
Responses endpoint with chained explicit caching
Launch write-up and full test data
Benchmarks, three-way speed comparison, and the traps we hit
Model pricing table
Unit prices, endpoints and groups for every model