Gemini 4 Carbon responds on Vertex AI global endpoint in live API call
According to AI tracker reporting on X, a live call through Vertex AI’s global endpoint from a new Google Cloud project yielded replies naming Gemini 4 Carbon, with metadata listing gemini-4-carbon as the model version. The account notes that name still lacks a matching row on the public Gemini API model list, implying cloud routing may run ahead of published model inventories. Teams standardizing on Vertex for traffic should watch such endpoint behavior when planning upgrades, because early slug responsiveness often appears before documented product cuts. Related chatter in the same reporting thread mentions GCP SKU catalog listing as a possible harbinger, but the packet supplies no official Google launch materials. Whether every GCP project can hit the slug remains unclear in the sourced reporting.
Gemini 4 Carbon responds on Vertex AI global endpoint in live API call
A report documents calling gemini-4-carbon from a brand-new Google Cloud project on the global endpoint. The response identified as Gemini 4 Carbon and the model version field showed gemini-4-carbon. The same report notes it is not yet on the public Gemini API model list.
Key takeaway
Gemini 4 Carbon may already be callable on Vertex AI’s global endpoint while remaining absent from the public Gemini API model list.
What happened
An X post attributed to AI tracker reporting describes a successful live API call using the gemini-4-carbon identifier from a brand-new Google Cloud project on the global Vertex AI endpoint.
The model reply reportedly identified itself as Gemini 4 Carbon, and the response metadata’s model version field showed gemini-4-carbon, even though the author states the name is not yet on the public Gemini API model list.
Evidence
Callers can invoke gemini-4-carbon on Vertex AI’s global endpoint from a new GCP project.
X · attributed
We just called gemini-4-carbon from a brand-new Google Cloud project on the global endpoint.
The live response self-identified as Gemini 4 Carbon with matching version metadata.
X · attributed
It answered as "Gemini 4 Carbon", and the response's model version field says gemini-4-carbon.
The model is not yet listed on the public Gemini API model list.
X · attributed
The same report notes it is not yet on the public Gemini API model list.
Related reporting ties Carbon to GCP SKU catalog listing as a release readiness signal.
X · attributed
Gemini 4 Carbon appears to be prepared for release on Google Cloud and is now listed in the GCP SKUs catalog.
Why it matters
A responsive Vertex slug without a public API list entry usually precedes wider documentation and can shift integration planning for teams standardizing on Google Cloud model routing.
Limits and uncertainties
The packet is single-source social reporting and does not include an official Google blog post, changelog, or pricing announcement.
It is unclear whether all GCP projects, regions, or entitlement paths can call gemini-4-carbon or only certain account setups.
Practical implications
Teams on Vertex should verify gemini-4-carbon in their own project on the global endpoint instead of relying solely on the public Gemini API model list.
Production rollouts should stay gated until Google publishes list entries, SKU visibility, and supported capability documentation for Carbon.
What to watch
Appearance of gemini-4-carbon on Google’s public Gemini API model list and Vertex model documentation.
Independent confirmation from additional GCP projects that the global endpoint returns gemini-4-carbon consistently.
Original reporting: Gemini 4 Carbon is live on Vertex AI 🟢
We just called gemini-4-carbon from a brand-new Google Cloud project on the global endpoint. It answered as "Gemini 4 Carbon", and the respo