新用戶 免費註冊,送 10 次呼叫,最高 $1,免綁卡。

DeepSeek V4 Pro (0813) vs DeepSeek V4.1 Flash

vs

何時用哪一個

兩者皆具備 1,000,000 token 的上下文長度與 393,216 token 的最大輸出,並支援聊天、程式碼、推理與工具使用,因此差異在於價格與輸入:deepseek-v4-pro-0813 每百萬輸入的費用為 $1.32,每百萬輸出為 $3.96,而較新的 deepseek-v4.1-flash 費用為 $0.3 與 $1.2,輸入約便宜 4.4x,輸出約便宜 3.3x,快取讀取為 $0.03 對比 $0.132。若為高用量工作或任何需要圖片輸入的任務,請選擇 deepseek-v4.1-flash,因為它加入了視覺功能。如果您必須使用該僅支援文字的 Pro 世代模型,請選擇 deepseek-v4-pro-0813。

Benchmark 成績

領先高於同儕均值無人分數更高DeepSeek V4 Pro (0813)214 / 211 / 21DeepSeek V4.1 Flash1316 / 194 / 19

雙方都被測過的 15 項。

DeepSeek V4 Pro (0813) DeepSeek V4.1 Flash 其他被測模型 同儕均值 無人分數更高
NL2Repo
61.5%
64%
Cybergym
83.3%
無人分數更高 88.1%
GDPval-AA v2 Elo · 1508-1769 據 Z.ai 公布 · 2026-09-04
1590
N/A
GPQA Diamond
92.4%
90.9%
Agents' Last Exam
25.7%
31.8%
BabyVision with tools
N/A
89.6%

廠商公布: Alibaba (Qwen) Anthropic ByteDance DeepSeek Google MiniMax Moonshot OpenAI Tencent Z.ai

定價

DeepSeek V4 Pro (0813) DeepSeek V4.1 Flash Δ
輸入 / 1M tokens $1.32 $0.3 4.4×
輸出 / 1M tokens $3.96 $1.2 3.3×
快取讀取 / 1M tokens $0.132 $0.03 4.4×
快取寫入 不額外計費 不額外計費 -

費率取自建置時的即時目錄;各模型頁面皆附有目前的費率卡。

它們的相對位置 — 在此計費單位下,所有 69 個 聊天 模型的 每 1M tokens 的輸入價格(對數尺度)

能力

DeepSeek V4 Pro (0813) DeepSeek V4.1 Flash
工具使用
思考控制 常駐開啟 是 —— 廠商未公布調節參數
結構化輸出 -
提示快取 隱式(自動) 隱式(自動)
快取生命週期 no fixed TTL (evicted when unused) no fixed TTL (evicted when unused)
最小快取前綴 未公開 未公開

規格

DeepSeek V4 Pro (0813) DeepSeek V4.1 Flash
輸入模態 文字 文字 影像
輸出模態 文字 文字
發布日期 2026-08-13 2026-09-10
上下文視窗 1M 1M
最大輸出 393K 393K
思考參數 reasoning_effort -
可接受的值
reasoning_effort
  • the model card documents low
  • high
  • max
-

規格摘錄自各供應商的文件;供應商未發布的資料列會直接省略,而非自行推測。 完整來源: DeepSeek V4 Pro (0813) · DeepSeek V4.1 Flash

單一提示詞,兩款模型 — 經由閘道測量

提示詞 Explain to a CFO, in exactly three sentences, why our LLM bill doubled after we enabled reasoning. 檢查 恰好 3 句

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

DeepSeek V4.1 Flash 通過 · 3 sentences

Enabling reasoning changed the unit economics: the model now spends extra billable tokens internally to “think” before producing the answer, and those reasoning tokens are charged like output tokens even though users never see them. That added token generation—plus longer contexts and occasional retries on harder prompts—roughly doubled our cost per request. We can control this by capping reasoning depth, routing only complex queries to reasoning models, and caching common prompts to bring the bill back down.

輸出 423 tok (+327 思考) 延遲 14.6 s

指令遵循(恰好三句,可數)、受眾適配(面向 CFO 的語氣),以及下方 token 計量所暴露的隱藏思考計費缺口。

提示詞 This function is supposed to return the longest run of consecutive equal items, but callers report it is off by one on single-element inputs and misses runs that end at the last index. Fix it and explain the bug in one paragraph. 檢查 修復通過測試

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

DeepSeek V4.1 Flash 通過 · 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` is counting equal adjacent pairs, not elements in the current run: every time `xs[i] == xs[i - 1]`, the run length increases by one element, but the first element of the run was never counted, so all runs are undercounted by one. Also, `best` starts at `0`, so single-element inputs return `0` instead of `1`, and a one-element run ending at the last index is missed entirely.

輸出 918 tok (+733 思考) 延遲 11.4 s

修復是否真的正確(可執行)、解釋的資訊密度,以及在一個邊界明確的任務上的 token 效率。

提示詞 Extract a JSON object with fields {company, quarter, revenue_usd_m, growth_pct, guidance} from this text. Use null for anything not stated; add no other fields. 檢查 合法 JSON,schema 精確

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

DeepSeek V4.1 Flash 通過 · 5/5 fields, guidance "withheld pending the Q4 close"

{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":11.0,"guidance":"withheld pending the Q4 close"}

輸出 1707 tok (+1667 思考) 延遲 15.1 s

schema 服從度(不臆造欄位)、幻覺壓力(guidance 明確被暫緩給出),以及結構化輸出路徑的差異。

提示詞 Write a 120-word product announcement for an API gateway feature that caches prompts across providers. Forbidden words: "seamless", "unlock", "game-changer", "revolutionize", "empower". Exactly one sentence must be a question. 檢查 120 詞,0 個禁用詞

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

DeepSeek V4.1 Flash 通過 · 116 words, 0 banned, 1 question

Today we're launching Cross-Provider Prompt Cache for our API gateway. It stores identical prompt requests and their responses across supported model providers, then serves cached results when a match is found. Teams can cut duplicate inference costs, reduce latency, and keep behavior consistent during provider failover. The cache works with configurable TTLs, per-route rules, and cache-key controls, so you decide what is reusable and what must stay fresh. Does your application send the same prompts to multiple providers? Now your gateway can answer many of those calls without another upstream request. Existing observability dashboards show hit rates, saved tokens, and estimated spend reduction. Enable it in the gateway console, set your policy, and start caching today.

輸出 917 tok (+770 思考) 延遲 9.0 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-pro-0813",
    # model="deepseek-v4.1-flash",  # 取消註解此行,並註解上一行
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

取得 API 金鑰 →

常見問題

DeepSeek V4 Pro (0813) 和 DeepSeek V4.1 Flash 哪個比較便宜?

DeepSeek V4.1 Flash 在 輸入 / 1m tokens 上較便宜($0.3 對比 $1.32,相差 4.4×)。其他項目可能呈現相反結果 — 上表提供完整資訊,實際成本取決於您的使用組合。

我可以在不進行兩次整合的情況下,對 DeepSeek V4 Pro (0813) 和 DeepSeek V4.1 Flash 進行 A/B 測試嗎?

可以。兩者皆透過同一個相容 OpenAI 的端點提供服務,並使用同一把 API 金鑰 — 切換只需更改一行的模型字串,因此您可以將部分流量分別導向兩者並直接比較帳單。

DeepSeek V4 Pro (0813) 與 DeepSeek V4.1 Flash 支援提示快取嗎?

是的 — 兩者的快取讀取費率皆低於其輸入費率,因此具有暖前綴的工作負載成本會低於牌價所示。確切的快取讀取列請見上方的定價表。

相關比較