GPT-6.1 Sol vs Tencent Hy4

vs

什麼情況選哪一個

提示詞不超過 272000 個輸入 token 時,每百萬輸出 token 為 $10 和 $2.501(gpt-6.1-sol 對 hy4)。 應用需要明確控制推理強度時,可評估 gpt-6.1-sol。 與 gpt-6.1-sol 相比,中英文長文件夾有截圖時,可評估 hy4。

定價

GPT-6.1 Sol Tencent Hy4 Δ
輸入 / 1M tokens $2 $0.834 2.4×
輸出 / 1M tokens $10 $2.501 4×
快取讀取 / 1M tokens $0.1 $0.042 2.4×
快取寫入 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 個聊天模型(對數尺度)

GPT-6.1 Sol · $2 Tencent Hy4 · $0.834
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

功能

GPT-6.1 Sol Tencent Hy4
工具使用 是 是
思考控制 一律開啟 是,但供應商未公布調整參數
結構化輸出 是 -
提示詞快取 隱式 + 顯式 隱式(自動)
快取存活時間 at least 30m by default, 12h option on the Responses API 未公布
最小快取前綴 1,024 個 token 未公布

規格

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

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

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

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

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

Tencent Hy4 通過 · 3 sentences

Enabling reasoning changed the unit economics of each request: the model now produces extra “reasoning tokens” and consumes more compute before it returns an answer, and those tokens are billed even if users never see them. Because our pricing is largely token-based, that extra work roughly doubled average cost per call, so flat request volume could still produce a doubled invoice. We are paying for better accuracy and less downstream rework on complex tasks, so the spend is justified only in high-value workflows and should be managed by cost per successful outcome.

輸出 1519 tok (+1409 思考) 延遲 21.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. 檢查 修正後通過測試

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

Tencent Hy4 通過 · 8/8 cases

```python def longest_run(xs): n = len(xs) if n == 0: return 0 best = cur = 1 for i in range(1, n): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 best = max(best, cur) return best ``` The loop range already includes the last index; the real bug is that `cur` and `best` start at `0` and only increase on equal adjacent comparisons, so the function counts equality links (`L - 1` for a run of `L` equal items), not the items in the run: a single item has no link, and the first item of a final run is never counted, with no end-of-list flush to compensate. […]

輸出 4509 tok (+4263 思考) 延遲 56.0 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.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

Tencent Hy4 通過 · 5/5 fields, guidance "withheld pending the Q4 close"

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

輸出 9869 tok (+9827 思考) 延遲 125.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.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

Tencent Hy4 通過 · 120 words, 0 banned, 1 question

Today we are introducing Cross Provider Prompt Cache for our API gateway, a feature that caches prompts and securely reuses them across all connected model providers. Teams can cut duplicate calls, reduce latency, and keep spend predictable when identical instructions appear in chat, search, agents, or batch jobs. What if one cached prompt could support traffic routed to any provider in your stack? Gateway policies control cache keys, time to live, tenant isolation, redaction, and fallback behavior, while usage metrics show hit rates and savings by application. Setup requires one configuration change, and existing client code stays intact. Cross Provider Prompt Cache is available in private beta today for enterprise plans, with general availability next month across all supported regions.

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

取得 API 金鑰 →

常見問題

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

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

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

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

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

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

相關比較