Google introduced Gemini 1.0 on December 6, 2023 with Ultra, Pro and Nano tiers. Gemini Pro was framed as a scalable general-purpose model for a wide variety of tasks. The family announcement was not a promise that Ultra and Nano became publicly accessible through the same API endpoint, on the same day, for every developer or region.
Historical research cutoff: 25 October 2026. Primary-source historical claims are date-scoped; cloud entitlements, region-specific availability, current pricing and rate limits are not implied.
Release identity at a glance
- Provider
- Model family
- Gemini 1.0 Pro
- Public launch
- 2023-12-06
- API ID / checkpoint
- gemini-pro
- API retirement status
- Not confirmed as retired at the research cutoff
The release and why it mattered
Google described Gemini as designed from the outset for multimodal use. That is a model-family description and must not be conflated with immediate image, video and audio inputs supported by the original `gemini-pro` endpoint. In December 2023 Google also introduced API access through AI Studio and Vertex AI, with separate controls and enterprise features across the two services.
Capabilities and genuine use cases
For early developers, natural-language Q&A, drafting and code-related assistance were basic trials. When adding the model to an application, teams needed to measure prompt injection resistance, citation quality and the tendency to produce unsupported text. A model’s broad multimodal research narrative does not validate a workflow that requires frame-by-frame video interpretation.
Integration and version identity
The historical identifier `gemini-pro` should be recorded as an API alias associated with the 1.0 era, not a guarantee of an immutable checkpoint. When reconstructing an old deployment, store the serving platform, prompt format and actual response schema. A current Gemini 3 endpoint is neither a like-for-like replacement nor evidence that historical features were present.
Limits and evidence gaps
Google’s launch made forward-looking statements about features still undergoing trust and safety review. Those future plans must not be backdated. Current quota, region, subscription and retirement facts belong to separately date-stamped Google documentation and AI 10’s commercial ledger.
How to choose or migrate
Gemini 1.0 Pro is a foundational archive entry for the Google ecosystem’s first Gemini generation. The right modern comparison begins with a defined use case and verifies current model IDs, supported inputs and governance options for the selected region.
Reproducible evaluation checklist
For Gemini, explicitly distinguish the Gemini API in AI Studio, the managed Vertex AI surface, and consumer app access. Test preview and stable versions separately with the same multimodal sample set and compare source-grounded extraction rather than marketing accuracy charts.
Before migration, check the official deprecations table for each concrete model ID and note automatic routing aliases. Record inputs, file preprocessing and tool permissions with the request.
Sources & Further Reading
- blog.google — documentation/reference (supplier-provided reference; not independently checked in this pass)
- ai.google.dev — documentation/reference (supplier-provided reference; not independently checked in this pass)
Source documentation establishes vendor-published facts, not independently measured model quality, tenant access, contractual rights or current prices. Use a dated pricing ledger and an account-specific entitlement check for deployment decisions.