← Wiki
2026-11-12 concept structured-outputclassificationcalibrationroutinggeminigooglellmdecision-models

Gemini Decisions API (gemini-decision-1)

Definition

A Google endpoint that does not generate text. You send one shared input and a map of typed questions; the model scores all of them in a single forward pass and returns a calibrated probability per question. gemini-decision-1 is the only model it accepts. It is the same class of model as Jev in jev-system-one, from a bigger vendor, with a multimodal input.

Status of each claim below: verified means read on a Google page (URL in learned_from); vendor claim means Google says it and publishes no method in the pages read; channels only means not found at a primary source.

What the digest said, checked

Claim from the digest Result
Google released Gemini Decisions API, gemini-decision-1 Verified. Google blog, AI Studio docs and a model page all exist. Press coverage is dated 11 Nov 2026 (MarkTechPost URL); the Google blog page carried no date in the extract.
A separate endpoint for choosing, routing, classifying Verified. Google’s own list: tool selection, policy checks, model routing, context grading.
“Competitor of Jev” Channels only. The type names are the same as Jev’s (noul, choice, score), and so is the idea (calibrated probabilities, one parallel pass). None of the Google pages I read mention Jev or TypeSafe.

Shape of the API (verified, docs page)

Price, speed, claims

Where it overlaps Jev, where it does not

Gemini Decision 1 Jev (our notes)
Question types noul / choice / score Noul / Choice / Score
Output probabilities, 0 text tokens same
Price per MTok input $0.10 $0.042 (reported, see jev-system-one)
Latency 150-250 ms e2e (vendor) 70-500 ms (reported); 247 ms p50 in Mike’s 17-case run
Input text, image, audio, video, PDF text and image
Options per choice up to 255 weaker above 20 options (Laya card claim)
Weights closed, hosted closed, hosted
Local copy none Laya, Apache 2.0, measured 13.7 ms on M5 GPU

The decisive difference for us is the last row. Anything that must stay on the Mac (privacy-first products) still needs Laya or a similar open model; Google’s endpoint is a cloud call with the data leaving the machine. Its edge is audio, video and PDF in the same call, which none of our current Jev jobs needed.

Mike’s table in jev-system-one already lists a “Microsoft decision-1” lane on Foundry, so Google is at least the second large vendor with this primitive.

What we would test (not run)

Goal: does Gemini Decision 1 beat Jev 1.14 and Laya on our own cases, in Russian too?

  1. Build 60 to 100 labeled cases from jobs we already have: the destructive-action gate (rm -rf style), the agent-output watchdog, the intent router from the kitchen demo, the channel-digest filter (“worth posting or not”, in Russian), and the BroCheck image questions. Label by hand first, before any model runs.
  2. Run the same cases through Gemini Decision 1, hosted Jev and Laya-multilingual with identical question wording; keep Russian cases as a separate slice, because Laya failed there.
  3. Record accuracy against our label, the number wrong while confidence is 0.9 or higher (the metric that sank JSON-from-LLM in Mike’s run: 7 of 17), p50 latency and cost per 100 cases.
  4. Set the threshold on half the cases and check it on the other half; compare how often each model passes a case to a human.
  5. Add 10 adversarial inputs that argue for their own label (the docs’ own warning) and check none flips a gate.

Decision rule: adopt Google’s only if it cuts confidently-wrong cases without losing the Russian slice; otherwise keep Jev for hosted and Laya for local.

Learned from

Primary: the three Google pages in learned_from. The starting claim came from a Telegram digest of 12 Nov 2026. Nothing here was run by us.

Sources

Related