Check rollout eligibility, a documented model identifier and the difference between introductory and standard pricing before planning a Carbon integration.
Before changing the model in a working application, find a documented identifier and establish whether your project can call it. A leaderboard position answers neither question. That distinction matters when reading the Gemini 4 Carbon announcement.
In Google's October 28 announcement, Koray Kavukcuoglu describes initial access for selected cyber defenders. Broader developer, business and consumer availability is still forthcoming. The Gemini API catalog, checked on November 1, does not list Carbon. That observation is not a reason to invent an endpoint or promise access for a particular account.
Keep introductory and subsequent prices separate in a budget. Google announces $2 per million input tokens and $10 per million output tokens initially; its footnote gives later rates of $4 and $20. Matching prices do not justify borrowing another model's discount deadline.
Artificial Analysis's own report also distinguishes selected access from public availability and uses standard prices in its calculations. A chart comparison and an estimate using introductory rates may therefore have different bases. These are not NODVIEW test results.
The useful preparation is to assemble representative examples and acceptance criteria while retaining the current integration. Once documentation confirms access, check the exact model, calling conditions and current rates before scheduling a migration.