新人 免费注册,送 10 次调用,最高 $1,无需绑卡。

Claude Fable 5.1 vs GPT-6 Sol

Claude Fable 5.1 目前为邀请制。下方是它的实时价格,但调用前需要先为你的工作空间开通权限;打算根据这份对比做开发的话,请先向我们申请。

vs

什么时候选哪个

两者均接受文本和图像输入,返回文本,将输出限制为 128000 token,并提供约一百万 token 的上下文(claude-fable-5-1 为 1000000,gpt-6-sol 为 1050000),因此真正的区别在于价格和对推理的控制。gpt-6-sol 的输入成本为每百万 $2,输出为每百万 $10,在这两项上比 $10 和 $50 的 claude-fable-5-1 便宜 5x,且其思考模式可以在廉价的短轮次中关闭。当你希望其始终开启的思考应用于每个请求并接受溢价时,请选择 claude-fable-5-1;否则 gpt-6-sol 能以更低廉的价格覆盖相同的模态。

Benchmark 成绩

高于同类均值无更高分Claude Fable 5.119 / 213 / 21GPT-6 Sol仅 4 项可比
Claude Fable 5.1 GPT-6 Sol 其他参测模型 同类均值 ★ 没有模型得分更高
DeepSWE 1.1
67.4%
68.8%
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
Agents' Last Exam
N/A
56.4%
Chartography with tools
88.4%
N/A

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

价格

Claude Fable 5.1 GPT-6 Sol Δ
输入 / 1M token $10 $2 5×
输出 / 1M token $50 $10 5×
缓存读取 / 1M token $0.25 $0.2 1.3×
缓存写入 1.25x (5m) / 2x (1h) 不单独收费 -

价格取自构建时的实时目录,最新价格见各模型页面。

两个模型所处的位置:全部 77 个按同一单位计费的聊天模型的每 1M token 输入价分布(对数刻度)

$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

能力

Claude Fable 5.1 GPT-6 Sol
工具调用 是 是
思考控制 始终开启 可配置
结构化输出 是 是
提示词缓存 显式(由你标记前缀) 隐式(自动)
缓存有效期 5m default, 1h option 5-10m, up to 1h
最小缓存前缀 1024 个 token 1024 个 token

规格

Claude Fable 5.1 GPT-6 Sol
输入模态 文本 图像 文本 图像
输出模态 文本 文本
发布日期 2026-09-01 2026-09-22
知识截止日期 2026-06 2026-04
上下文窗口 1M 1.1M
最大输出 128K 128K
思考参数 output_config.effort (thinking is adaptive-only and always on) reasoning.effort
可选值
effort
  • low
  • medium
  • high
  • xhigh
  • max
reasoning.effort
  • none
  • low
  • medium
  • high
  • xhigh
  • max
默认值

thinking always on (adaptive)

effort
  • high
medium

规格照录自各供应商的文档;供应商没有公布的项目,对应的行直接省略,不做推断。 完整来源: Claude Fable 5.1 · GPT-6 Sol

同一条提示词,两个模型,经网关实测

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

GPT-6 Sol 通过 · 3 sentences

Enabling reasoning made the model generate extra internal tokens to work through each request, and those tokens are billed even though users don’t see them. If request volume stayed roughly the same, more billed tokens per request could explain why the bill doubled. We should check the usage breakdown to confirm, then lower reasoning effort or limit it to tasks that need it.

输出 188 tok (+111 思考) 延迟 5.0 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

GPT-6 Sol 通过 · 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 original `cur` counted matching *adjacent pairs*, not items, so every run was one too short—including a single-element input, which returned 0. Starting each run at 1 counts its first item, and updating `best` on every iteration ensures a run that reaches the last index is included.

输出 206 tok (+59 思考) 延迟 5.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 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

GPT-6 Sol 通过 · 5/5 fields, guidance "Withheld pending the Q4 close"

{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":null,"growth_pct":null,"guidance":"Withheld pending the Q4 close"}

输出 227 tok (+185 思考) 延迟 5.2 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

GPT-6 Sol 通过 · 120 words, 0 banned, 1 question

Today, we’re introducing cross-provider prompt caching for our API gateway, helping teams reuse repeated prompt content when routing requests among supported AI providers. The gateway identifies eligible prompt prefixes, stores cache references, and applies them to subsequent requests where provider capabilities allow. Why send the same context again if it can be reused? With fewer duplicate input tokens, applications can reduce costs and improve latency without changing how developers call the gateway. Configure caching by route, monitor hit rates and savings in your dashboard, and keep existing provider fallback rules in place. Availability and cache behavior vary by provider, so the gateway reports eligibility and usage for each request. Get started today with our documentation and test your existing workloads.

输出 586 tok (+443 思考) 延迟 7.7 s

是否守住约束(字数预算、禁用词表、只能有一个问句)、文风特征,以及长度控制。

改一行代码就能在两个模型之间切换

下方每个标签页里都有两个模型 ID,高亮的那两行是唯一要改的地方。端点不变,API key 不变,请求结构也不变。

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="gpt-6-sol",  # 取消注释此行,注释上一行
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

获取 API key →

常见问题

Claude Fable 5.1 和 GPT-6 Sol 哪个更便宜?

按「输入 / 1M token」算,GPT-6 Sol 更便宜($2 对 $10,相差 5.0×)。其他计费项的结论可能相反,完整价格见上方表格,实际成本取决于你的用量构成。

不用分别集成两次,就能对 Claude Fable 5.1 和 GPT-6 Sol 做 A/B 测试吗?

可以。两个模型走同一个 OpenAI 兼容端点,用同一个 API key,切换时只要改一行里的模型名,所以可以给两个模型各分一部分流量,直接对比账单。

Claude Fable 5.1 和 GPT-6 Sol 支持提示词缓存吗?

支持。两个模型的缓存读取价都低于各自的输入价,所以前缀能反复命中缓存的负载,实际成本会比按官网价估算的低。具体的缓存读取价见上方价格表。

相关对比

我们的实测研究