DeepSeek V4 Flash (0731) vs DeepSeek V4 Pro (0813)
何時該用哪一個 — 綜合評斷，而非基準測試數據表
這兩個 DeepSeek 兄弟模型在規格上配置完全相同：皆具備 1000000-token 的上下文視窗、393216 最大輸出 tokens、純文字輸入/輸出，以及相同的聊天、程式碼、推理與工具標記。規格表上唯一真正的差異在於定價表，deepseek-v4-pro-0813 在每個層級的成本大約貴了 4.29 倍（輸入為 $1.32 對 $0.308，輸出為 $3.96 對 $0.924，快取讀取為 $0.132 對 $0.0308）。對於高流量工作請預設使用 deepseek-v4-flash-0731，只有在您的內部評估證明其溢價合理時，才考慮使用 0813 Pro 層級。
定價
| DeepSeek V4 Flash (0731) | DeepSeek V4 Pro (0813) | Δ | |
|---|---|---|---|
| 輸入 / 1M tokens | $0.308 | $1.32 | 0.23× |
| 輸出 / 1M tokens | $0.924 | $3.96 | 0.23× |
| 快取讀取 / 1M tokens | $0.0308 | $0.132 | 0.23× |
| 快取寫入 | 不額外計費 | 不額外計費 | — |
費率取自建置時的即時目錄；各模型頁面皆附有目前的費率卡。
它們的相對位置 — 在此計費單位下，所有 63 個 聊天 模型的 每 1M tokens 的輸入價格（對數尺度）
能力
| DeepSeek V4 Flash (0731) | DeepSeek V4 Pro (0813) | |
|---|---|---|
| 工具使用 | 是 | 是 |
| 思考控制 | 是 —— 廠商未公布調節參數 | 常駐開啟 |
| 結構化輸出 | 是 | 是 |
| 提示快取 | 隱式（自動） | 隱式（自動） |
| 快取生命週期 | no fixed TTL (evicted when unused) | no fixed TTL (evicted when unused) |
| 最小快取前綴 | 未公開 | 未公開 |
規格
| DeepSeek V4 Flash (0731) | DeepSeek V4 Pro (0813) | |
|---|---|---|
| 輸入模態 | 文字 | 文字 |
| 輸出模態 | 文字 | 文字 |
| 發布日期 | 2026-07-31 | 2026-08-13 |
| 上下文視窗 | 1M | 1M |
| 最大輸出 | 393K | 393K |
| 思考參數 | — | reasoning_effort |
| 可接受的值 | — | reasoning_effort
|
規格摘錄自各供應商的文件；供應商未發布的資料列會直接省略，而非自行推測。 完整來源： DeepSeek V4 Flash (0731) · DeepSeek V4 Pro (0813)
單一提示詞，兩款模型 — 經由閘道測量
DeepSeek V4 Flash (0731) 通過 · 3 sentences
Enabling reasoning mode prompts the model to generate extensive internal chain-of-thought tokens before answering, often multiplying total token output per query by several times. This directly inflates costs because we are billed per token, and these reasoning tokens are processed at a premium compute tier that carries a higher price per million tokens. However, this spend buys measurably higher accuracy and fewer failed calls, so we are tracking it against specific error-reduction KPIs to ensure the ROI justifies the increase.
輸出 365 tok (+266 思考) 延遲 5.1 s
DeepSeek V4 Pro (0813) 通過 · 3 sentences
Enabling reasoning causes the model to generate a hidden chain-of-thought with many additional tokens before producing the final answer, which sharply increases compute consumption per request. Those extra reasoning tokens are billed at the same or higher rates, so total usage doubled even though the volume of final outputs stayed similar. We can control this by adjusting reasoning effort, setting token limits, or routing only complex requests through reasoning mode.
輸出 308 tok (+226 思考) 延遲 5.1 s
指令遵循（恰好三句，可數）、受眾適配（面向 CFO 的語氣），以及下方 token 計量所暴露的隱藏思考計費缺口。
DeepSeek V4 Flash (0731) 通過 · 8/8 cases
```python def longest_run(xs): if not xs: return 0 best = 1 cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 best = max(best, cur) else: cur = 1 return best ``` The original bug stems from initializing `cur` to 0 and only incrementing it when adjacent elements are equal, which counts the number of *equal transitions* rather than the actual run length—so every run of length L is reported as L−1, and a single‑element run (with no transitions) yields 0. Moreover, because `best` is updated only inside the equality branch, it never accounts for a run that ends at the last element if that run is longer than any previously seen (though the real issue remains the off‑by‑one). […]
輸出 1268 tok (+1016 思考) 延遲 14.0 s
DeepSeek V4 Pro (0813) 通過 · 8/8 cases
```python def longest_run(xs): if not xs: return 0 best = 1 cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 best = max(best, cur) return best ``` The bug is that `cur` was initialized to `0` and only counted adjacent matching pairs, so a run of length `n` produced `n - 1` (or `0` for a single element) instead of `n`. The code also reset to `0` on a change, when the new run should start at length `1`. Initializing `cur` and `best` to `1` fixes both the single-element case and runs ending at the last index.
輸出 1315 tok (+1130 思考) 延遲 16.9 s
修復是否真的正確（可執行）、解釋的資訊密度，以及在一個邊界明確的任務上的 token 效率。
DeepSeek V4 Flash (0731) 通過 · 5/5 fields, guidance null
{ "company": "Meridian Robotics", "quarter": "Q3", "revenue_usd_m": 412, "growth_pct": null, "guidance": null }
輸出 1119 tok (+1072 思考) 延遲 12.3 s
DeepSeek V4 Pro (0813) 通過 · 5/5 fields, guidance null
{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":11.0,"guidance":null}
輸出 2155 tok (+2121 思考) 延遲 26.0 s
schema 服從度（不臆造欄位）、幻覺壓力（guidance 明確被暫緩給出），以及結構化輸出路徑的差異。
DeepSeek V4 Flash (0731) 未命中 · 141 words, 0 banned, 1 question
**Introducing Prompt Cache for API Gateway** We are pleased to announce Prompt Cache, a new feature that stores and reuses identical prompt prefixes across all connected LLM providers. By automatically recognizing repeated requests, this cache reduces token consumption and lowers latency without altering your application logic. Whether you use OpenAI, Anthropic, or open-source models, the cache operates transparently, ensuring consistent behavior while cutting costs. Developers can configure cache TTL and scoping rules via a simple API call, giving you precise control over data freshness and privacy. This feature also minimizes redundant upstream calls, freeing provider rate limits for more critical workloads. Start caching today through the dashboard or CLI, and watch your operational expenses drop significantly. […]
輸出 254 tok (+80 思考) 延遲 4.4 s
DeepSeek V4 Pro (0813) 通過 · 121 words, 0 banned, 1 question
Introducing cross-provider prompt caching in our API gateway. Send a prompt once, and the gateway stores its computed prefix across Anthropic, OpenAI, and other LLM providers. Subsequent requests with the same prompt hit the cache, cutting latency and token costs while keeping outputs consistent across routing decisions and provider failovers. Teams can route identical prompts between providers without reprocessing shared context or lengthy system instructions. How much could you save on repeated prompt prefixes? The cache respects provider-specific key formats, handles TTLs automatically, and works with streaming and batch requests. Enable it with one configuration flag—no changes to your application code. Available today on all plans. Monitor cache hit rates, token savings, and provider-specific performance metrics in the live dashboard.
輸出 2845 tok (+2694 思考) 延遲 25.5 s
約束服從度（字數預算、禁用詞表、唯一的那句問句）、文風指紋，以及長度控制。
只需一行程式碼即可在兩者間切換
以下每個頁籤中都有這兩個 ID — 醒目提示的這兩行是唯一的修改處。相同的端點，相同的金鑰，相同的請求結構。
from openai import OpenAI
client = OpenAI(
base_url="https://synthorai.io/v1",
api_key="sk-syn-...",
)
resp = client.chat.completions.create(
model="deepseek-v4-flash-0731",
# model="deepseek-v4-pro-0813", # 取消註解此行，並註解上一行
messages=[{"role": "user", "content": "Summarize this diff"}],
reasoning_effort="medium",
)
print(resp.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://synthorai.io/v1",
apiKey: "sk-syn-...",
});
const resp = await client.chat.completions.create({
model: "deepseek-v4-flash-0731",
// model: "deepseek-v4-pro-0813", // 取消註解此行，並註解上一行
messages: [{ role: "user", content: "Summarize this diff" }],
reasoning_effort: "medium",
});
console.log(resp.choices[0].message.content);curl https://synthorai.io/v1/chat/completions \
-H "Authorization: Bearer sk-syn-..." \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek-v4-flash-0731",
# "model": "deepseek-v4-pro-0813", # 取消註解此行，並註解上一行
"messages": [{"role": "user", "content": "Hello"}],
"reasoning_effort": "medium"
}'package main
import (
"context"
"fmt"
"github.com/openai/openai-go/v3"
"github.com/openai/openai-go/v3/option"
)
func main() {
client := openai.NewClient(
option.WithBaseURL("https://synthorai.io/v1"),
option.WithAPIKey("sk-syn-..."),
)
resp, _ := client.Chat.Completions.New(context.TODO(), openai.ChatCompletionNewParams{
Model: "deepseek-v4-flash-0731",
// Model: "deepseek-v4-pro-0813", // 取消註解此行，並註解上一行
Messages: []openai.ChatCompletionMessageParamUnion{
openai.UserMessage("Summarize this diff"),
},
ReasoningEffort: openai.ReasoningEffortMedium,
})
fmt.Println(resp.Choices[0].Message.Content)
}import com.openai.client.OpenAIClient;
import com.openai.client.okhttp.OpenAIOkHttpClient;
import com.openai.models.chat.completions.*;
import com.openai.models.ReasoningEffort;
OpenAIClient client = OpenAIOkHttpClient.builder()
.baseUrl("https://synthorai.io/v1")
.apiKey("sk-syn-...")
.build();
ChatCompletion resp = client.chat().completions().create(
ChatCompletionCreateParams.builder()
.model("deepseek-v4-flash-0731")
// .model("deepseek-v4-pro-0813") // 取消註解此行，並註解上一行
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));常見問題
DeepSeek V4 Flash (0731) 和 DeepSeek V4 Pro (0813) 哪個比較便宜？
DeepSeek V4 Flash (0731) 在 輸入 / 1m tokens 上較便宜（$0.308 對比 $1.32，相差 4.3×）。其他項目可能呈現相反結果 — 上表提供完整資訊，實際成本取決於您的使用組合。
我可以在不進行兩次整合的情況下，對 DeepSeek V4 Flash (0731) 和 DeepSeek V4 Pro (0813) 進行 A/B 測試嗎？
可以。兩者皆透過同一個相容 OpenAI 的端點提供服務，並使用同一把 API 金鑰 — 切換只需更改一行的模型字串，因此您可以將部分流量分別導向兩者並直接比較帳單。
DeepSeek V4 Flash (0731) 與 DeepSeek V4 Pro (0813) 支援提示快取嗎？
是的 — 兩者的快取讀取費率皆低於其輸入費率，因此具有暖前綴的工作負載成本會低於牌價所示。確切的快取讀取列請見上方的定價表。