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

Claude Fable 5.1 vs Claude Sonnet 5.5

Claude Fable 5.1 採邀請制提供服務。下方的數據為即時費率,但進行呼叫前需先取得工作區授權;在您基於此比較進行開發之前,請先向我們申請存取權限。

vs

何時用哪一個

這兩者在 Claude 系列中相差兩個等級:claude-fable-5-1 是最高等級,Anthropic 將其定位於高要求推理與長程代理工作,而 claude-sonnet-5-5 是較低等級,被標榜為速度較快,而 Fable 則較慢。兩者皆接受文字與影像輸入,並具備 1000000-token 上下文與 128000 最大輸出,因此價格突顯了兩者的差距:claude-fable-5-1 為輸入 $10 與輸出 $50,是輸入 $2 與輸出 $10 的 claude-sonnet-5-5 的 5x,且快取讀取為 $0.25 對比 $0.2。請將日常與大流量請求運行於 claude-sonnet-5-5,並在值得該成本的長程任務上升級至 claude-fable-5-1。

Benchmark 成績

Claude Sonnet 5.5:廠商沒有公布過 benchmark 成績。

高於同儕均值無人分數更高Claude Fable 5.119 / 213 / 21
Claude Fable 5.1 Claude Sonnet 5.5 其他被測模型 同儕均值 ★ 無人分數更高
DeepSWE 1.1
67.4%
N/A
OSWorld 2.0 partial
80.7%
N/A
HealthBench Professional
58.1%
N/A
Terminal-Bench-Science 0.1
52.6%
N/A
GPQA Diamond
93.7%
N/A
AutomationBench
31.4%
N/A
Chartography with tools
88.4%
N/A

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

定價

Claude Fable 5.1 Claude Sonnet 5.5 Δ
輸入 / 1M tokens $10 $2 5×
輸出 / 1M tokens $50 $10 5×
快取讀取 / 1M tokens $0.25 $0.2 1.3×
快取寫入 1.25x (5m) / 2x (1h) 1.25x (5m) / 2x (1h) -

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

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

能力

Claude Fable 5.1 Claude Sonnet 5.5
工具使用 是 是
思考控制 常駐開啟 常駐開啟
結構化輸出 是 是
提示快取 顯式(由您標記前綴) 顯式(由您標記前綴)
快取生命週期 5m default, 1h option 5m default, 1h option
最小快取前綴 1024 個 token 1024 個 token

規格

Claude Fable 5.1 Claude Sonnet 5.5
輸入模態 文字 影像 文字 影像
輸出模態 文字 文字
發布日期 2026-09-01 2026-09-28
知識截止日期 2026-06 2026-06
上下文視窗 1M 1M
最大輸出 128K 128K
思考參數 output_config.effort (thinking is adaptive-only and always on) thinking.type
可接受的值
effort
  • low
  • medium
  • high
  • xhigh
  • max
thinking.type
  • adaptive (default)
  • between_tools
預設值

thinking always on (adaptive)

effort
  • high
adaptive, effort high

規格摘錄自各供應商的文件;供應商未發布的資料列會直接省略,而非自行推測。 完整來源: Claude Fable 5.1 · Claude Sonnet 5.5

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

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

Claude Fable 5.1 通過 · 3 sentences

When we enabled reasoning, the model started generating a long chain of internal "thinking" tokens before producing each answer, and we're billed for those tokens at the same output rate even though users never see them. In practice, that hidden reasoning often runs several times longer than the visible response, so the total tokens per request roughly doubled while the number of requests stayed flat. The upside is measurably better accuracy on complex tasks, so the right conversation is whether that quality gain justifies the cost—and if not, we can restrict reasoning to the workflows that actually need it rather than turning it on globally.

輸出 186 tok 延遲 3.2 s

Claude Sonnet 5.5 通過 · 3 sentences

Enabling reasoning makes the model "think" before it answers, and that internal thinking is generated as extra text (reasoning tokens) that we are billed for at the same rate as output tokens, even though users never see it. Output tokens also cost several times more than input tokens, so a single request that used to produce a short answer can now generate many times more billable text behind the scenes. Because our request volume and prompts didn't change, the doubling comes almost entirely from this hidden thinking, and we can bring it down by limiting reasoning effort, turning it off for simple tasks, and reserving it for the workloads where the accuracy gain justifies the cost.

輸出 205 tok 延遲 3.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. 檢查 修復通過測試

Claude Fable 5.1 通過 · 8/8 cases

