changelogGoogle

Google opens Gemini 4 Carbon to paying developers; API rates double to $4 input, $20 output per 1M tokens on Dec. 1

TL;DR

Google opened Gemini 4 Carbon, its newest reasoning model, to paying developers and enterprises on November 10. Introductory API prices expire November 30, and standard input and output rates double on December 1, according to eWeek.

2 min read
0

Google opened Gemini 4 Carbon, its newest reasoning model, to paying developers and enterprises on November 10. Introductory API prices expire November 30, and standard input and output rates double on December 1, according to a report from eWeek.

Rollout

The November 10 expansion follows an October 28 rollout that was limited to selected cybersecurity defenders. Carbon is now available through Google's paid developer API and its enterprise products.

In its November 10 announcement, Google positioned Carbon for complex coding, scientific research, cybersecurity and multistep AI workflows.

API pricing

Google's published API rates, per 1M tokens:

Token type Through Nov. 30 From Dec. 1
Standard input $2 $4
Standard output $10 $20
Cached input $0.10 $0.20

Carbon supports implicit caching.

Carbon and Gemini 4 Argon

eWeek reports that Carbon's per-token prices match those of Gemini 4 Argon. The outlet frames the choice for enterprise AI teams as a cost question: whether Carbon's deeper reasoning justifies the additional computing costs, or whether Gemini 4 Argon can handle the same workloads more economically.

What this means

The price change is scheduled, not a surprise: the introductory rates carry a fixed end date of November 30, and the standard rates take effect the next day. Teams that plan to run Carbon in production need to budget against the December 1 figures of $4 per 1M input tokens and $20 per 1M output tokens, not the introductory ones.

The cached input rate is also part of the change, moving from $0.10 to $0.20 per 1M tokens. Because Carbon supports implicit caching, workloads that resend large shared prompts are affected by that line item as well as by the standard input and output rates.

The practical evaluation, as eWeek describes it, is a workload-by-workload comparison between Carbon and Gemini 4 Argon. Google's targeted use cases for Carbon are complex coding, scientific research, cybersecurity and multistep workflows. Those are the areas where a team would test whether Carbon's reasoning depth justifies its compute costs over Argon.

The source article does not report Carbon's context window, benchmark scores or parameter count.

Related Articles

product update

Gemini 4 Carbon is now generally available in GitHub Copilot

GitHub says Gemini 4 Carbon, Google's latest model, is now generally available in GitHub Copilot. GitHub describes it as designed for complex coding, agentic and reasoning tasks, with a focus on secure code generation.

model release

Google rolls out Gemini 4 Carbon to AI Ultra subscribers at $2/$10 per 1M tokens, Argon stays

Google is rolling out Gemini 4 Carbon to AI Ultra subscribers in the Gemini app, AI Mode and Antigravity, following last month's preview. Introductory API pricing is $2 per 1M input tokens and $10 per 1M output tokens until November 30, and Argon remains available for AI Pro and up.

model release

Google releases Gemini 4 Argon for robot control, reports 87% on ERQA without helper tools

Google has released Gemini 4 Argon, a general-purpose physical-reasoning model for robot control, Real2Sim scene construction, robot video labeling and iterative policy improvement. Google reports 87% on the ERQA benchmark using pure reasoning, and says that leads other frontier models. It is available to Google AI Ultra subscribers and via the paid Gemini API as gemini-4-argon.

product update

Google launches Gemini Decisions API, handling up to 1,000 independent questions per request

Google introduced the Gemini Decisions API on November 11, 2026. The endpoint, powered by Gemini Decision 1, evaluates as many as 1,000 independent questions across text, images, audio, video and PDFs in a single request.

Comments

Loading...