Loading the catalogue…
Loading the catalogue…
DeepSeek's unified multimodal MoE model combining native text+image input, a 1M-token context window, and a controllable reasoning-effort slider in one Flash-tier endpoint.
Overview. DeepSeek-V4.1-Flash is a multimodal Mixture-of-Experts model from DeepSeek, released in September 2026 as the unified successor to the separate V4 Flash, V4 Pro, and V4 Flash Vision text and vision models it replaces. It runs a 552B-parameter backbone with a sparse activation pattern (8B on prefill, 16B on decode) and takes native text and image input over a 1M-token context window. Developers consolidating separate text and vision workloads onto one endpoint, or needing very long-context Inference, are the natural audience.
Key strengths. The model routes each token through 6 of 384 routed experts plus a shared expert, giving it a large parameter backbone without paying the full dense-compute cost per token. Its vision encoder was trained jointly with the language model from the start of pre-training rather than bolted on afterward, so image and text are processed as a single native input stream. It also exposes a controllable reasoning-effort slider, letting a call opt into deeper deliberation for harder instructions or agentic steps. DeepSeek's own positioning describes this Flash tier as matching or exceeding its prior Pro-tier model on task completion, though that comparison comes from the vendor rather than an independent benchmark.
When to use it. Reach for this model when a workload mixes text and image input in a single call and needs to stay in one native multimodal path rather than juggling separate vision and text models. Its 1M-token context window suits long-document or long-conversation tasks that would otherwise need chunking. The reasoning-effort slider makes it a candidate for agentic or multi-step instruction-following tasks where you want to dial deliberation up only when the query warrants it, while defaulting to a faster interactive response otherwise.
Limitations. Independent latency and quality benchmarks are not yet available for this newly released model, so its interactive-tier speed claim currently rests on DeepSeek's own description rather than measured data. Tool-calling, structured output, and JSON-mode support have not been confirmed for this checkpoint, and its training data cutoff has not been published. Maximum output length is bounded to roughly 384K tokens by the current serving provider rather than an unlimited generation length.
| Inference Provider | Sovereignty | Runs in | In / out per 1M | Status | Pin |
|---|---|---|---|---|---|
| L1 | €0.45 / 1.35 | Online | |||
| L0 | €0.18 / 0.54 | Online | |||
| L0 | €0.20 / 0.59 | Online |
14 use cases classified by the curator. The note says why.
Combines tool-calling with a huge context window, enabling retrieval-augmented answer generation over large document sets in one pass.
1,048,576-token context window allows ingesting entire large documents or document sets in a single pass, a strong architectural fit for document Q&A.
Explicit tool-calling capability is the core requirement for function-calling apps; this variant supports it directly.
The 1M+ token context window supports synthesizing across many long source documents without chunking, a clear advantage for research synthesis tasks.
A 1M-token context window is well suited to summarizing very long documents or transcripts in a single call without truncation.
Native tool-calling support combined with a 1,048,576-token context window makes this a strong fit for orchestrating multiple tool calls across long-running agentic sessions.
Tool-calling and large context window support agentic coding loops, but the 'Flash' designation suggests a speed/cost-optimized tier likely below top-end coding benchmarks.
Open-weights, non-CLOUD-Act-exposed deployment plus a 1M-token context window suits audit workflows requiring ingestion of large document trails, though no audit-specific benchmarks exist.
Tool-calling support enables browser-automation workflows, though no agentic benchmark scores are published to confirm reliability at scale.
The huge context window allows reviewing large codebases in a single pass, but lack of published code benchmarks limits confidence to acceptable rather than strong.
Massive context window helps ingest multiple papers at once, though no domain-specific reasoning benchmarks are available to confirm quality of synthesis.
Tool-calling plus huge context window supports multi-step plans, but as the 'Flash' speed-tier variant it likely trades some reasoning depth for latency, so acceptable rather than strong absent benchmark confirmation.
Sourced numbers, not our own evaluations. Percentiles are against the whole Stav catalogue.
Computed from aa-intelligence-index, gpqa-diamond, aa-engineering-index, aa-coding-index, livecodebench, terminal-bench-v4, aa-lcr.
curl https://api.stav.ai/v1/chat/completions \
-H "Authorization: Bearer $STAV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek-ai/deepseek-v4-1-flash",
"reasoning_effort": "high",
"messages": [{"role": "user", "content": "Hello!"}]
}'→ X-Stav-Request-Id · X-Stav-Model · X-Stav-Provider → X-Stav-Sovereignty-Level — the rung the request was served at