What changed
On 11 November 2026 Google launched Gemini Decision 1 (gemini-decision-1) through its Gemini Decisions API. Instead of generating prose, it scores up to 1,000 independent yes/no, categorical-choice and rubric questions against one shared multimodal input of up to 262,144 tokens. It returns probabilities and confidence scores. Supported inputs include text, images, audio, video and PDFs. The paid list price is $0.10 per million input tokens, with zero generated-output tokens billed; the free tier has separate data-use terms.
Why it matters
Agents often need a small decision—whether to call a tool, which specialist model to route to, or whether a document passes a check—not a verbose completion. A bounded API can reduce parsing and token overhead. Google's multimodal support and 1,000-question cap extend this pattern beyond text-only routing. But confidence scores require calibration against the application's own labelled cases, and low token pricing does not remove engineering, privacy or failure-handling costs.
One shared input, many independent checks
The API accepts a map of up to 1,000 questions over a shared input, returning typed outputs: noul (yes/no probability), choice among fixed options, or score against an ordered rubric. Questions are evaluated independently and cannot inspect one another's answers. The shared input is billed once, while each question adds instruction and criteria tokens.
Pricing and performance claims
Google's official pricing lists $0.10 per million paid input tokens, no output tokens, and no context caching or Batch API support. Google reports 150–250ms end-to-end latency, but its published low-latency measurements concern shorter contexts and smaller question counts than the maximum request. Real deployments should benchmark tail latency and calibration.
Integration boundary is a beta endpoint
Google's developer guide uses the Gemini Developer API v1beta endpoint and google-genai SDK version 3.2 or later. Developers must construct typed questions and handle probabilities, not treat the API as a replacement for arbitrary chat or free-form generation. Free-tier inputs can be used to improve Google's products, while paid-tier terms differ.
How it compares with the existing decision-model category
BTN already covers OpenAI's Decisions API in dossier #353. Google's announcement is distinct because of the multimodal input support and larger per-call question cap. Independent developer Simon Willison tested video input and observed non-extreme probabilities in a simple example. That is useful implementation evidence, not a comprehensive accuracy benchmark.