Gemini 4 Carbon vs Tencent Hy4

vs

什麼情況選哪一個

基礎檔每百萬輸出 token 的價格為 $10 和 $2.501(gemini-4-carbon 對 hy4)。 需直接輸入音訊或影片時選 gemini-4-carbon,並將已公布的調價納入預算。 與 gemini-4-carbon 相比,中英文長文件夾有截圖時,可評估 hy4。

Benchmark 成績

Tencent Hy4:供應商沒有公布 benchmark 成績。

高於平均沒有模型更高Gemini 4 Carbon12 / 1210 / 12
Gemini 4 Carbon Tencent Hy4 其他有成績的模型 其他模型平均 ★ 沒有模型分數更高
FrontierSWE 2 Proximal leaderboard, Carbon report
61.2%
N/A
OSWorld 2.1 82 offline tasks, partial score. Gemini: best of 3. Peers: published evaluations
81.5%
N/A
AutomationBench (Zapier) Zapier private set
沒有模型分數更高 53.9%
N/A
GraphWalks BFS (F1) 256k to 1M tokens, 200 tasks, Google evaluation
沒有模型分數更高 96.2%
N/A
Blueprint-Bench 2 Similarity score, Andon Labs leaderboard
沒有模型分數更高 58.6%
N/A
Vending-Bench 2 (USD) Andon Labs leaderboard, Carbon report · 5422-16484
沒有模型分數更高 16484
N/A
Chartography No tools, Carbon report
沒有模型分數更高 72.5%
N/A

供應商公布: Google

定價

Gemini 4 Carbon Tencent Hy4 Δ
輸入 / 1M tokens $2 $0.834 2.4×
輸出 / 1M tokens $10 $2.501 4×
快取讀取 / 1M tokens $0.1 $0.042 2.4×

費率取自網站建置時的即時目錄;各模型頁面都列有最新的價目。

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

Gemini 4 Carbon · $2 Tencent Hy4 · $0.834
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

功能

Gemini 4 Carbon Tencent Hy4
工具使用 是 是
思考控制 一律開啟 是,但供應商未公布調整參數
結構化輸出 是 -
提示詞快取 隱式(自動) 隱式(自動)
快取存活時間 未公布 未公布
最小快取前綴 4,096 個 token 未公布

規格

Gemini 4 Carbon Tencent Hy4
輸入模態 文字 圖像 音訊 影片 文字 圖像
輸出模態 文字 文字
發布日期 2026-11-10 2026-11-04
知識截止日期 2026-03 -
上下文視窗 1,048,576 1,048,576
最大輸出 65,536 65,536
思考參數 thinking_level -
可接受的值
thinking_level
  • low
  • medium
  • high

"minimal" and thinking_budget return 400

-
預設值 medium -

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

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

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

Gemini 4 Carbon 通過 · 3 sentences

Enabling reasoning instructs the AI to generate a lengthy, behind-the-scenes "thought process" to verify its logic before delivering a final answer. Because our vendor bills us based on total output volume, we are charged for all of that invisible scratchpad work in addition to the visible response, effectively doubling the compute consumed per query. Moving forward, we can control this cost by restricting reasoning strictly to complex, high-stakes workflows where higher accuracy justifies the premium, while routing routine tasks back to standard, lower-cost models.

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

Gemini 4 Carbon 通過 · 8/8 cases

```python def longest_run(xs): if not xs: return 0 best = 1 cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 best = max(best, cur) else: cur = 1 return best ``` The original function counts the number of matching adjacent *transitions* rather than the number of *elements* in a run because `best` and `cur` are initialized and reset to `0` instead of `1`. Because a single item on its own already forms a run of length `1`, starting at `0` causes every non-empty result to be short by one: single-element lists (where the loop never executes) and lists with no duplicates return `0` instead of `1`, and any run of $k$ equal items—including one ending at the last index—only increments `cur` $k - 1$ times, making it appear as though the final element of the run was missed. […]

輸出 1411 tok (+1131 思考) 延遲 32.7 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

Gemini 4 Carbon 通過 · 5/5 fields, guidance null

```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": null, "growth_pct": null, "guidance": null } ```

輸出 3338 tok (+3281 思考) 延遲 61.6 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 個禁用詞

Gemini 4 Carbon 通過 · 120 words, 0 banned, 1 question

Are your engineering teams paying multiple AI vendors to generate identical responses? Today, we are introducing Universal Prompt Caching for our flagship API Gateway. When applications route traffic across providers like OpenAI, Anthropic, and Mistral, duplicate queries drain budgets and degrade user experiences. Our new unified caching layer intercepts incoming prompts directly at the network edge. If an identical request was previously fulfilled by any connected model, the gateway delivers the stored response in milliseconds, completely bypassing external API calls. This practical upgrade cuts monthly token expenses substantially while accelerating overall application speed. Best of all, deployment requires zero complex code changes. Simply activate this capability inside your gateway configuration dashboard today to start reducing latency and infrastructure costs immediately.

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

取得 API 金鑰 →

常見問題

Gemini 4 Carbon 和 Tencent Hy4 哪個比較便宜?

以「輸入 / 1M tokens」來看,Tencent Hy4 比較便宜($0.834 對 $2,相差 2.4×)。其他項目的結果可能相反,完整價目請看上表;實際成本要看你的用量組合。

可以只串接一次,就對 Gemini 4 Carbon 和 Tencent Hy4 做 A/B 測試嗎?

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

Gemini 4 Carbon 與 Tencent Hy4 支援提示詞快取嗎?

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

相關比較