The gemini decisions api is Google's new endpoint for one narrow job: making fast, bounded choices. Google launched it on 11 November 2026 with a new model, Gemini Decision 1 (gemini-decision-1). If you run automations for a small business, such as sorting support tickets, scoring leads or checking order photos, this is worth a look. Here's a research-based summary of what it does and how you might use it.
What it is
Most AI models write an answer word by word, and then your code has to parse it. Gemini Decision 1 doesn't write text at all. According to Google's announcement, it scores your candidate options in a single pass and returns probabilities and confidence scores.
You send one shared input (text, images, audio, video or PDFs, up to 256K tokens) plus up to 1,000 independent questions. There are three question types:
-
noul: a yes/no check that returns the probability the condition holds. -
choice: picks one of 2 to 255 options and returns a probability for each. -
score: grades the input against an ordered rubric.
Every answer includes a confidence score from 0 to 1, so your workflow can send unsure cases to a fallback or a person.
What it costs and how fast it is
Google lists it at $0.10 per 1M input tokens, with $0 for output tokens. The shared input is billed once per request, however many questions you ask. There's a no-cost tier in Google AI Studio for prototyping. Google reports 150-250 ms end-to-end latency for inputs up to 16K tokens.
MarkTechPost's write-up adds useful caveats: it's Google-hosted only (v1beta, google-genai SDK 3.2 or later), there's no prompt caching or batch option yet, and the benchmark figures are self-reported by Google.
A simple example: triaging a support message
Here's a sketch based on the request shape in Google's post. One message, three questions, one call:
from google import genai
client = genai.Client(http_options={"api_version": "v1beta"})
result = client.decisions.create(
model="gemini-decision-1",
input=[{"type": "text",
"text": "I was charged twice for my order. Please refund one."}],
questions={
"wants_refund": {
"type": "noul",
"instructions": "Is the customer asking for a refund?",
},
"team": {
"type": "choice",
"instructions": "Which team should handle this?",
"criteria": {
"billing": "Payments, refunds, invoices.",
"shipping": "Delivery, tracking, damaged parcels.",
"general": "Anything else.",
},
},
"urgency": {
"type": "score",
"instructions": "How urgent is this message?",
"criteria": ["Not urgent.", "Needs a reply today.", "Needs a reply now."],
},
},
)
Check the official docs for the exact response fields before you wire it into production.
Where it fits in a small-business workflow
- Lead scoring: ask "Is this a real buyer?" and "Which package fits?" on every form submission.
- Ticket routing: pick the right team and urgency before a person opens the inbox.
- Order checks: pair a customer photo with the order note and ask "Does the item look damaged?"
- Agent guardrails: a quick yes/no before an AI agent runs a risky tool.
A practical rule: act on high-confidence answers automatically, and send low-confidence ones to a human queue. That keeps the speed without trusting every guess.
Google says integrations are rolling out across OpenRouter, LangChain, Vercel, LiteLLM and others, so you may be able to call it from tools you already use.
For more research-based AI news for small businesses and creators, visit ainews.useaifix.com. If you'd like help setting up automations like this, see useaifix.com.
Top comments (0)