Google Launches Gemini Decisions API for Multimodal Evaluation
Google launched the Gemini Decisions API on November 11, 2026, enabling developers to evaluate up to 1,000 multimodal questions-spanning text, images, audio, video, and PDFs-in a single batch call. The API, built on the Gemini Decision 1 model, supports yes/no, multiple-choice, and rubric-based scoring with calibrated confidence scores, eliminating the need for separate preprocessing pipelines for each media type. Pricing, benchmarks, and latency details remain undisclosed.


Short answer: Google launched the Gemini Decisions API on November 11, 2026, enabling developers to evaluate up to 1,000 multimodal questions-spanning text, images, audio, video, and PDFs-in a single batch call. The API, built on the Gemini Decision 1 model, supports yes/no, multiple-choice, and rubric-based scoring with calibrated confidence scores, eliminating the need for separate preprocessing pipelines for each media type. Pricing, benchmarks, and latency details remain undisclosed.
Google Gemini Decisions API Launch
Google just dropped the Gemini Decisions API, a fresh developer interface running on their Gemini Decision 1 model. It can chew through up to a thousand evaluation questions in one go, handling text, images, audio, video, and PDFs all at once. The news broke on the Google AI Blog back on November 11, 2026, courtesy of product manager Min Choi and principal scientist Felix Yu from Google DeepMind.
Supported Decision Task Types
The API takes yes-or-no questions, multiple-choice picks, and rubric-based scoring tasks. The big deal here is that it ingests all those different media types without forcing you to build separate preprocessing pipes for each one. That’s a real shift from the usual grind where developers have to duct-tape separate vision, audio, and language models together just to get a multimodal judgment system working.
For teams building AI apps, the value proposition comes down to throughput and calibration. Being able to fire off a batch of a thousand distinct decision prompts-each maybe looking at different media-and get back calibrated confidence scores in a single network round trip cuts out a ton of orchestration headache. When we say calibration, we mean the model’s reported confidence actually matches its real-world accuracy. That’s a tough nut to crack when you’re chaining a bunch of specialized models together.
Consolidate Multimodal Decision Pipelines
Developers tackling content moderation, document review, media analysis, or automated grading can now swap out those multi-stage pipelines for a single API call. Picture a content safety team: they could run a queue of mixed media posts against a consistent policy rubric in one batch. No more routing images to a vision classifier, audio to a speech model, and text to an LLM before stitching the results back together. The latency savings stack up fast at scale, and having unified calibration makes threshold tuning way simpler.
It also supports rubric scoring, which lets you get more nuanced than simple binary or categorical outputs. A rubric might define a five-point scale for factual consistency, tone, or visual quality, and the model hands back a score plus a calibrated confidence interval. That granularity matters when downstream systems need to flag uncertain calls for human review.
Missing Benchmarks Architecture Pricing
Google hasn’t published benchmark comparisons against other approaches, nor have they spilled the beans on the model’s architecture, training data, or pricing tiers. The blog post talks a big game on speed and calibration but stays quiet on actual latency figures, token limits per request, or where it’s available. Devs wanting early access will just have to keep an eye on the Google DeepMind and Google Cloud channels for docs and sign-up info.
If you’re evaluating whether to adopt this, the first move is spotting existing multimodal decision pipelines that could collapse into a single batch call. Prototyping a side-by-side comparison against your current multi-model workflows will show you if the calibration quality and latency actually hold up in production. Teams should also prep for the operational shift of managing one calibrated confidence score per decision instead of reconciling disparate metrics from separate models.
This release mirrors a broader industry push toward unified multimodal models that natively handle heterogeneous inputs instead of leaning on ensemble architectures. As these models mature, the engineering focus shifts from plumbing disparate components to designing solid evaluation rubrics and calibration-aware decision thresholds. Google stepping in with a dedicated decisions API signals they see calibrated judgment as its own product category, separate from general-purpose generation.
Frequently asked questions
What is the Gemini Decisions API and when was it announced?
The Gemini Decisions API is a developer interface running on Google's Gemini Decision 1 model that processes up to 1,000 multimodal evaluation questions per batch. It was announced on the Google AI Blog on November 11, 2026, by product manager Min Choi and principal scientist Felix Yu from Google DeepMind.
What media types can the Gemini Decisions API evaluate simultaneously?
The API accepts text, images, audio, video, and PDFs in a single request without requiring separate preprocessing pipelines for each modality. This unified input handling replaces the traditional approach of stitching together specialized vision, audio, and language models.
What types of evaluation tasks does the API support?
The API handles yes-or-no questions, multiple-choice selections, and rubric-based scoring tasks. Rubrics can define multi-point scales for criteria like factual consistency, tone, or visual quality, returning both a score and a calibrated confidence interval for each decision.
How does calibrated confidence improve multimodal decision workflows?
Calibration means the model's reported confidence matches its real-world accuracy. This simplifies threshold tuning for human-review escalation and eliminates the complexity of reconciling disparate confidence metrics from separate models in traditional multi-stage pipelines.
Where can developers find documentation and early access information?
Google has not yet published detailed documentation, pricing, latency figures, token limits, or regional availability. Developers should monitor Google DeepMind and Google Cloud channels for future documentation releases and sign-up opportunities.
Source: Google AI Blog
Related posts

OpenAI Launches ChatGPT Wallet for Agent Payments
OpenAI launched ChatGPT Wallet on November 13, 2026, enabling AI agents to complete purchases for ChatGPT Pro subscribers in the US. Built with American Express, Mastercard, and Visa, the system tokenizes card details so merchants never see real credentials. Users approve each transaction via biometrics after reviewing items, totals, and the selected card. OpenAI is rolling out access narrowly to refine compatibility with existing checkout and fraud-prevention systems.

Nvidia CEO Jensen Huang Resigns Amid China Deal Scrutiny
Nvidia CEO Jensen Huang resigned on November 12, 2026, amid growing scrutiny over the company's dealings in China and potential export control violations. The departure triggers congressional investigations into whether U.S. officials overlooked arrangements that may have bypassed sanctions. Huang's exit creates leadership uncertainty for the dominant AI chip supplier, raising concerns about supply chain stability and regulatory risks for the broader AI industry dependent on Nvidia har

FAA Expands AI Traffic Tool Nationwide After DC Trial
The FAA has deployed its $875 million SMART system to all 22 traffic control centers after a September trial in the Washington region. The platform analyzes weather, flight paths, and staffing to recommend routing changes. The trial rerouted 180 flights, saving 10 minutes and 80 gallons of fuel per flight. Controllers retain final authority, and a Washington team reviews suggestions before they reach facilities. The controllers' union says it was excluded from design and testing.