Gemini 4 Hydrogen vs Tencent Hy4

vs

Which one, when

Choose gemini-4-hydrogen if your coding workflow needs direct audio or video input alongside screenshots. At 100000 input tokens, gemini-4-hydrogen costs $1.5/$7.5 and hy4 costs $0.834/$2.501 per million input/output tokens.

Benchmarks

Tencent Hy4: the vendor has not published benchmark scores.

Gemini 4 Hydrogen: 10 published, but no benchmark it shares with enough other models to compare.

Gemini 4 Hydrogen Tencent Hy4 other models measured peer average ★ no peer scored higher
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

Vendor-published: Google

Pricing

Gemini 4 Hydrogen Tencent Hy4 Δ
Input / 1M tokens $1.5 $0.834 1.8×
Output / 1M tokens $7.5 $2.501 3×
Cache read / 1M tokens $0.075 $0.042 1.8×

Rates from the live catalogue at build time; each model page carries the current rate card.

Where they sit · input price per 1M tokens across all 86 chat models on this billing unit (log scale)

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

Capabilities

Gemini 4 Hydrogen Tencent Hy4
Tool calling yes yes
Thinking control always on yes (vendor dial not published)
Structured output yes -
Prompt caching implicit (automatic) implicit (automatic)
Cache lifetime not published not published
Minimum cached prefix 4,096 tokens not published

Specs

Gemini 4 Hydrogen Tencent Hy4
Input modalities text image audio video text image
Output modalities text text
Released 2026-11-12 2026-11-04
Knowledge cutoff 2026-03 -
Context window 1,048,576 1,048,576
Max output 65,536 65,536
Thinking parameter thinking_level -
Accepted values
thinking_level
  • low
  • medium
  • high
  • xhigh

"minimal" and thinking_budget return 400

-
Default high -

Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: Gemini 4 Hydrogen · Tencent Hy4

One prompt, both models, measured through the gateway

PROMPT Explain to a CFO, in exactly three sentences, why our LLM bill doubled after we enabled reasoning. CHECK exactly 3 sentences

Gemini 4 Hydrogen passed · 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.

out 1236 tok (+1136 thinking) latency 9.0 s

Tencent Hy4 passed · 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.

out 1519 tok (+1409 thinking) latency 21.0 s

Instruction following (exactly three sentences, so countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.

PROMPT 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. CHECK fix passes tests

Gemini 4 Hydrogen passed · 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.

out 1489 tok (+1247 thinking) latency 10.8 s

Tencent Hy4 passed · 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. […]

out 4509 tok (+4263 thinking) latency 56.0 s

Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.

PROMPT 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. CHECK valid JSON, schema exact

Gemini 4 Hydrogen passed · 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" } ```

out 3165 tok (+3100 thinking) latency 21.2 s

Tencent Hy4 passed · 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"}

out 9869 tok (+9827 thinking) latency 125.2 s

Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.

PROMPT 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. CHECK 120 words, 0 banned words

Gemini 4 Hydrogen passed · 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.

out 3710 tok (+3574 thinking) latency 24.1 s

Tencent Hy4 passed · 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.

out 5744 tok (+5601 thinking) latency 57.6 s

Constraint obedience (word budget, banned-word list, the single question), style fingerprint, and length control.

Switch between them with one line

Both ids are in every tab below; the highlighted pair of lines is the only edit. Same endpoint, same key, same request shape.

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",  # uncomment this line, comment the one above
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

Get your API key →

FAQ

Which is cheaper, Gemini 4 Hydrogen or Tencent Hy4?

Tencent Hy4 is cheaper on the "Input / 1M tokens" row ($0.834 vs $1.5, 1.8× apart). Other rows may point the other way; the table above carries the full rate card, and real cost depends on your mix.

Can I A/B test Gemini 4 Hydrogen against Tencent Hy4 without two integrations?

Yes. Both are served through the same OpenAI-compatible endpoint with one API key. Switching is a one-line change to the model id, so you can route a fraction of traffic to each and compare bills directly.

Do Gemini 4 Hydrogen and Tencent Hy4 support prompt caching?

Yes. Both bill cache reads below their input rate, so warm-prefix workloads cost less than the list rates suggest. The exact cache-read rows are in the pricing table above.

Related comparisons