Development ·
Gemini adds a multimodal fixed-choice decision API
Google released a dedicated endpoint for scoring predefined choices over shared multimodal input.
Why it matters
Applications can separate bounded classification from free-form generation and reuse input across many independent questions.
What to watch
Independent calibration evaluations, production error rates and behavior on long or ambiguous inputs.
Still uncertain. Probability calibration, workload latency and useful decision thresholds require task-specific testing. No API request was run here.
Impact assessment reviewed 2026-11-13.
- Who it helps
- Developers building bounded classification or review steps
- Availability
- Google announced gemini-decision-1 on November 11 in AI Studio and the Developer API. Listed price is $0.10 per million input tokens, with no output-token charge.
Questions are independent
A request can ask up to 1,000 questions about shared input. Each question must stand alone: it cannot use another question’s answer. Application code must handle dependent decisions.
A score still needs validation
The API returns fixed-choice scores without explanations or tool calls. Test thresholds against labeled examples and route ambiguous cases for review. Vendor latency figures do not guarantee performance at maximum input size.
Decisions API documentation ↗Gemini Decisions API announcement ↗
A small independent example
Simon Willison published a four-question video example and its returned probabilities on November 11. It illustrates the output shape; one video cannot establish reliable confidence calibration.
What you can do
- Read the primary description and its stated limits before planning an evaluation. Open reference ↗
Where the evidence stops
Documentation checked November 13. No API call, calibration study or production routing test performed.
Sources read. Public source text checked November 13, 2026 UTC. No third-party project or full workflow executed.
Sources & further reading
Web · official
Gemini Decisions API announcement ↗
November 11 announcement read; pricing and latency are vendor statements.
Google · page checked 2026-11-13 · Published 2026-11-11
Web · official
Decisions API documentation ↗
Input limits, independent questions and unsupported features read. No API request sent.
Google · page checked 2026-11-13
Reddit · discussion
Decisions API discussion ↗
Original post and three replies read. Dates were relative and engagement counts unavailable.
u/javimbuilds · page checked 2026-11-13
More sources reviewed (2)
Hacker News · discussion
Decisions API discussion ↗
First five commenters inspected: eminence32, janalsncm, computably, orbis-tertius and reexpressionist. Calibration concerns are discussion, not measured accuracy.
Hacker News · page checked 2026-11-13
157 comments · observed 2026-11-13 07:01 UTC
Web · demonstration
A video classification example ↗
November 11 example shows four questions and returned probabilities for one video. This is a creator-reported run, not a calibration study.
Simon Willison · page checked 2026-11-13 · Published 2026-11-11
Coverage note: Documentation checked November 13. No API call, calibration study or production routing test performed.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
- · Added to Current
2026-11-11: Google released a dedicated endpoint for scoring predefined choices over shared multimodal input.
Assessment: Applications can separate bounded classification from free-form generation and reuse input across many independent questions.