Gemini 4 Hydrogen vs GPT-6.1 Terra

vs

Which one, when

Choose gemini-4-hydrogen if your coding workflow needs direct audio or video input alongside screenshots. For prompts up to 272000 input tokens, gemini-4-hydrogen costs $1.5/$7.5 and gpt-6.1-terra costs $1/$5 per million input/output tokens.

Benchmarks

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

GPT-6.1 Terra: 9 published, but no benchmark it shares with enough other models to compare.

Gemini 4 Hydrogen GPT-6.1 Terra other models measured peer average ★ no peer scored higher
SWE-sweep Hydrogen: Antigravity CLI 1.4.8. Peers: official leaderboard
13.5%
5.8%
OSWorld 2.1 82 offline tasks, partial score. Hydrogen and Sonnet: best of 3. Terra: system card
77.6%
74.2%
Agents’ Last Exam v1.1 Oct 17 task set. Hydrogen: Antigravity CLI. Sonnet: ALE-Claw. Terra: official leaderboard
71.6%
69.8%
HLE-Diamond Artificial Analysis leaderboard, November report
58.8%
47.3%
Vending-Bench 2 (USD) Andon Labs leaderboard, Hydrogen report · 9107-14549
14549
9107
Chartography No tools. Hydrogen and Terra: Google evaluation. Sonnet: system card
66.6%
63.2%

Vendor-published: Google

Pricing

Gemini 4 Hydrogen GPT-6.1 Terra Δ
Input / 1M tokens $1.5 $1 1.5×
Output / 1M tokens $7.5 $5 1.5×
Cache read / 1M tokens $0.075 $0.05 1.5×
Cache write - 1.25x (30m) / 2.5x (12h) -

Rates from the live catalogue at build time; each model page carries the current rate card. The main table shows base rates. Prompt length can change the rate for the entire request. See each model’s full rate card.

GPT-6.1 Terra · Rates by prompt length

The whole request uses the rate for its input-length tier. Prices are USD per million tokens.

Input tokensInputOutput
0 - 272,000 $1 $5
272,001 - 1,050,000 $2 $7.5

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

Capabilities

Gemini 4 Hydrogen GPT-6.1 Terra
Tool calling yes yes
Thinking control always on configurable
Structured output yes yes
Prompt caching implicit (automatic) implicit + explicit
Cache lifetime not published at least 30m by default, 12h option on the Responses API
Minimum cached prefix 4,096 tokens 1,024 tokens

Specs

Gemini 4 Hydrogen GPT-6.1 Terra
Input modalities text image audio video text image
Output modalities text text
Released 2026-11-12 2026-10-26
Knowledge cutoff 2026-03 2026-06
Context window 1,048,576 1,050,000
Max output 65,536 128,000
Thinking parameter thinking_level reasoning.effort
Accepted values
thinking_level
  • low
  • medium
  • high
  • xhigh

"minimal" and thinking_budget return 400

reasoning.effort
  • none
  • low
  • medium
  • high
  • xhigh
  • max
Default high medium

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 · GPT-6.1 Terra

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

GPT-6.1 Terra passed · 3 sentences

Enabling reasoning caused the model to process additional internal tokens before producing each answer, even though those tokens are not visible to users. Those tokens are generally billable, increasing the cost per request and potentially doubling the bill even if usage stayed the same. To confirm the cause, compare request counts, model pricing, and token usage—including reasoning tokens—before and after the change.

out 196 tok (+115 thinking) latency 4.6 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

GPT-6.1 Terra passed · 8/8 cases

```python def longest_run(xs): if len(xs) == 0: return 0 best = 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 original code counted matching *adjacent pairs* rather than items, so every nonempty run was undercounted by one, including a single-element input. It did update `best` for matches at the last index, but still undercounted those runs. The fix starts each run at length one and updates `best` as the run grows.

out 331 tok (+172 thinking) latency 6.3 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

GPT-6.1 Terra passed · 5/5 fields, guidance "Withheld pending the Q4 close"

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

out 317 tok (+261 thinking) latency 6.9 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

GPT-6.1 Terra passed · 120 words, 0 banned, 1 question

Meet Prompt Cache, a new API gateway feature that stores reusable prompts across providers, helping teams reduce latency and control costs without changing how they build. When a request matches a cached prompt, the gateway retrieves the stored result instead of sending the same work again. Need to route traffic between models or vendors? Prompt Cache works across supported providers, giving your applications a consistent caching layer as your stack evolves. Set expiration policies, monitor cache performance, and choose which requests qualify through familiar gateway controls. Your team can spend less time repeating requests and more time improving the experiences customers rely on. Start using Prompt Cache today and make every request work harder for your application and your budget.

out 579 tok (+440 thinking) latency 9.1 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="gpt-6.1-terra",  # 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 GPT-6.1 Terra?

The main table shows base rates. Prompt length can change the rate for the entire request. See each model’s full rate card.

Can I A/B test Gemini 4 Hydrogen against GPT-6.1 Terra 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 GPT-6.1 Terra 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

From our measured studies