GPT-6 Sol vs GPT-6.1 Sol

vs

什麼情況選哪一個

gpt-6.1-sol 是較新的 Sol 發行版(2026-09-29),OpenAI 將其定位為以較低成本處理複雜程式開發、電腦操作與專業工作;在帳面規格上,它與 gpt-6-sol 相當,具備 1050000-token 上下文、128000 最大輸出、文字與圖片輸入、2026-04 知識截止時間以及 $2 輸入 / $10 輸出的定價。有兩點不同:gpt-6.1-sol 的快取讀取成本為 $0.1,相對於 $0.2,且只有 gpt-6-sol 允許關閉思考功能。對於總是需要推理的快取密集型工作,請轉移至 gpt-6.1-sol;而在需要隨選提供非推理回覆的情況下,請繼續使用 gpt-6-sol。

Benchmark 成績

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

高於平均GPT-6 Sol僅 4 項可比
GPT-6 Sol GPT-6.1 Sol 其他有成績的模型 其他模型平均 ★ 沒有模型分數更高
DeepSWE 1.1
68.8%
N/A
OSWorld 2.0 offline set, partial
60.5%
N/A
Agents' Last Exam
56.4%
N/A

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

定價

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

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

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

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

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

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

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

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

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

GPT-6 Sol · $2 GPT-6.1 Sol · $2
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

功能

GPT-6 Sol GPT-6.1 Sol
工具使用 是 是
思考控制 可設定 一律開啟
結構化輸出 是 是
提示詞快取 隱式 + 顯式 隱式 + 顯式
快取存活時間 at least 30m by default, 12h option on the Responses API at least 30m by default, 12h option on the Responses API
最小快取前綴 1,024 個 token 1,024 個 token

規格

GPT-6 Sol GPT-6.1 Sol
輸入模態 文字 圖像 文字 圖像
輸出模態 文字 文字
發布日期 2026-09-22 2026-09-29
知識截止日期 2026-04 2026-04
上下文視窗 1,050,000 1,050,000
最大輸出 128,000 128,000
思考參數 reasoning.effort reasoning.effort
可接受的值
reasoning.effort
  • none
  • low
  • medium
  • high
  • xhigh
  • max
reasoning.effort
  • low
  • medium
  • high
  • xhigh
  • max
預設值 medium medium

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

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

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

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

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

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

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

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

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

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

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="gpt-6-sol",
    # model="gpt-6.1-sol",  # 取消這一行的註解,並把上一行註解掉
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

取得 API 金鑰 →

常見問題

GPT-6 Sol 和 GPT-6.1 Sol 哪個比較便宜?

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

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

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

GPT-6 Sol 與 GPT-6.1 Sol 支援提示詞快取嗎?

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

相關比較