
DeepSeek V4.1 Flash is a sparse mixture-of-experts model from DeepSeek, and the first built on the company's Causal Encoder-Decoder (CED) architecture. It activates 8B parameters on input and 16B on output from a 552B-parameter backbone, an asymmetric split that keeps per-token compute low relative to the model's total size. Image understanding is native to the architecture, with visual and text embeddings trained jointly from the start of pre-training rather than added afterward as in the earlier experimental V4 Flash Vision ExpOpens in new tab.
It is suited for coding, terminal, and computer-use agents, along with long-horizon tasks that must run to completion across many steps and long-context analysis. Compressed KV caching cuts cache memory to roughly a quarter of the previous Flash generation, significantly reducing costs on agentic workloads. DeepSeek positions it as the cost-efficient tier of the V4.1 family and reports that it exceeds V4 ProOpens in new tab on performance, speed, and task completion time.
| $0.0077 | $0.60 | $0.005 | 1.39s | 80 tps | ||
| $0.029 | $1.00 | $0.009 | 1.30s | 76 tps | ||
| $0.05 | $1.60 | $0.049 | 0.81s | 148 tps | ||
| $0.08 | $0.40 | $0.01 | 1.16s | 54 tps | ||
| $0.09 | $0.18 | $0.018 | 1.48s | 50 tps | ||
| $0.10 | $1.10 | $0.01 | 0.83s | 48 tps | ||
| $0.105 | $0.60 | $0.015 | 1.35s | 113 tps | ||
| $0.12 | $1.20 | $0.005 | 2.37s | 65 tps | ||
| $0.20$0.14 | $0.60$0.42 | $0.006$0.0042 | 1.31s | 46 tps | ||
50% off | $0.30$0.15 | $1.20$0.60 | $0.006$0.003 | 1.75s | 135 tps | |
| $0.15 | $0.60 | $0.003 | 1.04s | 148 tps | ||
| $0.165 | $0.66 | $0.006 | 0.75s | 174 tps | ||
40% off | $0.30$0.18 | $1.20$0.72 | $0.006$0.0036 | 3.18s | 117 tps | |
35% off | $0.30$0.195 | $1.20$0.78 | $0.006$0.0039 | 2.21s | 93 tps | |
| $0.20 | $0.65 | $0.03 | 0.69s | 190 tps | ||
30% off | $0.30$0.21 | $1.20$0.84 | $0.006$0.0042 | 1.90s | 68 tps | |
| $0.27 | $1.15 | $0.009 | 1.00s | 124 tps | ||
| $0.29 | $1.20 | $0.007 | 0.73s | 113 tps | ||
| $0.30 | $1.20 | $0.006 | 1.22s | 191 tps | ||
| $0.30 | $1.20 | $0.03 | 1.45s | 155 tps | ||
| $0.30 | $1.20 | $0.007 | 0.36s | 214 tps | ||
| $0.30 | $1.20 | $0.03 | 1.13s | 86 tps | ||
| $0.30 | $1.20 | $0.006 | 0.32s | 215 tps | ||
| $0.30 | $1.20 | $0.006 | 2.14s | 91 tps | ||
| $0.30 | $1.20 | $0.03 | 0.51s | 157 tps | ||
| $0.30 | $1.20 | $0.007 | 0.32s | 156 tps | ||
| $0.30 | $1.20 | $0.006 | 0.80s | 145 tps | ||
| $0.30 | $1.20 | $0.0075 | 0.65s | 163 tps | ||
| $0.30 | $1.20 | $0.006 | 3.05s | 46 tps | ||
| $0.00979 | $0.36 | $0.0045 | 3.38s | 21 tps | ||
| $0.60 | $2.40 | $0.014 | 0.42s | 348 tps | ||
Not used in Standard routing:Why these endpoints are not used | ||||||
| $0.45 | $1.80 | $0.009 | 0.55s | 249 tps | ||
P50, best across providers
P50, best provider
When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and customization options.
