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

Claude Sonnet 5 vs Claude Sonnet 5.5

vs

何时用哪一个

claude-sonnet-5 和 claude-sonnet-5-5 定价相同,均为每百万输入 token $2、每百万输出 token $10 以及缓存读取 $0.2,且均具有 1000000-token 上下文、128000 最大输出、文本加图像输入,以及相同的 chat、code、thinking、tools 和 reasoning 标志。真正的区别在于生成与控制:claude-sonnet-5-5 是较新的版本(2026-09-28,知识截止日期 2026-06),而 claude-sonnet-5(2026-06-30,截止日期 2026-01)允许你关闭 thinking。当你需要非 thinking 响应时,请选择 claude-sonnet-5,否则请选择 claude-sonnet-5-5 以在无额外费用的情况下获得更晚的截止日期。

Benchmark 成绩

Claude Sonnet 5.5:厂商没有公布过 benchmark 成绩。

高于同侪均值无人分数更高Claude Sonnet 54 / 221 / 22
Claude Sonnet 5 Claude Sonnet 5.5 其他被测模型 同侪均值 ★ 无人分数更高
DeepSWE 1.1
53.8%
N/A
BioMysteryBench hard
34.1%
N/A
OSWorld 2.0 Partial score, batch tool enabled
42.6%
N/A
Finance Agent v2
53.9%
N/A
Harvey Lab-AA
90.1%
N/A
HLE-Verified
31%
N/A
AutomationBench
10.7%
N/A
LVBench
68.5%
N/A

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

定价

Claude Sonnet 5 Claude Sonnet 5.5 Δ
输入 / 1M tokens $2 $2 =
输出 / 1M tokens $10 $10 =
缓存读取 / 1M tokens $0.2 $0.2 =
缓存写入 1.25x (5m) / 2x (1h) 1.25x (5m) / 2x (1h) -

费率取自构建时的实时目录;每个模型页面均附有当前的费率卡。

它们的位置 — 以该计费单位计费的所有 76 个 聊天 模型的 每 1M token 的输入价格(对数刻度)

能力

Claude Sonnet 5 Claude Sonnet 5.5
工具使用 是 是
思考控制 可配置 始终开启
结构化输出 是 是
提示词缓存 显式(由您标记前缀) 显式(由您标记前缀)
缓存生存时间 5m default, 1h option 5m default, 1h option
最小缓存前缀 1024 个 token 1024 个 token

规格

Claude Sonnet 5 Claude Sonnet 5.5
输入模态 文本 图像 文本 图像
输出模态 文本 文本
发布日期 2026-06-30 2026-09-28
知识截止日期 2026-01 2026-06
上下文窗口 1M 1M
最大输出 128K 128K
思考参数
  • thinking.type "adaptive"
  • output_config.effort
thinking.type
允许的值
thinking.type
  • adaptive
  • disabled
effort
  • low
  • medium
  • high
  • xhigh
  • max

"enabled" returns 400

thinking.type
  • adaptive (default)
  • between_tools
默认值

thinking on (adaptive)

effort
  • high
adaptive, effort high

规格转录自各供应商的文档;若供应商未发布某项数据,则直接省略该行,而非进行推断。 完整来源: Claude Sonnet 5 · Claude Sonnet 5.5

单个 Prompt,两个模型 —— 通过网关实测

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

Claude Sonnet 5 通过 · 3 sentences

Reasoning mode works by having the model generate extended internal "thinking" steps before producing its final answer, and since we're billed on total tokens, that hidden reasoning text adds significantly to what we pay for—even though you never see it in the output. This is different from simply getting longer visible responses; the model is essentially "showing its work" behind the scenes, and complex prompts can trigger thousands of extra reasoning tokens per request. The upside is improved accuracy on complex tasks, but if we want to control costs, we should selectively enable reasoning only for queries that truly need it, rather than applying it universally.

输出 194 tok 延迟 4.3 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 Sonnet 5 通过 · 8/8 cases

## The Bug The function has two related off-by-one issues rooted in the same cause: `cur` and `best` are initialized to `0` instead of `1`, treating run lengths as the number of *matches* between adjacent elements rather than the number of *elements* in the run. This means a single-element input never enters the loop (since `range(1, 1)` is empty) and returns `0` instead of the correct answer of `1`. It also means that for any input, the run length is undercounted by exactly one — a run of 3 equal elements only produces 2 "match" increments, so `best` ends up as 2 instead of 3. The claim that it "misses runs that end at the last index" is actually a symptom of this same undercount: the logic does update `best` correctly on every iteration (including the last), but because it's counting matches instead of elements, the final reported value is always one less than the true longest run. […]

输出 536 tok 延迟 7.1 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 Sonnet 5 通过 · 5/5 fields, guidance null

```json { "company": "Meridian Robotics", "quarter": "Q3", "revenue_usd_m": 412, "growth_pct": 11.5, "guidance": null } ```

输出 348 tok 延迟 5.3 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 Sonnet 5 通过 · 123 words, 0 banned, 1 question

## Introducing Cross-Provider Prompt Caching We're rolling out a new caching layer for our API gateway that works across every major LLM provider you connect through it. Instead of resending identical prompts and paying full price each time, the gateway recognizes repeated requests and serves cached responses in milliseconds—regardless of whether you're routing to OpenAI, Anthropic, or Google. What does this mean for your bill and your latency? Both drop, often significantly, especially for teams running high-volume, repetitive workloads like customer support bots or batch content generation. The cache is configurable per route, with adjustable TTLs and invalidation rules, so you stay in control of freshness versus cost. Available now for all Pro and Enterprise plans. Check your dashboard to enable it today.

输出 259 tok 延迟 4.8 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-sonnet-5",
    # model="claude-sonnet-5-5",  # 取消注释此行,注释上一行
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

获取 API 密钥 →

常见问题

Claude Sonnet 5 和 Claude Sonnet 5.5 哪个更便宜?

它们列出的 输入 / 1m tokens 相同($2),因此价格不是这一项的决定因素——请参考下文的规格与能力。

我可以在不进行两次集成的情况下,对 Claude Sonnet 5 和 Claude Sonnet 5.5 进行 A/B 测试吗?

可以。两者均通过同一个兼容 OpenAI 的端点提供服务,并使用同一把 API 密钥——切换只需更改一行模型字符串,因此你可以将一部分流量路由到各个模型并直接比较账单。

Claude Sonnet 5 和 Claude Sonnet 5.5 支持提示词缓存吗?

是的 —— 两者对缓存读取的计费均低于其输入费率,因此热前缀工作负载的成本低于标价。准确的缓存读取行位于上方的定价表中。

相关对比

来自我们的实测研究