```python def longest_run(xs): if not xs: return 0 best = cur = 1 for i in range(1, len(xs)): cur = cur + 1 if xs[i] == xs[i - 1] else 1 best = max(best, cur) return best ``` The bug is that `cur` counts *matches between adjacent elements* rather than *elements in the run*: it starts at 0 and only increments when `xs[i] == xs[i-1]`, so a run of length k produces a count of k−1. That's why a single element returns 0 instead of 1, and why every other run also comes out one short — the "misses runs at the end" reports are the same off-by-one seen on inputs like `[1, 2, 2]`, where the trailing run of length 2 is reported as 1 (the original code does update `best` inside the loop, so end-of-list runs aren't actually skipped, just undercounted). […]

輸出 882 tok (+507 思考) 延遲 3.4 s

Claude Sonnet 5.5 通過 · 8/8 cases

**The bug:** `cur` counts the number of *adjacent equal pairs* rather than the number of items in the run. A run of length k contains only k−1 such pairs, so every result is one too small. The counter also starts at 0 and the loop starts at index 1, so a single-element list never updates `best` and returns 0 instead of 1. (An empty list should return 0.) In addition, `cur` resets to 0 on a mismatch, when it should reset to 1, because the item at `xs[i]` begins a new run of length 1. The claim that it "misses runs ending at the last index" is really the same off-by-one: the final run is counted, but as one less than its true length. Because `best` is updated inside the loop on every extension, the last run isn't skipped. […]

輸出 444 tok 延遲 6.7 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 Fable 5.1 通過 · 5/5 fields, guidance null

```json { "company": "Meridian Robotics", "quarter": "Q3 (September quarter)", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null } ``` Notes on judgment calls (not part of the object): - **revenue_usd_m**: The text says "412 for the topline" but never states the currency or that the figure is in millions; it's also on a constant-currency basis and prefaced with "call it," so it's approximate. If you want strict literalism, this should be `null`. - **growth_pct**: "Eleven and change" means slightly above 11%; the exact figure isn't given. - **quarter**: "September quarter" is Q3 on a calendar basis, consistent with the reference to a pending Q4 close. - **guidance**: Explicitly withheld, so `null`.

輸出 633 tok (+349 思考) 延遲 3.8 s

Claude Sonnet 5.5 通過 · 5/5 fields, guidance null

Here is the extracted JSON: ```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null } ``` Notes on the choices: - **quarter**: The text says "September quarter" without specifying a fiscal year or Q-number, so I kept the wording as stated. - **revenue_usd_m**: The text gives "412" for the topline, with no currency or unit stated explicitly. I've taken it as 412 million USD per the field definition, but the text does not confirm that, and the figure is constant-currency. - **growth_pct**: "Eleven and change" means slightly above 11, so 11 is an approximation. The exact figure isn't given. - **guidance**: Guidance is withheld pending the Q4 close, so no guidance is stated, hence null.

輸出 300 tok 延遲 3.5 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 Fable 5.1 通過 · 121 words, 0 banned, 1 question

**Introducing Cross-Provider Prompt Caching for the Gateway.** Starting today, your API gateway can cache prompts once and reuse them across OpenAI, Anthropic, Google, and any other provider you route to. Long system instructions, retrieval context, and few-shot examples are stored at the gateway layer, so switching models no longer means paying to resend the same tokens. Why send the same 8,000-token preamble to three different vendors when you could send it once? Our cache normalizes prompt segments, fingerprints them, and serves matching prefixes from memory before the request ever reaches an upstream API. Early customers report token costs falling by 30 to 60 percent on high-volume workloads, with median latency dropping alongside. Available today on all Team and Enterprise plans.

輸出 1722 tok (+1463 思考) 延遲 2.9 s

Claude Sonnet 5.5 通過 · 122 words, 0 banned, 1 question

**Introducing Cross-Provider Prompt Caching** Your API gateway now caches prompts across every connected LLM provider, whether you route traffic to OpenAI, Anthropic, Google, or a self-hosted model. Here's how it works: the gateway fingerprints each prompt prefix, stores it centrally, and applies the right provider-specific caching mechanism automatically. When you switch providers or fail over during an outage, your cached context follows you. Early testing shows input token costs dropping by up to 70% on repeated system prompts and long documents, with latency improvements of 40% or more on cache hits. Tired of paying to send the same instructions thousands of times a day? Enable it with one configuration flag. Cache rules, TTLs, and per-team isolation are available in the dashboard today.

輸出 266 tok 延遲 3.8 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-fable-5-1",
    # model="claude-sonnet-5-5",  # 取消註解此行,並註解上一行
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

取得 API 金鑰 →

常見問題

Claude Fable 5.1 和 Claude Sonnet 5.5 哪個比較便宜?

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

我可以在不進行兩次整合的情況下,對 Claude Fable 5.1 和 Claude Sonnet 5.5 進行 A/B 測試嗎?

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

Claude Fable 5.1 與 Claude Sonnet 5.5 支援提示快取嗎?

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

相關比較