Gemini 4 Hydrogen vs Kimi K3.1 Pro

vs

什么时候选哪个

编程流程需要把音频或视频连同截图直接作为输入时,选 gemini-4-hydrogen。 输入为 100000 token 时,每百万输入/输出 token 的费率为 gemini-4-hydrogen $1.5/$7.5,kimi-k3.1-pro $2/$10。

Benchmark 成绩

Kimi K3.1 Pro:供应商没有公布 benchmark 成绩。

Gemini 4 Hydrogen:公布了 10 项成绩,但每一项测过的其他模型都太少,没法比较。

Gemini 4 Hydrogen Kimi K3.1 Pro 其他参测模型 同类均值 ★ 没有模型得分更高
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 Δ
输入 / 1M token $1.5 $2 0.75×
输出 / 1M token $7.5 $10 0.75×
缓存读取 / 1M token $0.075 $0.2 0.37×

价格取自构建时的实时目录,最新价格见各模型页面。

两个模型所处的位置:全部 86 个按同一单位计费的聊天模型的每 1M token 输入价分布(对数刻度)

能力

Gemini 4 Hydrogen Kimi K3.1 Pro
工具调用 是 是
思考控制 始终开启 是,但供应商未公布调节参数
结构化输出 是 是
提示词缓存 隐式(自动) 隐式(自动)
缓存有效期 未公布 未公布
最小缓存前缀 4,096 个 token 未公布

规格

Gemini 4 Hydrogen Kimi K3.1 Pro
输入模态 文本 图像 音频 视频 文本 图像
输出模态 文本 文本
发布日期 2026-11-12 2026-10-23
知识截止日期 2026-03 -
上下文窗口 1,048,576 1,048,576
最大输出 65,536 1,048,576
思考参数 thinking_level -
可选值
thinking_level
  • low
  • medium
  • high
  • xhigh

"minimal" and thinking_budget return 400

-
默认值 high -

规格照录自各供应商的文档;供应商没有公布的项目,对应的行直接省略,不做推断。 完整来源: Gemini 4 Hydrogen · Kimi K3.1 Pro

同一条提示词,两个模型,经网关实测

提示词 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 通过 · 3 sentences

Enabling reasoning makes the model generate extra internal “thinking” tokens before responding, and these are typically billed at output-token rates even though users never see them. If request volume and pricing stayed flat but reasoning substantially increased tokens per request, the total bill could double. Compare pre- and post-change usage reports for reasoning tokens, then control costs with lower reasoning effort, token budgets, cheaper models, and selective use on tasks where the quality gain justifies the spend.

输出 471 tok (+366 思考) 延迟 14.3 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 通过 · 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: best = max(best, cur) cur = 1 return max(best, cur) ``` The original `cur` counts matching adjacent pairs rather than items: it starts at 0, so a singleton returns 0, and a run of `k` equal items is recorded as only `k - 1`. Its bookkeeping also never correctly finalizes the current run’s length at end of input. The fix starts every run at 1, records its length when a mismatch ends it, and takes a final `max` after the loop so a run ending at the last index is included; empty input returns 0.

输出 2984 tok (+2785 思考) 延迟 70.1 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 通过 · 5/5 fields, guidance null

{"company":"Meridian Robotics","quarter":"September quarter","revenue_usd_m":412,"growth_pct":11,"guidance":null}

输出 454 tok (+410 思考) 延迟 12.0 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 通过 · 120 words, 0 banned, 1 question

Meet Prompt Cache, our new API gateway feature for caching prompts and responses across model providers. It cuts token spend, lowers latency, and keeps applications responsive during traffic surges. Define cache keys, expiration rules, and tenant boundaries in one policy, then apply them to OpenAI, Anthropic, Gemini, or custom models without changing application code. Encryption, redaction, and immediate purges help protect sensitive data, while metrics reveal hit rates, savings, and performance by endpoint and provider. Need a faster way to handle repeated requests? Serve eligible results from cache and preserve your existing routing, fallback, and retry behavior. Available today in beta, Prompt Cache gives platform teams controls for cost, speed, and reliability, with no extra infrastructure to deploy or maintain.

输出 2740 tok (+2576 思考) 延迟 55.8 s

是否守住约束(字数预算、禁用词表、只能有一个问句)、文风特征,以及长度控制。

改一行代码就能在两个模型之间切换

下方每个标签页里都有两个模型 ID,高亮的那两行是唯一要改的地方。端点不变,API key 不变,请求结构也不变。

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",  # 取消注释此行,注释上一行
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

获取 API key →

常见问题

Gemini 4 Hydrogen 和 Kimi K3.1 Pro 哪个更便宜?

按「输入 / 1M token」算,Gemini 4 Hydrogen 更便宜($1.5 对 $2,相差 1.3×)。其他计费项的结论可能相反,完整价格见上方表格,实际成本取决于你的用量构成。

不用分别集成两次,就能对 Gemini 4 Hydrogen 和 Kimi K3.1 Pro 做 A/B 测试吗?

可以。两个模型走同一个 OpenAI 兼容端点,用同一个 API key,切换时只要改一行里的模型名,所以可以给两个模型各分一部分流量,直接对比账单。

Gemini 4 Hydrogen 和 Kimi K3.1 Pro 支持提示词缓存吗?

支持。两个模型的缓存读取价都低于各自的输入价,所以前缀能反复命中缓存的负载,实际成本会比按官网价估算的低。具体的缓存读取价见上方价格表。

相关对比