{"slug": "gemini-3-6-flash-vs-3-5-flash-lite-api-migration-guide", "title": "Gemini 3.6 Flash vs 3.5 Flash-Lite: API Migration Guide", "summary": "Google released gemini-3.6-flash and gemini-3.5-flash-lite as generally available Gemini API models on July 21, 2026. Both support a 1-million-token context window, up to 64K output tokens, thinking, and built-in tools including Computer Use. The models deprecate temperature, top_p, and top_k, and require migration from numeric thinking budgets.", "body_md": "Google released `gemini-3.6-flash`\n\nand `gemini-3.5-flash-lite`\n\nas generally available Gemini API models on July 21, 2026. Both support a 1-million-token context window, up to 64K output tokens, thinking, and built-in tools including Computer Use. They solve different production jobs:\n\nDo not treat this as a model-ID-only upgrade. These models deprecate `temperature`\n\n, `top_p`\n\n, and `top_k`\n\n, reject conversations that end with a prefilled model turn, and continue the Gemini 3.x migration away from numeric thinking budgets. Remove incompatible fields, run both models through the same task fixtures, and route by workload before changing a production default.\n\nThis guide is for teams migrating a Gemini API application, coding agent, or automation system.\n\nIf you are evaluating other current models, compare the same fixtures with the [Kimi K3 rollout guide](https://indieseek.co/blogs/kimi-k3-api-context-cost-agent-rollout-guide/) and [Grok 4.5 coding-agent checklist](https://indieseek.co/blogs/grok-4-5-coding-agent-api-eval-cost-checklist/). If the model can execute repository commands, keep the [untrusted-repository sandbox gate](https://indieseek.co/blogs/ai-coding-agent-sandbox-untrusted-repo-checklist/) independent of model choice.\n\nThe new stable models add a useful two-tier route instead of one universal replacement:\n\n| Model | Default thinking | Input / 1M tokens | Output / 1M tokens | Best first test |\n|---|---|---|---|---|\n| Gemini 3.6 Flash | `medium` |\n$1.50 | $7.50 | Coding, multimodal analysis, tool-heavy planning |\n| Gemini 3.5 Flash-Lite | `minimal` |\n$0.30 | $2.50 | Extraction, classification, routing, cheap subagents |\n\nGoogle says 3.6 Flash uses fewer turns and tool calls than 3.5 Flash, makes fewer unwanted code edits, and improves agentic and spatial tasks. It now powers the Antigravity managed agent by default. Human evaluators still preferred earlier models for some visual styling, so keep screenshot review.\n\nFlash-Lite is the throughput route. Keep `minimal`\n\nfor bounded tasks; test `medium`\n\nor `high`\n\nfor autonomous planning and complex tools. Higher thinking can erase its latency and cost advantage.\n\nStart with this router, then test assumptions:\n\n| Workload | Start with | Promote when | Keep a fallback to |\n|---|---|---|---|\n| Repository diagnosis or multi-file implementation | 3.6 Flash | Acceptance rises without extra unwanted edits | Current coding model |\n| Screenshot-to-code or chart interpretation | 3.6 Flash | Visual fixtures and browser checks pass | Human-reviewed baseline |\n| Document extraction or strict JSON parsing | 3.5 Flash-Lite | Schema pass rate holds at target throughput | 3.6 Flash for hard cases |\n| Triage, labeling, or request routing | 3.5 Flash-Lite | False-route rate stays below threshold | Rules or current classifier |\n| Autonomous subagent with several tools | Flash-Lite at `medium` , then 3.6 Flash |\nTool completion improves enough to justify cost | One-step manual escalation |\n\nFor 100K input and 10K output tokens, listed-token cost is about `$0.225`\n\non 3.6 Flash and `$0.055`\n\non Flash-Lite. Compare cost per accepted task, not per request.\n\nStart with the smallest current Interactions API request:\n\n``` python\nfrom google import genai\n\nclient = genai.Client()\n\ninteraction = client.interactions.create(\n    model=\"gemini-3.6-flash\",\n    input=\"Inspect this failure and return the most likely cause.\",\n    system_instruction=\"Do not modify files. Return evidence before recommendations.\",\n)\n\nprint(interaction.output_text)\n```\n\nThen audit the production adapter:\n\n`gemini-3.6-flash`\n\nor `gemini-3.5-flash-lite`\n\nbehind a routing flag.`temperature`\n\n, `top_p`\n\n, and `top_k`\n\n; these fields are deprecated and ignored now, and future model generations will return HTTP 400.`thinking_budget`\n\nwith the string `thinking_level`\n\n; remove unsupported `candidate_count`\n\n.`model`\n\nrole, the request returns HTTP 400. Use `system_instruction`\n\nand structured outputs instead.`previous_interaction_id`\n\n. For `generateContent`\n\n, preserve required thought signatures and include `call_id`\n\nplus `name`\n\nin every function response.| Case | Probe | Pass condition |\n|---|---|---|\n| Contract | Send removed sampling fields and a prefilled model turn in disposable negative tests | Monitoring identifies the expected deprecation or HTTP 400 instead of silently corrupting output |\n| Quality | Run 20 representative tasks on the old route, 3.6 Flash, and Flash-Lite | Blind acceptance rate and unwanted-edit rate are recorded under one harness |\n| Tools | Exercise search, code execution, function calls, and one failure/retry path | Call IDs match, retries are bounded, and the agent stops on permission boundaries |\n| Structure | Validate extraction and refusal cases against the production JSON Schema | Invalid output never reaches downstream writes |\n| Cost | Replay short, long-context, and multi-turn tasks | Cost per accepted task and p95 latency stay within explicit budgets |\n| Rollback | Disable the route flag during a canary | New sessions return to the prior model without reusing incompatible conversation state |\n\nPromote one workload at a time: 5%, then 25%, then the target share. Stop on schema regressions, unexpected tool actions, budget breaches, or lower acceptance.\n\n`minimal`\n\n.Input remains $1.50 per million tokens while output falls from $9.00 to $7.50. Fewer turns and tool calls can matter more than the rate.\n\nIt handles lightweight web coding and subagents, but its strongest case is high-throughput bounded work. Start complex repository changes on 3.6 Flash and test fixtures before rerouting.\n\n`generateContent`\n\n?\nYes, but Google recommends the GA Interactions API for the latest models and features. On either surface, test deprecated fields, conversation state, thought signatures, and function responses.", "url": "https://wpnews.pro/news/gemini-3-6-flash-vs-3-5-flash-lite-api-migration-guide", "canonical_source": "https://dev.to/ahab_indieseek/gemini-36-flash-vs-35-flash-lite-api-migration-guide-7j9", "published_at": "2026-07-22 10:21:30+00:00", "updated_at": "2026-07-22 11:00:40.565416+00:00", "lang": "en", "topics": ["artificial-intelligence", "large-language-models", "ai-products", "developer-tools"], "entities": ["Google", "Gemini 3.6 Flash", "Gemini 3.5 Flash-Lite", "Antigravity"], "alternates": {"html": "https://wpnews.pro/news/gemini-3-6-flash-vs-3-5-flash-lite-api-migration-guide", "markdown": "https://wpnews.pro/news/gemini-3-6-flash-vs-3-5-flash-lite-api-migration-guide.md", "text": "https://wpnews.pro/news/gemini-3-6-flash-vs-3-5-flash-lite-api-migration-guide.txt", "jsonld": "https://wpnews.pro/news/gemini-3-6-flash-vs-3-5-flash-lite-api-migration-guide.jsonld"}}