Gemini 4 Hydrogen vs Argon: Which Model Should You Use?
Compare Gemini 4 Hydrogen and Argon for coding, agents and long documents: thinking defaults, output limits, current prices and three measured API checks.
Read as MarkdownStart with Gemini 4 Hydrogen for everyday coding, interactive applications and repeated extraction tasks. Put Gemini 4 Argon on your shortlist when the job involves difficult reasoning across many steps. That recommendation follows Google's positioning; it is a starting point for testing your own workload, not a measured quality ranking.
As of November 13, 2026, Hydrogen has official documentation and a callable API. We verified three Hydrogen requests through SeedRouter: structured JSON, streaming and a function call. We did not run a paired Hydrogen–Argon benchmark. This comparison separates the documented differences from those limited observations.
What are Gemini 4 Hydrogen and Argon?
Both are Gemini 4 models with the same native request structure. Google describes Hydrogen as suited to everyday coding, interactive apps and tool-using agents, including parallel subagents. Argon is positioned for advanced reasoning and longer tasks. The official IDs are gemini-4-hydrogen and gemini-4-argon. Google's Hydrogen guide explains how to move between them.
Earlier articles described Hydrogen as an unreleased Flash codename. Use the current documented model ID when integrating it; a rumor or an Arena label is not an API contract. Availability in one application also does not establish access through your API account or coding tool.
Carbon is another Gemini 4 option. Google positions it for deeper reasoning, with more thinking per turn than Argon. That makes the family a set of task choices, rather than a rule that every new model replaces the previous one. See the official Carbon guide for that distinction.
Choose by the work you need to finish
The useful question is which model completes your task within its quality, time and cost limits. A model name alone does not answer that.
| Your work | Start by testing | What would justify trying the other model? |
|---|---|---|
| Repeated classification, extraction or short summaries | Hydrogen | Missing fields, unsupported statements or corrections that erase the token-price saving |
| Interactive coding and small feature changes | Hydrogen | Failing tests, unnecessary edits or repeated attempts to finish a change |
| Difficult debugging, architecture review or a long tool sequence | Argon | Hydrogen produces equally acceptable results at a lower total cost or shorter completion time |
| Research across long documents, tables or recordings | Both on the same materials | Compare source fidelity, numerical accuracy and overlooked constraints |
| A user-facing feature with a strict response deadline | Hydrogen as an initial candidate | Measure time to first useful output and full completion before committing |
For financial or legal documents, require references to the relevant passages and have a qualified reviewer check consequential conclusions. A large context window does not establish professional accuracy. For a simple high-volume classifier, also compare your existing smaller model: neither frontier option is automatically necessary.
Capabilities and limits that change the decision
The following values come from Google's model-specific documentation, checked on November 13. Documented support is broader than the three integration checks we performed.
| Capability | Gemini 4 Hydrogen | Gemini 4 Argon |
|---|---|---|
| Shared context budget | 1,048,576 tokens across input, thinking and output | Same |
| Thinking levels | low, medium, high, xhigh | low, medium, high |
| Default thinking level | high | medium |
| Output budget per streaming response | 65,536 tokens | 65,536 tokens |
| Output budget per non-streaming response | 65,536 tokens | 32,768 tokens |
| Inputs | Text, images, audio, video and PDF | Same |
| Output modality | Text | Text |
| Long decode | Continuation across responses within the shared budget | Same |
| Explicit context caching | Unsupported; implicit caching is available | Same |
The default effort difference matters. Changing only the model ID while leaving thinking unspecified gives Hydrogen high and Argon medium. For a comparison, explicitly select a level both accept. The same level name still does not guarantee the same number of thinking tokens or equivalent reasoning work.
maxOutputTokens includes thinking as well as the answer. A small limit can leave little room for visible text. Likewise, a million-token context window does not mean a million-token answer in a single response. Long decode uses continuationToken; follow the documented continuation procedure and account for the input billed on each request.
Both accept mixed media as input, but neither is an image or audio generation model. API limits also do not describe upload limits in the Gemini consumer app. Review the Hydrogen API reference before migrating media, built-in tools or continuation workflows. We have not verified those workflows through SeedRouter in this test.
Compare the cost of a completed task
API token charges and consumer subscriptions are separate products. Paying for a Gemini app plan does not itself establish an API budget or access through another service.
Google's standard list prices, checked on November 13, 2026, are below. Output includes thinking. Argon's announced introductory period ends on November 30; its December column is Google's announced schedule, not a promise about future SeedRouter rates. Google pricing
| Per 1M tokens | Hydrogen, current standard price | Argon, through November 30 | Argon, from December 1 |
|---|---|---|---|
| Input | $1.50 | $2.00 | $4.00 |
| Output including thinking | $7.50 | $10.00 | $20.00 |
| Cached input | $0.075 | $0.10 | $0.20 |
At those current list prices, Hydrogen is 25% cheaper for identical quantities of each token category. It need not be 25% cheaper per finished task. Extra reasoning, another attempt or a longer answer can change the result. Read the Argon pricing section before budgeting beyond November.
Current SeedRouter rates are loaded below:
Gemini 4 Hydrogen
USD per 1M tokens
| Item | USD per 1M tokens |
|---|---|
| Input | $1.05 |
| Output, including thinking | $5.25 |
| Cached input | $0.0525 |
Current token rates. Cached input is billed once at its own rate; thinking counts as output. Check tool and processing-tier availability before using them.
Gemini 4 Argon
USD per 1M tokens
| USD per 1M tokens | googlellm | googlellm-vertext |
|---|---|---|
| Input | $0.90 | $1.40 |
| Output, including thinking | $4.50 | $7.00 |
| Cached input | $0.045 | $0.07 |
Cached tokens are part of input, not additional input. Each continuation request has its own usage. Failed requests are not charged.
Budget using uncached input, cached input and billed output separately. Add tool charges when applicable, then include every attempt needed to finish the job. Comparing only the final successful response hides the cost of earlier attempts.
Implicit caching can reduce input charges when eligible content is reused. Hydrogen's documented minimum is 4,096 input tokens; crossing that threshold does not guarantee a cache hit. Inspect reported cache usage instead of assuming the discounted rate applies to every repeated prompt. We did not test cache hits, processing tiers or grounded searches here.
What our three Hydrogen checks actually showed
On November 13, we made one paid attempt for each case below. We captured the responses and matched each request to its billing record. These were short integration checks with known expected results.
| Check | Settings | Result | Input / answer / thinking tokens | Elapsed seconds | Recorded charge |
|---|---|---|---|---|---|
| Structured JSON | low, output budget 1,024 | Returned {"ok":true} matching the schema | 191 / 21 / 68 | 3.111 | $0.000668 |
| SSE response | xhigh, output budget 2,048 | Streamed the correct answer, 323, to 17 × 19 | 47 / 7 / 154 | 4.773 | $0.000894 |
| Declared function call | low, output budget 1,024 | Requested lookup_order with order_id: A17 | 87 / 26 / 40 | 3.232 | $0.000438 |
All three completed successfully; the recorded charges totaled $0.002. Token counts agreed with the charges at the applicable rates, allowing for billing precision. A returned function call demonstrates a structured tool request, not that an external order lookup was executed.
The elapsed times are individual observations, not averages or a speed guarantee. We did not measure time to first token separately. There was no Argon control group, so these results cannot establish which model is faster, more accurate or cheaper on real work. Media understanding, grounding, Computer Use, continuation and long decode remain outside this test.
Test both on the same job before switching
Take a small set of representative tasks, including ones your current model fails. Keep the prompt, source documents, available tools and output requirements the same. Explicitly set a shared thinking level and a suitable output budget, then record these measures for every attempt:
| Measure | Evidence to keep |
|---|---|
| Correctness | Passing tests, expected fields, verified calculations and source citations |
| Unwanted changes | Unrelated edits, altered requirements or invented details |
| Completion time | Time to first useful output and time until the whole task is acceptable |
| Total cost | Input, cache and output usage across attempts and tool calls |
| Human effort | Corrections, review time and manual recovery |
For coding, run the repository's relevant tests and inspect the diff. A plausible explanation is not evidence that a patch works. For research, check whether each conclusion follows from the cited material; supplying a long document does not prevent hallucinations.
Benchmarks can disagree because effort, tools, task sets and scoring differ. Preserve those conditions when reading a leaderboard. In your own evaluation, compare cost per acceptable completed task and repeat the important cases enough to see variation. Three successful API responses are insufficient for that decision.
Tool-using agents also need appropriate permissions. Treat instructions embedded in retrieved pages or documents as untrusted content, and require review before consequential external actions. A stronger reasoning model does not remove those boundaries.
Where to try Hydrogen and Argon
Google documents access through its Gemini developer products, and Argon is also available on Google Cloud. Check the specific account, region and product you intend to use. An announcement, a consumer-app selector and a callable API are different evidence. Google Cloud's Argon announcement
On SeedRouter, start with the Hydrogen page or Argon page. Review current prices and the available model choices. Before an API request, use the read-only model list to confirm the exact ID your key can access:
curl "https://api.seedrouter.ai/v1/models" \
-H "Authorization: Bearer $SEEDROUTER_API_KEY"Set MODEL_ID to an available Hydrogen or Argon ID from that list. This example uses the native Gemini format and an explicit shared thinking level:
curl "https://api.seedrouter.ai/v1beta/models/${MODEL_ID}:streamGenerateContent?alt=sse" \
-H "Authorization: Bearer $SEEDROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"contents":[{"role":"user","parts":[{"text":"List three checks for a database migration that adds a required column."}]}],"generationConfig":{"thinkingConfig":{"thinkingLevel":"medium"},"maxOutputTokens":32768}}'Moving between the models retains the native request shape, but review defaults, output limits and unsupported levels such as Argon's lack of xhigh. For coding tools, confirm that the client supports the endpoint and the parameters you need. The full references are Hydrogen API docs and Argon API docs.
FAQ
Are there different Gemini models?
Yes. Hydrogen, Argon and Carbon are distinct Gemini 4 models. Their shared API structure does not make their thinking defaults, output limits or intended workloads identical. Choose using the task and documented model contract.
Where can I use Gemini 4 Argon?
Google documents Argon for the Gemini API and Google Cloud. SeedRouter also offers an Argon model page and API access. Consumer apps and IDEs have their own eligibility and integration requirements; confirm access in the product you plan to use.
Is Gemini 4 free?
There is no single answer for the whole family. Google's current pricing page lists a limited free tier for Hydrogen and no free API tier for Argon. Consumer-app plans are separate. SeedRouter API usage is billed at its published rates; Google's free tier does not transfer to it.
What is Gemini 4 Carbon?
Carbon is a Gemini 4 model positioned by Google for deeper reasoning and difficult tasks. Its guide says it spends more thinking tokens per turn than Argon. That may justify testing it on work Argon struggles with; it does not make Carbon necessary for routine tasks.
Is Gemini 4 Hydrogen better than Argon?
We have no paired quality result that establishes a universal winner. Hydrogen offers lower current standard token prices and an additional xhigh setting; Argon remains a candidate for advanced reasoning and long tasks. Start with the model that fits your work, then keep the one that produces acceptable results within your budget and deadline.



