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
Computer use (preview)
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.
Computer use is preview functionality and requires careful integration and validation.
Gemini thinking levels
minimal · defaultlowmediumhigh
Start with minimal for bounded extraction and classification. Increase the thinking level only if tests show a quality improvement. Minimal does not guarantee zero thinking; difficult inputs can still require some reasoning.
This page documents the stable API ID shown above, not an earlier preview mentioned in the launch article.
The model-specific card does not establish a training cutoff; no cutoff is inferred from its release date.
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
Extract invoice fields
Use a supplied invoice and a strict schema; keep missing fields visible.
Extract vendor, invoice number, issue date, currency, subtotal, tax, and total from the invoice I provide. Return one JSON object and a list of fields that were unreadable or absent. Do not infer missing amounts. Check whether the supplied subtotal plus tax matches the total and report any discrepancy.
Workflow 02
Route a support queue
Keep routing bounded to the categories you actually support.
Classify each support ticket below into billing, login, product question, or needs human review. Return the ticket ID, category, urgency, and one short evidence quote. Preserve the original IDs. If the ticket is ambiguous or asks for an account change, choose human review instead of inventing a resolution.
Workflow 03
Normalize a product feed
Specify what may change and what must remain literal.
Normalize these product records into the provided schema. Preserve SKUs, prices, currency codes, and quoted dimensions exactly. Standardize only category spelling and whitespace. Return valid rows separately from rows needing review, with the reason for each rejection. Do not add product claims or fill missing specifications.
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.
Google lists a 5,000-per-month Search allowance shared across Gemini 3.x models, with a separate shared Gemini 3 Maps allowance. One prompt can trigger multiple billable searches.
Common questions
A few things worth knowing.
What is Gemini 3.5 Flash-Lite useful for?
Consider it for document parsing and lightweight agent tasks. Supply clear constraints and assess correctness, latency, and total usage on your own examples before making it a default.
How should I configure thinking?
This Flash-Lite model supports minimal, low, medium, and high thinking levels, with minimal as the default. More thinking can increase response time and output-token cost; it is not a substitute for validation.
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.
How does this compare with the other Flash-Lite version?
Compared with 3.1 Flash-Lite, 3.5 adds preview computer-use support and has its own token rates. Compare extraction accuracy and total latency on the same inputs; a newer version is not automatically the cheapest.
What costs are additional to input and output tokens?
Cache storage and grounding can add charges beyond ordinary input/output tokens. Audio input has a separate rate where shown. Review the units and free allowances in the provider pricing page.
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.