Gemini
Google DeepMind's multimodal model family.
Gemini is Google's multimodal model line, available through the Gemini app and the Google AI developer APIs.
At a glance — Nano Banana Pro (Gemini 3 Pro Image)
- Cost
- $2.00 in · $12.00 out per 1M tokensMid-range
- Memory
- 131K tokens — about 200 pages
- Reads
- Text · Images
- Can do
- Use tools (agents)
- Structured output
- Thinking mode
- Reliability
- 100.00% uptime, last 24h
- Released
- Jun 18, 2026
Advanced details
- API model ID
google/gemini-3-pro-image- Max output
- 33K tokens
- Cached input
- $0.20 per 1M
- Tokenizer
- Gemini
Providers
The same model, hosted by different companies. OpenRouter picks one per request and falls back to the next if it fails.
| Provider | Input /1M | Output /1M | Cached /1M | Max output | Uptime 24h |
|---|---|---|---|---|---|
| Google AI Studio · global | $2.00 | $12.00 | $0.20 | 33K | 100.00% |
| Google · global | $2.00 | $12.00 | $0.20 | 33K | 99.45% |
Supported parameters
- include_reasoning
- max_tokens
- reasoning
- response_format
- seed
- stop
- structured_outputs
- temperature
- tool_choice
- tools
- top_p
Live from OpenRouter, refreshed hourly.
Official apps
Use it in
- Cursor
- Visual Studio Code· via Gemini Code Assist
- GitHub Copilot· in the model picker
- Continue· bring your own key
- Aider· bring your own key
- Devin Desktop· formerly Windsurf
- WebStorm· via JetBrains AI Assistant
- Kilo Code· bring your own key
- OpenCode· bring your own key
- OpenRouter· one API for every model
- OmniRoute· self-hosted gateway
Pairs well with
Skills
MCP Servers
Frameworks
Templates
Starter prompts
Copy one, fill in the brackets, and paste it into your tool.
Write a GEMINI.md for this project · context
Read this repository and write a GEMINI.md at its root, the context file Gemini CLI loads at the start of every session. Keep it brief: - How to run, test and build, with exact commands - Where the important code lives - Conventions and rules that are easy to miss - Things never to do in this repo Leave out anything the code already makes obvious.
Review my changes before I commit · debugging
Review the uncommitted changes in this repository as a careful senior engineer would. For each problem, give the file and line, what goes wrong, and a concrete scenario that triggers it. Focus on bugs, security and missing edge cases; skip style nitpicks. If you find nothing serious, say so plainly.
Sketch or screenshot to layout · design
I am attaching [a sketch / a screenshot]. Turn it into a responsive layout for [the page] using this project's components. Before writing code, describe the structure you see: sections, hierarchy, what repeats. Then build it mobile first. Call out anything the image does not show — hover states, empty states, errors — instead of making it up.
Map a codebase you just inherited · planning
I am new to this codebase. Read all of it, then give me: 1. What the app does, in three sentences 2. The main parts, and how a request flows through them 3. The five files I should read first, and why 4. Anything that looks risky, unfinished or inconsistent Cite a file path for every claim so I can check it.
Key info
- Pricing
- Freemium
- Platform
- Web · iOS · Android
- Category
- Models
- Best for
- Beginner
Guided walkthroughs
Related reading
- Fundamentals
Reviewing code you did not write
You are going to merge a lot of code you did not type. Reviewing it is a different skill from writing it, and it is the one that actually keeps a vibe-coded…
Intermediate - Context engineering
Why your AI keeps forgetting what you told it
Models have a context window, a fixed budget of text they can consider at once. Everything competes for it: your instructions, the files you opened, the erro…
Intermediate