
Google launches new Gemini Decisions API for better decision-making in AI applications
Google has introduced the Gemini Decisions API, powered by Gemini Decision 1, its first dedicated decision model. Instead of generating text responses, the model assigns probability scores to predefined options. Developers can evaluate up to 1,000 questions in a single request, with support for binary decisions, multiple-choice selection, and rubric-based scoring. The API also returns confidence scores to help determine when decisions can be automated or require further review.
Gemini Decision 1 supports text, images, audio, and video, with a context window of up to 256,000 tokens. Google reports latency of 150 to 250 milliseconds for contexts up to 16,000 tokens, with relatively stable performance across one to 100 questions. Pricing starts at $0.10 per million input tokens, with no output-token fees. Shared input is billed only once per request, and additional questions incur charges only for their instruction and criteria tokens.
Google already uses the technology in Gemini Notebook to route queries based on complexity, reportedly reducing latency for everyday queries by up to 40%. Google Search also uses it to detect adversarial behavior involving Model Context Protocol (MCP) tools. The API is available through Google AI Studio, with developer framework integrations rolling out and Google Cloud support planned for a later release.





Comments
"CC [Google's "family’s AI agent"] from Google Labs uses the Decisions API to pick the right emoji reaction from a palette of more than 200 options in a fraction of a second, so reactions appear instantly without adding latency." As Pichai said in 2018: "Technology doesn't solve humanity's problems." Nearly ten years later, he was still right.
This is an interesting direction for AI development. I work with AI tools myself, and I've often felt that generating an answer is one thing, but making a reliable decision is something else entirely. The speed and pricing look promising, especially for applications that need to process many requests. What concerns me is how developers will interpret those confidence scores. A 95% confidence level doesn't necessarily mean the decision is correct. I think this could be a very useful tool, as long as we don't forget the importance of human oversight.