Gemini Decision 1 vs Jev

Gemini Decision 1 60

Model reading for gemini-decision-1 on the Gemini API's Decisions endpoint. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. No machine payment protocol (0). The pricing page lists $0.10 per million input tokens on the paid tier for every modality and no output charge, without a login (20). Free of charge on the free tier (20). A Google account and an AI Studio key come first (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Jev 30

No x402, MPP or L402 (0). Per-token price published without a login, $0.042 per million input tokens for Jev 1.14 and 1.13 with output free (20). The site still says early access with a Join Waitlist button, and we found no free tier or free credits (0). A person signs in at the console and waits for access before creating a key (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Gemini Decision 1 79

Model reading for gemini-decision-1 on the Gemini API's Decisions endpoint. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Released on 11 November 2026, the day of this check (30). Deprecations with earliest dates and no stated minimum notice (4 of 12). Shutdowns in the last 90 days kept to their table (4 of 8). Dated changelogs: google-genai 3.2.0's entry adds the Decisions API; the platform changelog wasn't re-read today (11 of 15). SDK replies not sampled (5 of 10). google-genai 3.2.0 tagged the same day with client.decisions.create; the JavaScript SDK is per Google's post (15). Runtimes stated on the platform (10). 30 + 4 + 4 + 11 + 5 + 15 + 10 = 79. The model is hours old, so these lines are the platform's habits more than this model's record.

Jev 66

Read for a closed model. Jev 1.14 became available on 14 October 2026 and jev-latest moved to it, and both SDKs released the same day (Python 0.7.5, TypeScript 0.7.0) (30). Model aliases and pinning advice exist, but the customer agreement still promises only commercially reasonable efforts to give advance notice of API changes, and the site terms allow changes without notice (5 of 12). Two model versions in seven weeks. The alias moved on release day with 1.13 still served by its versioned ID, which the docs describe ahead of time (4 of 8). Public SDK changelogs that call out breaking changes (Python 0.6.0 and 0.7.0, TypeScript 0.6.0 and 0.7.0). Issues are welcome but pull requests aren't accepted, and issue replies are unchecked because GitHub refuses our reader (7 of 15). Current SDKs in Python and TypeScript, now released together, Python 0.7.5 and TypeScript 0.7.0 tagged on 14 October (15, was 13 while TypeScript lagged at 0.6.0). The public repositories are mirrors published by a bot. Each has only a publish workflow and no public workflow runs the test suites (5 of 10).

Gemini Decision 1 70

Model reading for gemini-decision-1 on the Gemini API's Decisions endpoint. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Closed service with clear terms, SDKs Apache-2.0 (15). The pricing page states that free-tier content is used to improve products and paid-tier content isn't; abuse retention has no number (15 of 30). Deprecations table; the model page names no deprecation for this model (15 of 20). Data may be cached anywhere Google has facilities; no subprocessor list checked (5 of 20). Every benchmark, latency and cost comparison is Google's own, and the post gives charts without scores in its text. 15 + 15 + 15 + 5 = 50.

Jev 58

Closed model under a customer agreement, terms of use and an acceptable-use policy, with MIT SDKs (15). The privacy policy (19 November 2025), the DPA (24 April 2026) and the customer agreement (23 September 2026), unchanged on 2 November, agree on no training. None gives a retention period. The policy keeps data as long as reasonably necessary, and the agreement lets TypeSafe delete customer data after termination at its discretion. The privacy policy names Google Analytics (14 of 30). Version pinning is documented, but there's no deprecation policy, and the agreement's notice promise is commercially reasonable efforts (6 of 20). Services are hosted in the United States, per the privacy policy. The DPA points to a subprocessor list at trust.typesafe.ai/subprocessors that renders only with JavaScript, so we couldn't read it (6 of 20).

Gemini Decision 1 80

Model reading for gemini-decision-1 on the Gemini API's Decisions endpoint. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. No published machine-readable contract for the Decisions endpoint; the request and response types are generated and typed in google-genai 3.2.0, Apache-2.0 (10 of 25). llms.txt with Markdown twins on the platform (10). The guide and model page say what the endpoint is for and list what it doesn't do (no caching, Batch, Flex, Priority, function calling, structured outputs or text generation; no YouTube or gs:// sources; history only as text) (18 of 20). Fields carry stated rules: question keys match [A-Za-z0-9_-]+ up to 64 characters, 1 to 1,000 questions, 2 to 255 options or levels, option keys 1 to 128 characters, P(true) between 0.01 and 0.99, nesting to 100 levels (14 of 15). Python, JavaScript and REST examples, and errors documented as HTTP 400 with codes safety, prohibited_content, blocklist, image_safety and content_blocked (13 of 15). Dated SDK changelog and the platform's dated changelog (15). 10 + 10 + 18 + 14 + 13 + 15 = 80.

Jev 90

api.typesafe.ai now disallows ClaudeBot, Claude-Web and anthropic-ai in robots.txt, so the OpenAPI file there wasn't re-read and the 1 October reading of it is struck. The same OpenAPI 3.1 document (TypeSafe v0.2.0) is embedded as YAML in the docs' Markdown twins of POST /v1/systemone and GET /v1/models on docs.typesafe.ai, which allows us (25). llms.txt indexes 137 links, each page with a Markdown twin (10). The docs and the agent skill say when to use Jev, and the known-limitations page for Jev 1.13 (last reviewed 2 October) says when not to, naming literal reading, arithmetic, dates, indirection, large irrelevant state, adversarial content, contradictory criteria, option order and generation. Jev 1.14 has no such page yet (18 of 20). Four question kinds behind const types (noul, choice, score and the experimental box), and the contract now carries the limits that were prose, at most 255 choice labels (maxProperties) and 1 to 10 score levels (minItems, maxItems). State and criteria items stay free-form by design (14 of 15, was 12). curl and SDK examples on every page plus cookbooks. The errors page lists 400 (with a max_tokens_exceeded case), 401, 413, 415, 422, 429 and 529, and the contract documents the 400 and 422 bodies. The 429 and 529 bodies aren't shown (13 of 15, was 12). Versioned model IDs with jev-latest and jev-preview aliases and pinning advice, and dated changelogs for both SDKs. No changelog for the API or the model. Jev 1.14 appears only as a line on the models page (10 of 15).

Gemini Decision 1 40

Model reading for gemini-decision-1 on the Gemini API's Decisions endpoint. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Status page at aistudio.google.com/status with no readable components or history (10 of 20) and no readable incident record (5 of 30). Rate-limit tiers and spend limits published for the platform, but the public rate-limit page, read on 11 November, has no row for Decision 1 and sends you to AI Studio (5 of 15). Backoff guidance for 429 and 503 and SDK retries (15). No SLA (0). The guide and the model page, read on 11 November, state no launch stage; the endpoint is v1beta and the model has one version, so half, as Gemini 4 Carbon was read (5 of 10). 10 + 5 + 5 + 15 + 0 + 5 = 40.

Jev 48

Status page at status.typesafe.ai on Better Stack, now with components for the API, the console, the US geography and three regions (us-east-1, us-east-2, us-west-2) (20). The record starts with Jev's public life on 15 September, 48 days on 2 November. Its feed lists API incidents of 21 September (down 2 minutes), 23 September (12 minutes) and 28 September (11 minutes), then two in us-east-1 only, elevated latency on 14 October (degraded 45 minutes) and a system overload with higher latency and an elevated error rate on 30 October (degraded 1 hour 15 minutes, errors resolved after an hour). One region of three, so partial. Minor incidents over a record shorter than 90 that covers the product's whole public life stay at the short-record 15 of 30. The models page no longer publishes figures. Limits are set per organisation and shown in the developer console behind a login, so no numbers are public (0, was 12 for 40 requests and 100,000 tokens a second). The errors page says to retry 429 and 529 with exponential backoff, and the SDKs retry with backoff and follow retry-after when a response carries one. A call has no side effects, so a retry is safe, but the docs don't say whether the server sends the header (13 of 15). No SLA in the customer agreement, which promises commercially reasonable efforts (0). Early access with a waitlist (0).

Gemini Decision 1 45

Model reading for gemini-decision-1 on the Gemini API's Decisions endpoint. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Keys bound to a service account and restricted to the Gemini API, with no scopes and a token accepted in the URL (15 of 30, the platform's deduction). The pricing page, read on 11 November, says free-tier content is used to improve Google's products and paid-tier content isn't (10 of 20, the platform's reading). Abuse retention with no number (5 of 15). Request logs for billed projects are described for Generate Content; the Decisions guide says nothing on logging (10 of 15). security.txt and a reward programme, no certification naming the API (5 of 20). 15 + 10 + 5 + 10 + 5 = 45.

Jev 53

Read for a model API. A bearer API key from console.typesafe.ai/keys. We found no scopes, expiry or rotation in the docs, re-read on 2 November, and didn't check revocation. The Python SDK validates the key early and keeps it out of logged errors (18 of 30). The models page, the privacy policy (19 November 2025) and the customer agreement (23 September 2026) all say customer data isn't used for training. The DPA (24 April 2026) keeps personal data as long as necessary for the purpose, with no period, and zero retention is for enterprise customers through a support form (13 of 20). Jev's job is judging content that often comes from users. The known-limitations page lists adversarial content as a failure mode and says to write precise prompts and test edge cases. That's a written warning with no mitigation (10 of 15). Each response reports input and output tokens and carries a request ID. We found no usage or audit logs documented (6 of 15). typesafe.ai/.well-known/security.txt still answers 404, and no bug bounty or disclosure policy was found. The trust centre at trust.typesafe.ai renders only with JavaScript, so certifications are unchecked. The DPA commits to breach notice within 72 hours (6 of 20). OSV holds no advisory for either SDK.