A purpose-built decision model for routing, policy checks and rubric scoring, separate from Google's generative Gemini models.
Google DeepMind released Gemini Decision 1 on 11 November 2026, and it can score up to 1,000 independent questions per request in 150 to 250 ms end to end, by Google's measure. It suits teams that route requests or check policy rules and want to branch on probabilities, not anything needing written output.
Checked 12 Nov against Google DeepMind's own pages.
| Job | Input | Output | Total |
|---|---|---|---|
| Summarise a 20-page PDF | $0.0030 | $0 | $0.0030 |
| Support reply | $0.0002 | $0 | $0.0002 |
| One coding agent run | $0.020 | $0 | $0.020 |
Budgets: 20-page PDF = 30k in / 1k out · Support reply = 2k in / 300 out · Coding agent run = 200k in / 20k out. Computed from the vendor's per-token prices at render time; cached-input discounts are not applied.
Paid tier: $0.10 per 1M input tokens and no output charge. Free tier: free of charge within rate limits. Caching, the Batch API, Flex and Priority inference are not available.
Gemini Decision 1 reads a shared input of up to 262,144 tokens and returns calibrated probabilities instead of text. Google DeepMind built it for the Decisions API, where yes/no, choice and rubric-score questions are answered in one forward pass, with a confidence value on every answer for routing and policy checks.
Reads
Writes
Typed questions, three answer shapes
A request mixes yes/no, choice (2 to 255 options) and score (ordered rubric) questions over the same input.
Confidence on every answer
Each answer carries a 0 to 1 confidence so code can run the action or escalate to a fallback.
Zero output tokens
The model generates no text, so output usage is always 0 and only input tokens are billed.
Multimodal shared input
Text, images, audio, video and PDFs can be combined in one input of up to 262,144 tokens.
Many questions in one pass
A single request carries up to 1,000 independent questions, scored in parallel and isolated from each other.
Low-latency scoring
Google reports 150 to 250 ms end to end, with latency staying nearly flat as questions are added (vendor-reported).
End-to-end latency per request, vendor-reported
Source: Google DeepMind launch post, 11 November 2026, read 12 November 2026| Measure | This model | Rank | Median |
|---|---|---|---|
| Blended price (3:1)$ per 1M tokens | $0.075/M | #6 / 103 | peer median $1.71/M |
Ranks are against GA models on Hokai that publish the same figure; ties share a rank.
| Model | Lab | Context | In / out per 1M | Reads and writes |
|---|---|---|---|---|
| 262K | $0.10 / $0 | text, image, audio, video, pdf → text | ||
| Amazon | -- | -- | text, image → text | |
| Shanghai AI Lab | -- | -- | text, image → text | |
| 1M | $0.30 / $2.50 | text, image, video, audio, pdf → text |
| Name | Endpoint | Auth |
|---|---|---|
| Gemini Developer API, Decisions endpoint (POST /v1beta/decisions) | https://aistudio.google.com/docs/decisions-api | API key (x-goog-api-key header) |
Ask narrow, single-purpose questions and combine the answers in code
Separate yes/no questions for is_damaged and needs_refund, joined by an if statement
Google's best practices say atomic checks compose better than one complex question.
Describe every choice option and score level
billing: Payments, invoices, and refunds.
Short descriptions make adjacent options clearly distinct, per Google's docs.
Yes/no probabilities stop at 0.99
Yes/no answers always fall between 0.01 and 0.99, so a check for a value above 0.99 never matches.
Workaround: Set thresholds inside the 0.01 to 0.99 range, for example 0.95.
Choice options are sorted alphabetically
The API sorts option keys in UTF-8 byte order before evaluating and breaks exact ties to the first key, so a catch-all named none_of_the_above sorts oddly.
Workaround: Name the catch-all option other and check the confidence before acting on the top option.
Input text can argue with the classifier
User-supplied text can argue for its own classification, which affects moderation and approval flows.
Workaround: Write explicit criteria, test with adversarial examples and keep a human or a second check on high-stakes actions.
Repeated input is billed in full
Context caching, Batch API, Flex and Priority inference are unavailable, so sending the same document in many requests costs the full input each time.
Workaround: Ask every question about one input in a single request and send only the fields the questions need.
gemini-decision-1 · 11 Nov 2026
Initial release with the Decisions API.
Google charges $0.10 per 1M input tokens on the paid tier of the Gemini API, the same for text, image, video, audio and PDF input. There is no output charge because the model produces zero output tokens, and the shared input is billed once per request however many questions follow. Caching, Batch, Flex and Priority pricing do not apply because the model does not support them.
It is proprietary and its weights are not downloadable. Google offers a free tier in the Gemini API at no charge, limited to 200 requests a minute, 50,000 tokens a minute and 10,000 requests a day. Open decision models such as Strands Decider 2B and Intern-Decision are the route for teams that want to self-host.
Google's pricing page says inputs are used to improve its products on the free tier and are not on the paid tier. The pages Hokai read state no retention period and do not describe how to opt out of retention. Input safety filters can also block a request, returning an HTTP 400 error with a code such as safety or blocklist.
Gemini Decision 1 returns a probability from a 262,144-token window and generates no text, while Hokai lists Gemini 3.5 Flash-Lite as a generative model with a 1,048,576-token window. Choose Decision 1 when the output is a closed-set answer your code branches on, and Flash-Lite when you need explanations, reasoning or tool calls. Google says Decision 1 is cheaper on its own benchmark suite but shows the figures only in charts.
The free tier allows 200 requests a minute and 50,000 tokens a minute. Tier 1 raises that to 1,500 requests and 1,000,000 tokens a minute, and Tiers 2 and 3 allow 5,000 and 15,000 requests a minute with unlimited daily requests. Each request may carry at most 1,000 questions.
Gemini Decision 1 (model code gemini-decision-1) is a specialised model from Google DeepMind, released on 11 November 2026 together with the Decisions API. Instead of writing an answer, it scores a fixed set of options in one forward pass and returns calibrated probabilities, so application code can branch on the result. It sits apart from the main Gemini line, for example Gemini 4 Carbon: Google's model page marks text generation, thinking, function calling and structured outputs as unsupported.
Google says the model leads its internal suite on agent routing, reasoning, ranking and multimodal understanding, with the lowest calibration error, but the launch post shows those results only as charts, so Hokai records no benchmark scores. Google also reports a median of 50 to 100 ms of model compute, or 150 to 250 ms end to end, all vendor-reported. OpenRouter, an independent listing, showed a 0.15 s latency for Google AI Studio when Hokai read it on 12 November 2026.
A request carries one shared input across text, images, audio, video and PDFs, plus a set of typed questions. A yes/no question returns a probability between 0.01 and 0.99, a choice question picks among 2 to 255 options, and a score question grades against an ordered rubric. Every answer includes a confidence value from 0 to 1, which code can use to send doubtful cases to a fallback or a person.
It is served only through the Decisions API on the Gemini Developer API (v1beta), with the Python and JavaScript SDKs or plain REST, and can be tried in Google AI Studio. Google names Gemini Notebook, which uses it to route queries, plus Stitch, Google Search and CC from Google Labs as internal users.
Do not use it for anything that needs written output, multi-step reasoning, tool calls, caching or batch discounts, and the Decisions API refuses YouTube and Cloud Storage links. A team that must run its own classifier should look at open models such as Strands Decider 2B, released under Apache 2.0, or Intern-Decision, which are both listed on Hokai as open decision models. A job that needs an explanation or a JSON object belongs on a generative model such as Gemini 3.5 Flash-Lite.
Google publishes no training cutoff, parameter count, architecture, system card or safety benchmark for this model on the pages Hokai read, and input safety filters can block a request with an HTTP 400 error.
Specifications on this page (context window, token prices, benchmark scores, licence) are read from Google DeepMind's own model card and documentation. The verdict is Hokai's reading of them, not the provider's claim.