DeepSeek V4.1 Flash 1017 is the October 17, 2026 snapshot of DeepSeek V4.1 Flash, served by DeepSeek under the deepseek-flash API model name. 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.038 | $0.50 | $0.005 | 0.36s | 153 tps | ||
| $0.035 | $0.50 | $0.005 | 0.71s | 138 tps | ||
| $0.18 | $0.72 | $0.006 | 0.79s | 169 tps | ||
| $0.16 | $0.50 | $0.008 | 0.31s | 155 tps | ||
| $0.165 | $0.495 | $0.0105 | 0.52s | 119 tps | ||
| $0.17 | $0.67 | $0.006 | 0.82s | 130 tps | ||
| $0.035 | $0.50 | $0.005 | 0.88s | 103 tps | ||
| $0.30 | $1.20 | $0.006 | 0.24s | 229 tps | ||
| $0.156 | $1.20 | $0.006 | 0.70s | 183 tps | ||
| $0.195 | $0.78 | $0.0039 | 0.44s | 178 tps | ||
| $0.195 | $0.66 | $0.006 | 0.40s | 166 tps | ||
| $0.08 | $0.55 | $0.008 | 0.37s | 102 tps | ||
Fast | $0.30 | $0.90 | $0.008 | 0.45s | 295 tps | |
| $0.29 | $1.20 | $0.007 | 0.51s | 176 tps | ||
| $0.08 | $0.55 | $0.008 | 0.38s | 92 tps | ||
| $0.25 | $1.00 | $0.005 | 0.52s | 159 tps | ||
| $0.33$0.165 | $1.32$0.66 | $0.033$0.0165 | 0.72s | 115 tps | ||
| $0.30 | $1.20 | $0.006 | 0.97s | 153 tps | ||
| $0.30 | $1.20 | $0.007 | 1.03s | 178 tps | ||
| $0.05 | $0.192 | $0.008 | 0.76s | 83 tps | ||
| $0.30 | $1.20 | $0.007 | 0.57s | 132 tps | ||
35% off | $0.30$0.195 | $1.20$0.78 | $0.006$0.0039 | 1.28s | 94 tps | |
| $0.10 | $0.60 | $0.003 | 1.66s | 88 tps | ||
| $0.195 | $0.78 | $0.0039 | 0.89s | 103 tps | ||
| $0.06 | $0.60 | $0.006 | 1.36s | 85 tps | ||
| $0.28 | $1.13 | $0.006 | 1.44s | 89 tps | ||
50% off | $0.30$0.15 | $1.20$0.60 | $0.006$0.003 | 2.23s | 87 tps | |
| $0.30 | $1.20 | $0.006 | 1.01s | 120 tps | ||
40% off | $0.30$0.18 | $1.20$0.72 | $0.006$0.0036 | 2.18s | 95 tps | |
| $0.101 | $0.15 | $0.006735 | 0.47s | 51 tps | ||
| $0.20$0.098 | $0.60$0.294 | $0.006$0.00294 | 1.47s | 51 tps | ||
| $0.20 | $1.20 | $0.006 | 1.56s | 100 tps | ||
| $0.30 | $1.20 | $0.0075 | 1.23s | 107 tps | ||
| $0.30 | $1.20 | $0.006 | 1.32s | 135 tps | ||
| $0.101 | $0.15 | $0.006735 | 0.44s | 48 tps | ||
| $0.30 | $1.20 | $0.006 | 0.92s | 101 tps | ||
| $0.30 | $1.20 | $0.006 | 0.63s | 40 tps | ||
| $0.21 | $0.84 | $0.0042 | 0.56s | 162 tps | ||
18% off | $0.15$0.123 | $0.60$0.492 | $0.003$0.00246 | 1.12s | 131 tps | |
| $0.30$0.147 | $0.90$0.441 | $0.009$0.00441 | 1.12s | 45 tps | ||
| $0.15 | $0.60 | $0.003 | 1.07s | 95 tps | ||
| $0.05 | $0.50 | $0.003 | -- | -- | ||
| $0.15 | $1.20 | $0.006 | -- | -- | ||
Standard ルーティングでは使用されません:これらのエンドポイントが使用されない理由 | ||||||
| $0.16$0.0784 | $0.48$0.2352 | $0.0048$0.002352 | 3.09s | 37 tps | ||
| $0.45 | $1.80 | $0.009 | 1.04s | 162 tps | ||
P50、プロバイダー全体での最良値
P50、最適なプロバイダー
上流のプロバイダーでエラーが発生した場合、リクエストフィルターが許可していれば、別の正常なプロバイダーにルーティングして復旧できます。プロバイダーごとの稼働率データにプログラムでアクセスするには Endpoints APIを利用できます。詳しくは、 負荷分散とプロバイダールーティングのオプションをご覧ください。
