identity

open weights
DeepSeek logo

deepseek-v4.1-flashDeepSeek

from /1M in$0.15runware
context1.0M393K out
best ttft338mstogether ai
price spread3.3x12 endpoints
endpoints
12
regions
2
best tok/s
320
api
chat
released
September 2026
eu routing
available

capabilities 6/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

The same weights cost 3.3x more on lyceum than on runware. That is what the endpoints table is for.

endpoints

12 / 2 regions
Providers serving deepseek-v4.1-flash, with pricing and measured performance. Best value in each column is coloured.
#flags
1RunwareGlobal1.0M$0.15$0.60$0.011.67s75.0zdr
2DeepInfraGlobal1.0M$0.16$0.48$0.00481.49s61.0-zdr
3DeepInfraGlobal1.0M$0.20$0.60$0.00601.49s61.0-zdr
4Fireworks AIGlobal1.0M$0.22$0.66$0.00701.29s61.0-zdr
5MeliousEU1M$0.23$1.14$0.02775ms69.0zdr
6DeepSeekGlobal1M$0.30$1.20$0.00601.20s122.0-no-train
7Novita AIGlobal1.0M$0.30$1.20$0.00602.92s94.0-zdr
8TencentGlobal1.0M$0.30$1.20$0.00601.78s24.0-no-train
9Together AIGlobal1.0M$0.30$1.20$0.01338ms227.0-zdr
10LyceumEU1.0M$0.50$1.50$0.131.59s267.0zdr
11sferenceEU1.0M$0.50$1.50$0.05562ms243.0zdr
12TensorXEU1.0M$0.50$1.50$0.132.03s320.0zdr
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Nov 2
median
-508ms2.97s6.45s08-3109-2811-023.16s2.80s2.50s2.31s1.81s1.80s1.42s1.28s1.21s749ms652ms
hover the plot for weekly values
time to first token per provider: current value, window low and high, and change across the window
providernowlowhighchange
Together AI338ms370ms2.80s+381%
sference562ms71ms794ms+955%
Melious775ms608ms689ms+7.2%
DeepSeek1.20s752ms1.50s+70%
Fireworks AI1.29s1.19s2.31s+71%
DeepInfra1.49s1.05s1.93s+36%
Lyceum1.59s627ms2.50s+300%
Runware1.67s1.60s2.10s-5.4%
Tencent1.78s1.71s5.87s-69%
TensorX2.03s1.00s1.48s+19%
Novita AI2.92s2.08s4.08s-4.6%

median wait before the first token lands. this is the number a user feels, and it moves with provider load through the day.

Lines are steps: each sample is one week of traffic held flat, not a slide from the week before. Click a name in the key to drop it from the plot. Measured through Nov 2.

benchmarks

artificial analysis

no published benchmark scores for this model

call it

model=
deepseek-v4.1-flash

requesty routes this id across every provider serving deepseek-v4.1-flash, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it

Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.

quickstart

openai compatible
main.py
from openai import OpenAI client = OpenAI(    api_key="YOUR_REQUESTY_API_KEY",    base_url="https://router.requesty.ai/v1",) response = client.chat.completions.create(    model="deepseek-v4.1-flash",    messages=[        {"role": "user", "content": "Explain quantum computing in one paragraph."},    ],) print(response.choices[0].message.content)

Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models

notes

reference

DeepSeek V4.1 Flash is a 552B parameter Mixture of Experts model built on a new Causal Encoder Decoder architecture that activates only 8B parameters for input and 16B for output, giving frontier level intelligence at a fraction of the cost. It is the smallest model in the new DeepSeek architecture family and the first Flash with native vision and multimodal understanding. V4.1 Flash beats DeepSeek V4 Pro on performance, cost, speed and task completion time and scores 88.1 on CyberGym. Its KV cache is compressed to 890 bytes per token, four times smaller than V4 Flash and over 400 times smaller than V1, cutting the cache hit costs that dominate agent workloads. 1M token context window, 384K max output, thinking and non thinking modes, tool calling, JSON output and prompt caching. Pricing per 1M tokens starts at $0.003 for cache hits, $0.15 input and $0.60 output off peak, with peak rates at double (01:00 to 04:00 and 06:00 to 10:00 UTC, Monday to Friday). Open weights are published on Hugging Face. Ideal for coding agents, long context RAG, high throughput batch processing and multimodal assistants. Replaces deepseek-v4-flash and deepseek-v4-flash-vision-exp, both still accepted as aliases.

questions 7

Which providers serve deepseek-v4.1-flash?
deepseek-v4.1-flash is available from 11 providers through Requesty: Runware, DeepInfra, Fireworks AI, Melious, DeepSeek, Novita AI. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does deepseek-v4.1-flash cost?
Pricing starts at $0.15 per million input tokens and $0.48 per million output tokens on the cheapest provider. Prices vary by provider and region; the table above shows every endpoint. Requesty charges exactly what the upstream provider charges, with no markup.
Is deepseek-v4.1-flash open weights?
Yes. deepseek-v4.1-flash is an open-weights model from DeepSeek, which is why multiple inference providers can host it. Provider choice affects price, latency, and data-privacy terms, all compared above.
What is the context window of deepseek-v4.1-flash?
deepseek-v4.1-flash supports up to 1.0M tokens of context, with up to 393K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
Which provider is fastest for deepseek-v4.1-flash?
In recent production traffic through Requesty, Together AI had the lowest median time to first token (338ms) for deepseek-v4.1-flash. Latency shifts over time, so Requesty's latency-based routing picks the fastest healthy provider per request automatically.
How do I use deepseek-v4.1-flash with the OpenAI SDK?
Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "deepseek-v4.1-flash" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call deepseek-v4.1-flash by its managed id or a provider id?
Use the managed id, "deepseek-v4.1-flash". Requesty picks which of the 11 providers serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. There is also an EU-only id, "deepseek-v4.1-flash@eu", which routes the same way but only through EU-hosted providers. Send a provider id like "runware/deepseek-v4.1-flash" only when you need one specific deployment and want no failover.

more from deepseek 6

Other DeepSeek models
modelcontextfrom /Mproviders
deepseek-v4.1-flash-10171.0M$0.108
deepseek-v4-flash-vision-exp1.0M$0.221
deepseek-v4-pro-08131.0M$1.305
deepseek-v4-flash-07311.0M$0.0710
deepseek-v4-pro-04241.0M$1.044
deepseek-v4-flash-04241.0M$0.074

route deepseek-v4.1-flash through one endpoint

One key for 11 providers on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology

deepseek-v4.1-flash11 providers12 endpointsfrom $0.15 /1M inctx 1.0Mttft 338msspread 3.3xupdated Nov 2