Free Intensive Nov 21–22Free 2-day hands-on Vibecoding Intensive on Nov 21–22 at 16:00 MSK (Sat–Sun) · Live Cohort 3 starts Nov 23Join Free →Cohort 3 (Nov 23)

Gemini 4 Hydrogen: Google's Junior Model Beats the Senior Argon and Runs 2.5x Faster Than Flash

Gemini 4 Hydrogen, the junior model by name, scores one point higher than Argon, one of Google's two senior models, on the Artificial Analysis leaderboard. Google itself says it solves tasks 2.5x faster than Gemini 3.8 Flash and makes up facts five times less often. In the API, it costs $1.5 per million input tokens and $7.5 per million output tokens. The speed and accuracy figures come only from the vendor for now, so run the model on your own prompts before migrating.

AI-processed from TG: @TochkiNadAI (Точки над ИИ); edited by Hamidun News
Gemini 4 Hydrogen: Google's Junior Model Beats the Senior Argon and Runs 2.5x Faster Than Flash
Source: TG: @TochkiNadAI (Точки над ИИ). Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceTG: @TochkiNadAI (Точки над ИИ) ↗
Editor-in-Chief
Key metric #1Free users are routed to the model automatically based on the query.
Example costa 2,000-token prompt plus a 500-token reply is about $0.007.
Key metric #3Output tokens cost five times more than input tokens, so calculate long responses separately.

Usually the model lineup is clear: the junior model is cheaper and faster but weaker, and you pay for quality with the senior one. Google has just broken that logic with a name. Gemini 4 Hydrogen is the junior model of the family by name, yet on default settings in the Artificial Analysis composite leaderboard it scores one point higher than Argon, one of the two senior models from the same Google.

Google also claims that Hydrogen solves tasks 2.5x faster than Gemini 3.8 Flash (a fast, cheap model from the previous generation) and makes up facts five times less often.

Artificial Analysis is a third-party index that combines model results across different tests into a single score. A token is a piece of text, roughly a syllable or a short word; it is what the API charges for.

What is actually claimed

The leaderboard position is the only point that was not calculated by Google itself. The one-point gap over Argon is tiny, so calling it a "win" is premature: for most applied tasks the difference is barely noticeable. What is more interesting is that the junior model turned out to be on par with the senior one.

The other two figures come from Google's own materials: speed is 2.5x higher than Gemini 3.8 Flash, and there are five times fewer invented facts. Fabrication here means the model confidently writes something that does not exist: a nonexistent API function, a wrong date, a fake quote. The announcement summary does not show which set of tasks was used or how the numbers were measured. So "5x less often" is better read as "in Google's tests." Independent measurements usually appear later, and until then these two numbers should be treated as a claim, not an established fact.

What it costs in practice

For those building products on the API, the price is $1.5 per million input tokens and $7.5 per million output tokens. Take an everyday example: a support bot receives a customer's question along with a chunk of documentation, which is 2,000 input tokens, and replies with 500 tokens. The input costs $0.003, the output $0.00375. The total is about $0.007 per conversation, or roughly $6.75 per thousand such requests.

For an internal assistant with moderate load, the sum is small. For a service handling millions of requests a day, something else matters more: output tokens cost five times more than input tokens. If an agent reasons aloud a lot and writes long answers, the bill will be driven by output, not by the prompt.

What developers and product managers should do

Hydrogen is already rolling out, including to free users. There, the specific model is selected automatically for each query, so the user does not choose it. For you as a developer, this means evaluating the model through the API, where the choice remains under your control.

A practical plan is simple:

  • Collect 50–100 real queries from your product and run them through Hydrogen and your current model. Compare three things: answer quality, latency, and cost.
  • Check fabrications separately on your own data, especially where exact figures, names, and links matter. A promise of "5x less often" does not guarantee your scenario will improve by the same amount.
  • If you are currently on Gemini 3.8 Flash, migration looks like a logical candidate, since the main arguments are speed and price.
  • Do not switch production over a single leaderboard position. One point above Argon is a reason to test, not a reason to change your stack.

Limitations

Google chose to compare against the previous generation's Flash rather than the current senior model. That is normal for marketing, but for your decision it is more useful to compare against what you use now. In addition, all speed and accuracy figures so far come from a single source: the vendor itself.

The author of the original post adds a taste-based remark: he likes the periodic-table naming, but finds the interactive animation in the announcement looks vibe-coded and sells poorly. This has nothing to do with the quality of the model.

Bottom line: Hydrogen looks like Google's attempt to remove the familiar ladder where the junior model is cheap but weak. Whether independent measurements will confirm this is unknown, but the price and claimed speed are attractive enough to spend a day on your own tests.

Story

Key Questions Answered

What is actually claimed?

The leaderboard position is the only point that was not calculated by Google itself. The one-point gap over Argon is tiny, so calling it a "win" is premature: for most applied tasks the difference is barely noticeable. What is more interesting is that the junior model turned out to be on par with the senior one. The other two figures come from Google's own materials: speed is 2.5x higher than Gemini 3.8 Flash, and there are five times fewer invented facts.

What it costs in practice?

For those building products on the API, the price is $1.5 per million input tokens and $7.5 per million output tokens. Take an everyday example: a support bot receives a customer's question along with a chunk of documentation, which is 2,000 input tokens, and replies with 500 tokens. The input costs $0.003, the output $0.00375. The total is about $0.007 per conversation, or roughly $6.75 per thousand such requests. For an internal assistant with moderate load, the sum is small.

What developers and product managers should do?

Hydrogen is already rolling out, including to free users. There, the specific model is selected automatically for each query, so the user does not choose it. For you as a developer, this means evaluating the model through the API, where the choice remains under your control. A practical plan is simple: Collect 50–100 real queries from your product and run them through Hydrogen and your current model. Compare three things: answer quality, latency, and cost.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Unified AI Workspace · Nomad

Test Frontier LLMs & Autonomous Agents in One Workspace

Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.

Try Nomad AI →Launch Nomad Agent
What do you think?
Loading comments…