Gemini 4 Hydrogen vs Kimi K3.1 Pro Highspeed

vs

什麼情況選哪一個

程式設計流程需要直接輸入音訊或影片與截圖時,選 gemini-4-hydrogen。 輸入為 100000 token 時,每百萬輸入/輸出 token 的費率為 gemini-4-hydrogen $1.5/$7.5,kimi-k3.1-pro-highspeed $4/$20。

Benchmark 成績

Kimi K3.1 Pro Highspeed:供應商沒有公布 benchmark 成績。

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

Gemini 4 Hydrogen Kimi K3.1 Pro Highspeed 其他有成績的模型 其他模型平均 ★ 沒有模型分數更高
SWE-sweep Hydrogen: Antigravity CLI 1.4.8. Peers: official leaderboard
13.5%
N/A
OSWorld 2.1 82 offline tasks, partial score. Hydrogen and Sonnet: best of 3. Terra: system card
77.6%
N/A
Agents’ Last Exam v1.1 Oct 17 task set. Hydrogen: Antigravity CLI. Sonnet: ALE-Claw. Terra: official leaderboard
71.6%
N/A
HLE-Diamond Artificial Analysis leaderboard, November report
58.8%
N/A
Vending-Bench 2 (USD) Andon Labs leaderboard, Hydrogen report · 9107-14549
14549
N/A
Chartography No tools. Hydrogen and Terra: Google evaluation. Sonnet: system card
66.6%
N/A

供應商公布: Google

定價

Gemini 4 Hydrogen Kimi K3.1 Pro Highspeed Δ
輸入 / 1M tokens $1.5 $4 0.38×
輸出 / 1M tokens $7.5 $20 0.38×
快取讀取 / 1M tokens $0.075 $0.2 0.37×

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

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

功能

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

規格

Gemini 4 Hydrogen Kimi K3.1 Pro Highspeed
輸入模態 文字 圖像 音訊 影片 文字 圖像
輸出模態 文字 文字
發布日期 2026-11-12 2026-10-23
知識截止日期 2026-03 -
上下文視窗 1,048,576 1,048,576
最大輸出 65,536 131,072
思考參數 thinking_level -
可接受的值
thinking_level
  • low
  • medium
  • high
  • xhigh

"minimal" and thinking_budget return 400

-
預設值 high -

規格摘錄自各供應商的文件;供應商沒有公布的項目就直接略過,不自行推測。 完整來源: Gemini 4 Hydrogen · Kimi K3.1 Pro Highspeed

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

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

Gemini 4 Hydrogen 通過 · 3 sentences

When reasoning is enabled, the AI generates extensive hidden "thinking" tokens to verify its logic step-by-step before delivering a final answer. Because vendors bill us for every token produced—meaning we pay full output-token rates for this invisible internal work—our billable consumption doubled even though the user-facing responses stayed the same length. To protect our margins, we should restrict reasoning mode strictly to complex, high-value tasks and route routine queries back to standard models.

輸出 1236 tok (+1136 思考) 延遲 9.0 s

Kimi K3.1 Pro Highspeed 通過 · 3 sentences

Enabling reasoning makes the model generate extra “thinking” tokens before each answer, so every request consumes more compute and output tokens even when the visible response stays short. Those reasoning tokens are typically billed, and the new configuration may also use a more expensive model or processing tier, raising both usage and unit cost. To control spend, we should verify reasoning-token volume and model pricing on the invoice, then cap reasoning effort and reserve it for high-value tasks.

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

Gemini 4 Hydrogen 通過 · 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 bug is that `best` and `cur` were initialized (and `cur` was reset) to `0` instead of `1`, causing the loop to count matching adjacent transitions rather than the number of elements in a run. As a result, any non-empty input was off by one—returning `0` on single-element lists where the loop doesn't execute at all, and undercounting every run (including runs ending at the last index) by 1. Returning `0` early for empty inputs and starting/resetting the run length at `1` ensures each element is counted accurately while still updating `best` on the final iteration when a run ends at the last index.

輸出 1489 tok (+1247 思考) 延遲 10.8 s

Kimi K3.1 Pro Highspeed 通過 · 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 else: cur = 1 best = max(best, cur) return best ``` The bug is counter bookkeeping, not the loop bounds: `cur` starts at zero, so the original counts equal adjacent pairs rather than items and never records a run for a single-element input. Runs are therefore reported one short, with singleton runs appearing as zero, including runs reaching the last index. The fix treats each item as a run of length one, resets `cur` to one on a mismatch, and updates `best` after every step, so a trailing run is recorded without needing a following mismatch; empty input returns `0`.

輸出 2102 tok (+2079 思考) 延遲 31.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

Gemini 4 Hydrogen 通過 · 5/5 fields, guidance "withheld pending the Q4 close"

```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": null, "growth_pct": null, "guidance": "withheld pending the Q4 close" } ```

輸出 3165 tok (+3100 思考) 延遲 21.2 s

Kimi K3.1 Pro Highspeed 通過 · 5/5 fields, guidance "Formal guidance withheld pending the Q4 "

{ "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": "Formal guidance withheld pending the Q4 close" }

輸出 2170 tok (+2170 思考) 延遲 29.3 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 Hydrogen 通過 · 120 words, 0 banned, 1 question

Introducing unified prompt caching, the newest capability in our enterprise API gateway. Are you tired of paying repeatedly for identical prompts sent across different AI providers? Our gateway now caches prompts across major AI providers within a unified, shared memory layer. When an application submits a matching query, the gateway intercepts the request and returns the saved output in milliseconds, completely bypassing external inference fees. Engineering teams gain predictable latency and substantial cost reductions without modifying any existing application code. Managing cache policies at the infrastructure edge helps your organization prevent provider dependency while maintaining strict data privacy standards. Enable unified prompt caching in your dashboard today to build faster, more economical artificial intelligence applications across your entire technology stack.

輸出 3710 tok (+3574 思考) 延遲 24.1 s

Kimi K3.1 Pro Highspeed 通過 · 120 words, 0 banned, 1 question

Introducing Cross-Provider Prompt Cache, a new API gateway feature that stores prompt responses and serves them across model providers. By reusing responses, teams can reduce latency, cut duplicate inference costs, and keep applications responsive during traffic spikes. You choose cache lifetime, scope, and eligibility rules, while provider credentials and routing policies remain under your control. Built-in metrics show hit rates, savings, and response times, helping you tune performance with confidence. Sensitive workloads can bypass caching, and entries expire according to your retention settings. Ready to spend less on repeated prompts? Enable the feature from your gateway configuration, define a cache policy, and start measuring results today. Cross-Provider Prompt Cache is available now, with documentation and examples in the developer console.

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

取得 API 金鑰 →

常見問題

Gemini 4 Hydrogen 和 Kimi K3.1 Pro Highspeed 哪個比較便宜?

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

可以只串接一次,就對 Gemini 4 Hydrogen 和 Kimi K3.1 Pro Highspeed 做 A/B 測試嗎?

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

Gemini 4 Hydrogen 與 Kimi K3.1 Pro Highspeed 支援提示詞快取嗎?

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

相關比較