Skip to main content
Google

Gemini 4 Hydrogen

Gemini 4 Hydrogen is a chat model from Google, tracked here with third-party throughput and latency measurements alongside provider pricing.

Input from
$1.50 / 1M tokens
on OpenRouter · 1 provider
Output from
$7.50 / 1M tokens
on OpenRouter

API Pricing

ProviderInput / 1MOutput / 1MCached / 1M
$0.750$3.75$0.037
$1.50$7.50$0.075

Prices updated daily. Last check: Nov 13, 2026

Compare API pricing for every Gemini model →

Gemini 4 Hydrogen pricing by provider

Input, output, and batch rates, plus alternatives, for one provider at a time.

Performance & Benchmarks

Source: Artificial Analysis →
Intelligence
53.9 / 100
Output Speed
261 t/s
Latency (TTFT)
65.1s

Benchmarks measured Nov 2026. Scores are independent evaluations, not vendor-reported.

Model Details

General

Creator
Google
Modalities
Text

Capabilities

Strengths & Limitations

Strengths

  • Measured output throughput of approximately 249 tokens per second, which shortens wall-clock time on long generations
  • Part of Google's Gemini family, so it fits workflows already built around Google model APIs and tooling conventions
  • Streaming output rate makes it practical for use cases where the full response is consumed rather than read word by word
  • Tracked across multiple serving providers on this page, allowing direct price comparison for the same model
  • Independent runtime benchmarks from Artificial Analysis are available rather than only vendor-published figures

Limitations

  • Time to first token of roughly 9.3 seconds, which is slow for interactive chat interfaces where immediate feedback matters
  • Context window size is not confirmed in our data, so long-document workloads need verification against provider documentation
  • We do not track confirmed quality benchmark scores for this model, making capability comparisons against peers difficult
  • Supported input modalities are not recorded in our metadata and should be checked with the serving provider
  • Latency and throughput can vary by provider and region, so the single benchmark figure may not match your deployment

Key Features

•Chat/conversational text generation interface
•Measured ~249 output tokens per second (Artificial Analysis)
•Measured ~9.3 second time to first token (Artificial Analysis)
•Part of Google's Gemini model family
•Available through API endpoints tracked in the pricing table on this page
•Streaming response support typical of Gemini API chat endpoints

About Gemini 4 Hydrogen

Gemini 4 Hydrogen is a chat-oriented large language model from Google, part of the company's Gemini line of general-purpose assistant and API models. Our catalog entry covers it as a conversational text model, and this page tracks the providers that serve it along with their current pricing. The measurements we hold for Gemini 4 Hydrogen come from Artificial Analysis and describe runtime behavior rather than quality: a median output rate of roughly 249 tokens per second and a time to first token of about 9.3 seconds. That combination is characteristic of a model that spends meaningful time before emitting its first token — often associated with longer internal processing or routing — and then streams the response quickly once generation begins. For a user watching a response appear, the perceived wait is front-loaded; for batch or pipeline work, the high sustained output rate dominates total completion time on long generations. Beyond those figures, we do not currently track confirmed details such as the context window, supported input modalities, or tool-calling behavior for Gemini 4 Hydrogen. Readers who need those specifics should check Google's own model documentation or the serving provider's API reference, since capabilities can also differ between endpoints that expose the same model. The pricing table on this page is the authoritative place to compare what each provider charges.

Common Use Cases

Gemini 4 Hydrogen's measured profile — a long time to first token paired with fast sustained generation — suits workloads where the complete output matters more than instant responsiveness. That includes batch content generation, document drafting and rewriting, summarization pipelines, backend agents that call the model asynchronously, and offline evaluation or data-labeling jobs where a few extra seconds of startup cost is amortized across a long response. It is a weaker fit for latency-sensitive front-ends such as autocomplete, voice assistants, or live customer-facing chat, where users notice the initial delay. Because our metadata does not confirm the context window or modality support, teams planning long-context retrieval or multimodal pipelines should validate those requirements against Google's documentation before committing.

Frequently Asked Questions

How much does Gemini 4 Hydrogen cost?

Pricing varies by provider and by pricing type — input tokens, output tokens, cached input, and batch rates are often billed differently. Because providers adjust rates frequently, see the pricing table on this page for current per-provider figures rather than relying on any fixed number.

What is Gemini 4 Hydrogen best used for?

It fits text generation workloads where throughput matters more than instant first-token response: batch generation, summarization, drafting, and asynchronous backend agents. Its measured ~9.3 second time to first token makes it less suitable for highly interactive chat or voice interfaces.

How fast is Gemini 4 Hydrogen?

Artificial Analysis measures it at roughly 249 output tokens per second with a time to first token of about 9.3 seconds. In practice that means a noticeable pause before the response starts, followed by rapid streaming. Actual numbers depend on the provider, region, prompt length, and load.

What context window does Gemini 4 Hydrogen support?

Our database does not currently hold a confirmed context window figure for this model. Check Google's model documentation or the specific serving provider's API reference, since context limits can also differ between endpoints offering the same model.

Does Gemini 4 Hydrogen accept image input or support tool calling?

We do not track confirmed modality or tool-calling details for this model, so we cannot state either way. The serving provider's API documentation is the right place to verify which input types and function-calling features are exposed on the endpoint you plan to use.