Gemini 4 Carbon API
NewLLMThe Gemini 4 Carbon API is Google's Gemini 4 route for complex multi-step debugging and open-ended research, billed on the same rate card as Argon and Hydrogen: 1M context, image input and tool use.
- Input · USD / 1M tokens$0.8 USDOfficial price
$2 USD - Output · USD / 1M tokens$4 USDOfficial price
$10 USD - Savings60%
- Context1M
- View tool pricing and billing rules
What are we making today?
Bring an idea, a question, or a first draft.
01
What this model is for
The Gemini 4 Carbon API is Google's Gemini 4 route for complex multi-step debugging and open-ended research, billed on the same rate card as Argon and Hydrogen: 1M context, image input and tool use.
Gemini 4 Carbon is the third Gemini 4 route on OmniaKey, beside Argon and Hydrogen, and Google points it at complex multi-step debugging and open-ended research rather than the everyday coding loop. All three bill on one rate card, so the catalog lists the same input, output and cached-input quote for Carbon as for its siblings, over a 1M-token window with image input and tool use.
That shared quote is the point: the choice between the three is about which snapshot answers a hard case best, not about the bill. Google keeps Argon as the default for most software engineering and reserves Carbon for work where the failing path is still unknown — a multi-service incident, a flaky test that only reproduces under load, a research question with no fixed answer shape.
Best-fit coding workloads
Multi-service incident triage
Hand Carbon the logs, the recent diffs and the service map, then ask it to rank plausible causes and name the check that would confirm each one. Practical tip: require a log line or a file path next to every claim, so the list is evidence rather than guesswork.
Bugs that only fail sometimes
Give it the intermittently failing test and the code around it, and ask which ordering assumption would make it fail under load. Practical tip: paste the flaky history with the request, because the failure rate changes the answer.
Open-ended research passes
Use Carbon where you would otherwise brief a person: have it lay out a comparison, say what would falsify each option, and keep the answer in a fixed structure. Practical tip: ask for the list of assumptions to verify first, then confirm them one at a time.
02
Technical specification
Catalog facts and integration details verified for this route.
- Model ID
- gemini-4-carbon
- Context
- 1M
- Inputs and tools
- Vision · Tool use
- API endpoint
- /v1/chat/completions
- Cache hit / 1M
- $0.04 USD
- Coding clients
- Cursor · Cline · Aider
Limits to plan around
- Google keeps Argon as the everyday default and points Carbon at the hardest cases, so routing ordinary coding here buys a slower, pricier loop rather than better answers.
- We have not yet run our own verification suite on this route, so treat the sibling Gemini 4 results as the reference until Carbon's own checks are published.
- The ids are not aliases: a fleet that mixes the three Gemini 4 routes has to attribute cost per snapshot, and switching back and forth makes that harder.
03
Compare nearby models
Compare workload fit and current listed token rates before choosing a route.
| Model | Best for | Context | Input | Output |
|---|---|---|---|---|
| Gemini 4 CarbonThis page gemini-4-carbon | The Gemini 4 route for complex debugging and open research, on the same rate card as Argon and Hydrogen. | 1M | $0.8 USD Official price $2 USD | $4 USD Official price $10 USD |
| Gemini 4 Argon gemini-4-argon | The everyday Gemini 4 default: same rates and window, aimed at routine coding and knowledge work. | 1M | $0.8 USD Official price $2 USD | $4 USD Official price $10 USD |
| Gemini 4 Hydrogen gemini-4-hydrogen | Same rate card as Carbon and Argon with the newest snapshot; pick it when you want the latest answers. | 1M | $0.8 USD Official price $2 USD | $4 USD Official price $10 USD |
04
SDK quickstarts
Use one base URL and model ID from cURL, Python, or TypeScript.
curl https://api.omniakey.com/v1/chat/completions \
-H "Authorization: Bearer $OMNIAKEY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "gemini-4-carbon",
"messages": [
{"role": "user", "content": "Review this pull request"}
],
"stream": true
}'05
Estimate token cost
Enter expected input and output tokens to compare current listed rates.
- OmniaKey estimate
- $0.16
- Official-rate estimate
- $0.40
- Estimated savings
- $0.24
Estimate covers input and output tokens only. Cache usage, retries, tools, and client-side token accounting can change the final charge.
06
Related coding guides
Deeper selection, setup, and troubleshooting guidance for this model family.
Gemini 4 Carbon vs Argon: Coding and Reasoning
Google keeps Argon as its default for most coding work and points Carbon at complex multi-step debugging and open research, at the same Standard token rate.
Read guideGemini 4 Carbon: Release Date, Price and API Access
Google's November 10, 2026 update makes Gemini 4 Carbon available on the paid Gemini API, at $2 input and $10 output per million tokens through November 30.
Read guide07
Sources and verification
Model facts and links were checked on 2026-11-19. Provider documentation remains the authority for upstream behavior.
Frequently asked questions
How much does Gemini 4 Carbon cost on OmniaKey?
OmniaKey charges $0.8 USD per 1M input tokens and $4 USD per 1M output tokens, in USD. Official prices are $2 USD and $10 USD; you save 60%.
What is the context window for Gemini 4 Carbon?
The listed context window is 1M. Actual usable limits can also depend on the client and upstream request format.
How does Gemini 4 Carbon differ from Argon?
Google keeps Argon as the default for most coding and knowledge work and points Carbon at complex multi-step debugging and open-ended research. The request format and the rate card are the same, so the difference shows up in how each one reasons through a hard case.
Is Carbon more expensive than the other Gemini 4 routes?
No. Google bills all three Gemini 4 routes on one rate card, and OmniaKey publishes the same input, output and cached-input quote for Carbon, Argon and Hydrogen, so a switch never changes the per-token price.
What can I send to Gemini 4 Carbon?
Text and images across a 1M-token window, with tool calling, JSON mode and streaming, the same contract as Argon and Hydrogen.
Should we move a production integration to Carbon?
Only for the workloads Google targets: multi-step debugging and open research. Replay your evaluation set against Carbon and keep Argon for routine traffic, since the two share a rate card and differ only in how they attack a hard problem.