Claude Sonnet 5.5 vs GPT-6.1 Sol

vs

什麼情況選哪一個

這兩款定價完全相同:每百萬輸入 token $2、每百萬輸出 $10、快取讀取每百萬 $0.1,最大輸出同為 128000,上下文視窗也幾乎一樣(claude-sonnet-5-5 為 1000000,gpt-6.1-sol 為 1050000),都接受文字與圖片輸入並回傳文字。差異很小:需要較晚的 2026-06 知識截止日期就選 claude-sonnet-5-5,需要稍大一點的視窗就選 gpt-6.1-sol。兩者都無法完全關閉思考。

Benchmark 成績

GPT-6.1 Sol:供應商沒有公布 benchmark 成績。

Claude Sonnet 5.5:公布了 10 項,但每一項都沒有夠多其他模型的成績,無法比較。

Claude Sonnet 5.5 GPT-6.1 Sol 其他有成績的模型 其他模型平均 ★ 沒有模型分數更高
SWE-sweep Hydrogen: Antigravity CLI 1.4.8. Peers: official leaderboard
3.1%
N/A
OSWorld 2.1 82 offline tasks, partial score. Hydrogen and Sonnet: best of 3. Terra: system card
83.9%
N/A
Agents’ Last Exam v1.1 Oct 17 task set. Hydrogen: Antigravity CLI. Sonnet: ALE-Claw. Terra: official leaderboard
60.4%
N/A
HLE-Diamond Artificial Analysis leaderboard, November report
53.3%
N/A
Vending-Bench 2 (USD) Andon Labs leaderboard, Hydrogen report · 9107-14549
11165
N/A
Chartography No tools. Hydrogen and Terra: Google evaluation. Sonnet: system card
61.6%
N/A

供應商公布: Google

定價

Claude Sonnet 5.5 GPT-6.1 Sol Δ
輸入 / 1M tokens $2 $2 =
輸出 / 1M tokens $10 $10 =
快取讀取 / 1M tokens $0.1 $0.1 =
快取寫入 1.25x (5m) / 2x (1h) 1.25x (30m) / 2.5x (12h) -

費率取自網站建置時的即時目錄;各模型頁面都列有最新的價目。 主表顯示基礎級距。提示詞長度可能改變整筆請求的費率,各模型頁有完整價目。

GPT-6.1 Sol · 依輸入長度分級的價格

整次請求依輸入長度所在級距計費。價格單位為美元/百萬 token。

輸入 token 數輸入輸出
0 - 272,000 $2 $10
272,001 - 1,050,000 $4 $15

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

功能

Claude Sonnet 5.5 GPT-6.1 Sol
工具使用 是 是
思考控制 一律開啟 一律開啟
結構化輸出 是 是
提示詞快取 顯式(由你標記前綴) 隱式 + 顯式
快取存活時間 5m default, 1h option at least 30m by default, 12h option on the Responses API
最小快取前綴 512 個 token 1,024 個 token

規格

Claude Sonnet 5.5 GPT-6.1 Sol
輸入模態 文字 圖像 文字 圖像
輸出模態 文字 文字
發布日期 2026-09-28 2026-09-29
知識截止日期 2026-06 2026-04
上下文視窗 1,000,000 1,050,000
最大輸出 128,000 128,000
思考參數 thinking.type reasoning.effort
可接受的值
thinking.type
  • adaptive (default)
  • between_tools
reasoning.effort
  • low
  • medium
  • high
  • xhigh
  • max
預設值 adaptive, effort high medium

規格摘錄自各供應商的文件;供應商沒有公布的項目就直接略過,不自行推測。 完整來源: Claude Sonnet 5.5 · GPT-6.1 Sol

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

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

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

GPT-6.1 Sol 通過 · 3 sentences

Enabling reasoning makes the model do more computational work before answering, and many providers bill the resulting reasoning tokens even though users never see them. That means the same number of requests can cost twice as much because each request consumes more billable tokens, even if the visible answers stay the same length. We should confirm the increase in our usage breakdown and reserve higher reasoning levels for tasks where the improvement justifies the added cost.

輸出 144 tok (+54 思考) 延遲 6.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.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

GPT-6.1 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 function counts equal adjacent pairs rather than items in a run: a run of length `n` has only `n - 1` equal pairs, so a single-element input returns `0`, and a run ending at the last index is also undercounted. It does process the last index, so the issue is not a missing final check. Initializing each nonempty run to `1` and updating `best` after every iteration correctly counts items, including singleton and trailing runs; empty inputs still return `0`.

輸出 189 tok 延遲 6.3 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/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

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

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

輸出 345 tok (+285 思考) 延遲 10.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 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

GPT-6.1 Sol 通過 · 120 words, 0 banned, 1 question

Introducing Cross-Provider Prompt Cache, a new API gateway feature that stores reusable prompts and manages caching across your supported AI providers. Why rebuild the same context every time your application switches models? With one configuration, teams can reuse shared instructions, standardize cache policies, and reduce repeated prompt processing wherever provider caching is available. The gateway handles provider-specific requirements while giving you clear visibility into cache hits, usage, and estimated savings. Set expiration windows, isolate cached content by project, and invalidate entries when prompts change. Your existing routing logic stays intact, so you can compare models without rebuilding your caching workflow. […]

輸出 588 tok (+435 思考) 延遲 13.9 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-5",
    # model="gpt-6.1-sol",  # 取消這一行的註解,並把上一行註解掉
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

取得 API 金鑰 →

常見問題

Claude Sonnet 5.5 和 GPT-6.1 Sol 哪個比較便宜?

主表顯示基礎級距。提示詞長度可能改變整筆請求的費率,各模型頁有完整價目。

可以只串接一次,就對 Claude Sonnet 5.5 和 GPT-6.1 Sol 做 A/B 測試嗎?

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

Claude Sonnet 5.5 與 GPT-6.1 Sol 支援提示詞快取嗎?

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

相關比較