Tool support requires the appropriate API integration; a supported tool is not automatically active in every chat.
Supported API features and tools
Multimodal understanding with text output
Function calling and structured outputs
Search grounding, Maps grounding, and URL context
Code execution and file search
Context caching and Batch API
Before you choose
No native image or audio generation; use a dedicated generation model.
The Live API is not supported by this model.
Large input capacity does not guarantee that every detail will be recovered correctly.
Stable-model access is restricted to prior Google API users; old preview IDs have separate retirement dates.
Extended thinking
Thinking is dynamic by default and cannot be disabled. The explicit thinking budget range is 128–32,768 tokens; -1 selects dynamic thinking. These budgets are not the same as Gemini 3 low/medium/high levels.
This page documents the stable API ID shown above, not an earlier preview mentioned in the launch article.
Gemini 2.5 uses thinkingBudget rather than Gemini 3 thinkingLevel; do not copy reasoning defaults between generations.
Tool execution, permissions, and validation belong to the application integrating the API. Always inspect citations and generated structured data.
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
Review a migration design
Provide the existing system and constraints before asking for a plan.
Review this database migration proposal against the current schema, traffic constraints, and rollback requirements I provide. Identify data-loss risks and incompatible assumptions. Produce a staged rollout with validation queries and explicit stop conditions. Separate verified constraints from questions for the engineering team.
Workflow 02
Compare conflicting specifications
Require evidence rather than an invented reconciliation.
Compare these two versions of our technical specification. List changed requirements, contradictions, and downstream test impacts, citing section headings in both documents. Do not silently choose a winner when the documents disagree. Finish with the decisions an owner must make before implementation can begin.
Workflow 03
Explain an algorithmic failure
Ask for falsifiable reasoning and focused tests.
Analyze the algorithm and failing examples below. State its intended invariant, trace where the supplied example violates it, and propose the smallest correction. Include complexity implications and three tests that would distinguish the fix from the old behavior. Do not rewrite unrelated parts of the program.
Developer reference
Google API pricing
These are Google API reference prices, not EZ Ai Assist subscription prices.
Prices are standard paid-tier API reference rates checked October 6, 2026. Free-tier terms and Batch, Flex, or Priority rates differ; verify the selected service tier before estimating spend.
Output pricing includes thinking tokens. Cached reads and cache storage are separate costs.
Search grounding includes 1,500 free requests per day; Maps includes 10,000 per day on the paid tier. Rates above apply after those allowances.
Above 200,000 input tokens, the long-context input, cache-read and output rates apply to that request.
Common questions
A few things worth knowing.
What is Gemini 2.5 Pro useful for?
Consider it for complex code analysis and long-document synthesis. Supply clear constraints and assess correctness, latency, and total usage on your own examples before making it a default.
How should I configure thinking?
Thinking is dynamic by default and cannot be disabled. The explicit thinking budget range is 128–32,768 tokens; -1 selects dynamic thinking. These budgets are not the same as Gemini 3 low/medium/high levels.
Can I send images, audio, or video?
The Google model card supports these inputs and text output. Upload and tool availability depend on your integration. This does not make the model an image generator, voice generator, or Live API model.
Is this model retired?
No. Google says the stable 2.5 models remain served, with access limited to users who actively used them before. Retired preview IDs are different. Check current provider and EZ Ai Assist availability independently.
Why are there two API price columns?
Requests above 200,000 input tokens use higher input, cached-input, and output rates. Cache storage and grounding can add charges. Measure full request usage rather than estimating from your visible prompt alone.
Does the large input limit guarantee a correct answer?
No. Keep evidence relevant, specify the required output, request source references, and check the result. The 1,048,576 input-token limit and 65,536 output-token limit are different constraints.
Are these the prices and limits of my EZ Ai Assist plan?
No. This guide separates Google’s direct API reference from EZ Ai Assist subscriptions. Use the pricing page for plans and the app for current model access. The example prompts are starting points, not guaranteed results.
Check the source
Official documentation
Specifications and API prices checked on . Example prompts and workflow advice are editorial guidance from EZ Ai Assist.