Tool support requires the appropriate API integration; a supported tool is not automatically active in every chat.
Supported API features and tools
Historical support: streaming and multimodal understanding
Historical support: function calling and structured outputs
Historical support: context caching and Batch API
Historical support: code execution, Google Search grounding, URL context, and file search
Before you choose
No native image or audio generation; these models return text.
Live API is not supported; audio input is not a real-time voice session.
Tool access, upload limits, and permissions depend on the integration. Validate outputs against the original evidence.
The original Gemini 3 Pro Preview model retired on March 9, 2026. The specifications here describe its historical behavior, not the model now reached through the old alias.
Computer use and Google Maps grounding were not supported by this model endpoint.
Historical prices were not verified from the reviewed official sources; the replacement model’s prices are not substituted.
Gemini thinking levels
lowhigh · default
The historical model supported low and high, with high as the default. Do not carry that two-level configuration into a replacement without reviewing its documentation. These controls were relative thinking levels, not a strict token budget.
Google announced the original model’s deprecation on February 26, 2026 and retired it on March 9. Its release notes say gemini-3-pro-preview now points to gemini-3.1-pro-preview.
The examples below are migration and comparison exercises for an available replacement. Prefer the explicit replacement ID; the old alias does not provide continued access to the original model.
Put it to work
Start with a more useful prompt.
Original examples from EZ Ai Assist. Adapt these to your task and the features available in your workspace.
Workflow 01
Create a migration evaluation
Turn archived examples into a repeatable acceptance set.
From these archived prompts and reviewed outputs, design a migration evaluation for an available replacement model. Group cases by required behavior, define a scoring rubric, and include edge cases for citations, formatting, and tool selection. Flag expectations that depend on retired features. Do not fabricate benchmark scores or call the old endpoint.
Workflow 02
Compare historical answers
Use saved results to identify changes that matter.
Compare the two saved answers and their source packet below. Identify factual differences, citation errors, omitted constraints, and formatting changes. Score only what the evidence supports and explain each deduction. Separate model-quality differences from different input settings. End with the cases that need a fresh human-reviewed test.
Workflow 03
Audit an old integration
Locate assumptions that need review before switching models.
Review the supplied integration configuration for assumptions tied to gemini-3-pro-preview. List the model ID, thinking settings, tools, schemas, and token limits that need checking against the replacement documentation. Propose a minimal migration checklist with rollback criteria. Do not invent unsupported settings or execute the migration.
Developer reference
Google API pricing
Google API reference pricing is not EZ Ai Assist subscription prices.
Historical API pricing was not verified from the reviewed official sources. Google’s current pricing table no longer lists the original retired model, so no numeric rates are shown here.
Do not use Gemini 3.1 Pro prices as historical Gemini 3 Pro prices. Consult the replacement guide for current API cost planning.
Retained workflows should be evaluated on an available model. The catalog route remains as a historical reference, not an availability guarantee.
Common questions
A few things worth knowing.
Can I still call gemini-3-pro-preview on Google’s API?
The original Gemini 3 Pro model retired March 9, 2026. Google’s release notes say gemini-3-pro-preview now points to gemini-3.1-pro-preview, so the old ID is not continued access to the original model. Prefer the explicit replacement ID and verify current routing and behavior before use.
What replacement does Google recommend?
Google’s lifecycle table recommends gemini-3.1-pro-preview. Follow the linked Gemini 3.1 Pro guide, then test your prompts and tools. Model replacement is not proof of identical outputs, defaults, latency, or cost.
Why is there no numeric price table?
The reviewed current official pricing page no longer lists the original retired model, and its historical rates were not verified. Showing the replacement’s rates or a zero value as Gemini 3 Pro pricing would be misleading.
Why retain this page after retirement?
It preserves a useful reference for people following older links or migrating an existing workflow. The lifecycle notice and replacement link explain what changed without silently redirecting to a different model.
Can I use these prompts in EZ Ai Assist?
Yes—adapt these original editorial examples to the inputs and controls available in your workspace. Share only material you are authorized to provide. They are starting points, not benchmarks or a promise of a particular result.
Does the input limit guarantee accurate long-document answers?
No. The 1,048,576-token input limit is capacity, not a recall guarantee. Organize sources with names and sections, request citations, and check them. The separate maximum output is 65,536 tokens; actual requests must also fit integration limits.
Are these the prices of my EZ Ai Assist plan?
No. Provider API token pricing and EZ Ai Assist subscriptions are separate. This historical guide does not show unverified numeric API rates. Use our pricing page for current plans and check the app for enabled models and controls.
Check the source
Official documentation
Specifications and API prices checked on . Example prompts and workflow advice are editorial guidance from EZ Ai Assist.