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

Claude Haiku 5.5 vs DeepSeek V4 Pro (0813)

vs

什麼情況選哪一個

claude-haiku-5-5 輸入 $0.1、輸出 $0.5,對比 deepseek-v4-pro-0813 的 $1.32 與 $3.96,輸入便宜約 13 倍、輸出便宜 8 倍,快取讀取則是 $0.01 對比 $0.132。兩者的上下文視窗同為 1000000 個 token。claude-haiku-5-5 接受圖片輸入,提示詞超過 100000 個 token 後按 5 倍計費,即使如此仍然比較便宜;deepseek-v4-pro-0813 只接受文字,可輸出 393216 個 token,對比 128000。高用量與圖片相關的工作選 claude-haiku-5-5,需要超長文字輸出時選 deepseek-v4-pro-0813。

Benchmark 成績

Claude Haiku 5.5:供應商沒有公布 benchmark 成績。

高於平均沒有模型更高DeepSeek V4 Pro (0813)13 / 211 / 21
Claude Haiku 5.5 DeepSeek V4 Pro (0813) 其他有成績的模型 其他模型平均 ★ 沒有模型分數更高
DeepSWE 1.1
N/A
62.7%
Cybergym
N/A
83.3%
GDPval-AA v2 Elo · 1508-1769 據 Z.ai 公布 · 2026-09-04
N/A
1590
GPQA Diamond
N/A
92.4%
Agents' Last Exam
N/A
25.7%

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

定價

Claude Haiku 5.5 DeepSeek V4 Pro (0813) Δ
輸入 / 1M tokens $0.1 $1.32 0.076×
輸出 / 1M tokens $0.5 $3.96 0.13×
快取讀取 / 1M tokens $0.01 $0.132 0.076×
快取寫入 1.25x (5m) / 2x (1h) 不額外計費 -

費率取自網站建置時的即時目錄;各模型頁面都列有最新的價目。

兩者的相對位置:每 1M tokens 的輸入價格,涵蓋同一計費單位下全部 78 個聊天模型(對數尺度)

功能

Claude Haiku 5.5 DeepSeek V4 Pro (0813)
工具使用 是 是
思考控制 可設定 一律開啟
結構化輸出 是 是
提示詞快取 顯式(由你標記前綴) 隱式(自動)
快取存活時間 5m default, 1h option no fixed TTL (evicted when unused)
最小快取前綴 1024 個 token 未公布

規格

Claude Haiku 5.5 DeepSeek V4 Pro (0813)
輸入模態 文字 圖像 文字
輸出模態 文字 文字
發布日期 2026-10-07 2026-08-13
知識截止日期 2026-06 -
上下文視窗 1M 1M
最大輸出 128K 393K
思考參數 output_config.effort reasoning_effort
可接受的值
output_config.effort
  • low
  • medium
  • high
  • xhigh
  • max
reasoning_effort
  • the model card documents low
  • high
  • max
預設值 medium -

規格摘錄自各供應商的文件;供應商沒有公布的項目就直接略過,不自行推測。 完整來源: Claude Haiku 5.5 · DeepSeek V4 Pro (0813)

同一段提示詞,兩個模型,經閘道實測

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

Claude Haiku 5.5 通過 · 3 sentences

Enabling reasoning makes the model generate a long internal chain of thought before its answer, and those thinking tokens are billed as output tokens, which cost several times more than input tokens. The model often produces many times more output per request than it did without reasoning, so the per-call cost rises even when the visible answer looks about the same length. Because that extra spend scales with every request, the bill roughly doubled, and we can control it by setting reasoning budgets, using reasoning only for tasks that need it, or routing simpler requests to a non-reasoning model.

輸出 332 tok (+159 思考) 延遲 2.9 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 計量顯示出的隱藏思考計費落差。

提示詞 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. 檢查 修正後通過測試

Claude Haiku 5.5 通過 · 8/8 cases

```python def longest_run(xs): if not xs: return 0 best = 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` counts adjacent equal *pairs*, not run *elements*. A run of k equal items produces k−1 matching pairs, so the function returns one less than the true length, and a single-element input produces no pairs at all, so it returns 0 instead of 1. Resetting `cur` to 0 on a mismatch compounds this by starting every run one step behind. The fix starts both `cur` and `best` at 1 (a non-empty list always has a run of at least one element), resets `cur` to 1 on a mismatch, and updates `best` after every element rather than only inside the equal-branch. The empty-list guard keeps the function from returning 1 for `[]`. […]

輸出 1012 tok (+591 思考) 延遲 6.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 效率。

提示詞 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

Claude Haiku 5.5 通過 · 5/5 fields, guidance "Formal guidance withheld pending the Q4 "

```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": null, "growth_pct": 11, "guidance": "Formal guidance withheld pending the Q4 close" } ``` Notes: The text gives revenue as 412 but doesn't state the currency, so I left `revenue_usd_m` as null. Growth is "eleven and change," so 11 is an approximation.

輸出 725 tok (+572 思考) 延遲 4.6 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),以及結構化輸出路徑的差異。

提示詞 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 個禁用詞

Claude Haiku 5.5 通過 · 120 words, 0 banned, 1 question

**Introducing Prompt Cache Sync, the newest feature in GatewayOne.** Teams routing requests across OpenAI, Anthropic, and Google have often paid to process the same long system prompts again and again. Now the gateway stores those prompts once and reuses them wherever they appear, regardless of provider. Repeated context is matched by content hash, so cached prefixes return faster and cost less, with no changes to your application code. How much could this save your team? Enable Prompt Cache Sync from the dashboard, and your next billing report will show the difference. Cache entries follow your existing retention settings and can be purged per project at any time. Availability begins this week for all Scale and Enterprise plans worldwide. Start today.

輸出 2164 tok (+1929 思考) 延遲 9.9 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="claude-haiku-5-5",
    # model="deepseek-v4-pro-0813",  # 取消這一行的註解,並把上一行註解掉
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

取得 API 金鑰 →

常見問題

Claude Haiku 5.5 和 DeepSeek V4 Pro (0813) 哪個比較便宜?

以「輸入 / 1M tokens」來看,Claude Haiku 5.5 比較便宜($0.1 對 $1.32,相差 13×)。其他項目的結果可能相反,完整價目請看上表;實際成本要看你的用量組合。

可以只串接一次,就對 Claude Haiku 5.5 和 DeepSeek V4 Pro (0813) 做 A/B 測試嗎?

可以。兩個模型都走同一個 OpenAI 相容端點,用的也是同一把 API 金鑰,切換時只要改一行裡的模型名稱字串。你可以把一部分流量分別導到兩邊,再直接比較帳單。

Claude Haiku 5.5 與 DeepSeek V4 Pro (0813) 支援提示詞快取嗎?

支援。兩者的快取讀取費率都低於輸入費率,所以前綴已經進快取的工作負載,實際成本會比官網價算出來的低。確切的快取讀取價格請見上方定價表。

相關比較