Gemini 4 Hydrogen vs Tencent Hy4
什麼情況選哪一個
程式設計流程需要直接輸入音訊或影片與截圖時,選 gemini-4-hydrogen。 輸入為 100000 token 時,每百萬輸入/輸出 token 的費率為 gemini-4-hydrogen $1.5/$7.5,hy4 $0.834/$2.501。
Benchmark 成績
Tencent Hy4:供應商沒有公布 benchmark 成績。
Gemini 4 Hydrogen:公布了 10 項,但每一項都沒有夠多其他模型的成績,無法比較。
供應商公布: Google
定價
| Gemini 4 Hydrogen | Tencent Hy4 | Δ | |
|---|---|---|---|
| 輸入 / 1M tokens | $1.5 | $0.834 | 1.8× |
| 輸出 / 1M tokens | $7.5 | $2.501 | 3× |
| 快取讀取 / 1M tokens | $0.075 | $0.042 | 1.8× |
費率取自網站建置時的即時目錄;各模型頁面都列有最新的價目。
兩者的相對位置:每 1M tokens 的輸入價格,涵蓋同一計費單位下全部 86 個聊天模型(對數尺度)
功能
| Gemini 4 Hydrogen | Tencent Hy4 | |
|---|---|---|
| 工具使用 | 是 | 是 |
| 思考控制 | 一律開啟 | 是,但供應商未公布調整參數 |
| 結構化輸出 | 是 | - |
| 提示詞快取 | 隱式(自動) | 隱式(自動) |
| 快取存活時間 | 未公布 | 未公布 |
| 最小快取前綴 | 4,096 個 token | 未公布 |
規格
| Gemini 4 Hydrogen | Tencent Hy4 | |
|---|---|---|
| 輸入模態 | 文字 圖像 音訊 影片 | 文字 圖像 |
| 輸出模態 | 文字 | 文字 |
| 發布日期 | 2026-11-12 | 2026-11-04 |
| 知識截止日期 | 2026-03 | - |
| 上下文視窗 | 1,048,576 | 1,048,576 |
| 最大輸出 | 65,536 | 65,536 |
| 思考參數 | thinking_level | - |
| 可接受的值 | thinking_level
"minimal" and thinking_budget return 400 | - |
| 預設值 | high | - |
規格摘錄自各供應商的文件;供應商沒有公布的項目就直接略過,不自行推測。 完整來源: Gemini 4 Hydrogen · Tencent Hy4
同一段提示詞,兩個模型,經閘道實測
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
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 計量顯示出的隱藏思考計費落差。
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
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 效率。
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
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),以及結構化輸出路徑的差異。
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
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-hydrogen",
# model="hy4", # 取消這一行的註解,並把上一行註解掉
messages=[{"role": "user", "content": "Summarize this diff"}],
reasoning_effort="medium",
)
print(resp.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://synthorai.io/v1",
apiKey: "sk-syn-...",
});
const resp = await client.chat.completions.create({
model: "gemini-4-hydrogen",
// model: "hy4", // 取消這一行的註解,並把上一行註解掉
messages: [{ role: "user", content: "Summarize this diff" }],
reasoning_effort: "medium",
});
console.log(resp.choices[0].message.content);curl https://synthorai.io/v1/chat/completions \
-H "Authorization: Bearer sk-syn-..." \
-H "Content-Type: application/json" \
-d '{
"model": "gemini-4-hydrogen",
# "model": "hy4", # 取消這一行的註解,並把上一行註解掉
"messages": [{"role": "user", "content": "Hello"}],
"reasoning_effort": "medium"
}'package main
import (
"context"
"fmt"
"github.com/openai/openai-go/v3"
"github.com/openai/openai-go/v3/option"
)
func main() {
client := openai.NewClient(
option.WithBaseURL("https://synthorai.io/v1"),
option.WithAPIKey("sk-syn-..."),
)
resp, _ := client.Chat.Completions.New(context.TODO(), openai.ChatCompletionNewParams{
Model: "gemini-4-hydrogen",
// Model: "hy4", // 取消這一行的註解,並把上一行註解掉
Messages: []openai.ChatCompletionMessageParamUnion{
openai.UserMessage("Summarize this diff"),
},
ReasoningEffort: openai.ReasoningEffortMedium,
})
fmt.Println(resp.Choices[0].Message.Content)
}import com.openai.client.OpenAIClient;
import com.openai.client.okhttp.OpenAIOkHttpClient;
import com.openai.models.chat.completions.*;
import com.openai.models.ReasoningEffort;
OpenAIClient client = OpenAIOkHttpClient.builder()
.baseUrl("https://synthorai.io/v1")
.apiKey("sk-syn-...")
.build();
ChatCompletion resp = client.chat().completions().create(
ChatCompletionCreateParams.builder()
.model("gemini-4-hydrogen")
// .model("hy4") // 取消這一行的註解,並把上一行註解掉
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));常見問題
Gemini 4 Hydrogen 和 Tencent Hy4 哪個比較便宜?
以「輸入 / 1M tokens」來看,Tencent Hy4 比較便宜($0.834 對 $1.5,相差 1.8×)。其他項目的結果可能相反,完整價目請看上表;實際成本要看你的用量組合。
可以只串接一次,就對 Gemini 4 Hydrogen 和 Tencent Hy4 做 A/B 測試嗎?
可以。兩個模型都走同一個 OpenAI 相容端點,用的也是同一把 API 金鑰,切換時只要改一行裡的模型名稱字串。你可以把一部分流量分別導到兩邊,再直接比較帳單。
Gemini 4 Hydrogen 與 Tencent Hy4 支援提示詞快取嗎?
支援。兩者的快取讀取費率都低於輸入費率,所以前綴已經進快取的工作負載,實際成本會比官網價算出來的低。確切的快取讀取價格請見上方定價表。