Gemini Decision 1 vs pplx-decider

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.

pplx-decider 75

Read as a hosted model API, the surface an agent would call. status.perplexity.com has an API component with uptime history and an incident feed. It has no Decisions component (20). The Decisions API was released on 1 October 2026 and its model changed to v1.2 on 16 October, so its record is 31 days long on 1 November. The feed, re-read on 1 November, has nothing after a Computer maintenance on 13 October, and its one incident since release, 'Elevated API errors and timeouts' on 9 October, says the API remained operational. A short clean record reads as 15 of 30 in this run (excaliclaw for 11 clean days, the OpenAI Decisions API for 26 days), so the 17 October 8 is brought into line (15). The guide states 10 requests a second per organisation shared by both models, and since 17 October publishes token limits for each, 15,000,000 a minute and 900,000,000 an hour for v1.2 (15). 429 carries Retry-After, successful responses carry x-ratelimit-* headers, the guide says to retry 5xx with backoff, and a decision has no side effects (15). The API FAQ, re-read on 1 November, says Perplexity does not guarantee uptime or recovery time (0). The guide carries no beta label, the OpenAPI description sits in the main openapi.json and both official SDKs have a Decisions method (10). 20 + 15 + 15 + 15 + 0 + 10 = 75.

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.

pplx-decider 68

Read for a model API. Project API keys are shown once, can be revoked, and can be generated and revoked through two documented endpoints with a rotation guide. No per-key scopes or spending limits were found (22 of 30). The API terms of service, readable on 17 October, say Perplexity will not use Customer Content to train, retrain or fine-tune any generative AI model, and the DPA says personal data will not train its models. The FAQ, rewritten since 17 October, now agrees with the Privacy and Security page that retention depends on the API, model and account and that zero data retention is not the default and needs an account-level configuration under a written agreement. No retention period for decision inputs is stated, the reading typesafe-jev got for the same gap (13 of 20). The endpoint judges text and images that often come from users. It returns only probabilities and never fetches a URL, and the v1.2 card says literal special tokens in user content are neutralised so user text cannot create readout markers, which is a property of the published inference code. The hosted docs have no guidance on adversarial input (6 of 15, up from 5). Responses carry x-request-id and token usage, and admins see usage and per-key invoice lines in the console. No audit log was found (10 of 15). security.txt on www.perplexity.ai is valid until 31 December 2027 and links a security page naming a public vulnerability disclosure programme, a private bug bounty on Bugcrowd, annual third-party penetration tests and a SOC 2 Type II report. The trust centre is script-drawn and was not read, and no public advisories for the API were found (17 of 20, up from 12). 22 + 13 + 6 + 10 + 17 = 68.

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.

pplx-decider 38

No x402, MPP or L402 in the guide, the reference, the pricing page or llms.txt, re-read on 17 October (0). The price is published without a login, $0.02 per million input tokens for v1.2 with free output and no per-request fee, the same as v1.1 (20). Usage is prepaid, the billing guide asked for a credit card on 9 October, and no free allowance was found (0). A person signs up in the console. The Stripe Projects route lets a coding agent provision a project, a key and credits from a terminal, but needs a person's Stripe account with a payment method and a $10 minimum purchase, per the 9 October check (5 of 20). The weights are free, and the hosted price is what this line grades. 25, unchanged. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.

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.

pplx-decider 65

Read for a hosted model with open weights. The v1.2 weights were committed on 16 October 2026 and the changelog carries the switch under October 2026 (30). The guide now states that a retired version's name routes to its replacement, announced in the changelog. No notice period is given, and the v1.1 and v1 names were moved to v1.2 on the day it shipped, 11 and 15 days after those versions were released (3 of 12, down from 5). Three 27B versions in 15 days, and each older pinned name is now answered by a model whose card says it reads requests differently and gives different answers to v1.1-style prompts. That is model churn, so the item moves from 5 of 8 to 2 of 8, the reading given to Clef-flash's context cut on an unchanged model ID. The changelog has several entries a month, and support runs through a community forum, a GitHub discussion repository and email. Replies were not sampled (10 of 15). The official Python SDK 0.44.0 and TypeScript SDK 0.39.0 carry Decisions methods from 15 October, with four releases each from 25 September to 15 October (14 of 15, up from 7). The v1.2 repository pins its requirements (torch 2.14.0, transformers 5.17.0) and has an Apache-2.0 pyproject.toml. It has no lock file or CI, and its card and release manifest still call the repository private (6 of 10, up from 5). No Decisions change since 16 October. The Hugging Face repository's only later commit, on 19 October, adds a tag to the card, and the guide and changelog read on 1 November announce no new version. 30 + 3 + 2 + 10 + 14 + 6 = 65.

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.

pplx-decider 89

An OpenAPI 3.1.0 description of POST /v1/decisions is in docs.perplexity.ai/openapi.json, listed in llms.txt and embedded in the reference page. The preview file read on 9 October now returns 404 (25). llms.txt indexes the guide, the reference and five Decisions cookbook pages, each with a Markdown twin (10). The guide says what a decision model is, where to use it in place of a chat model and what it does not do, and now says when to pick each model and when grouping questions hurts accuracy. No page lists languages (18 of 20, up from 16). Questions are a union discriminated on type, with 1 to 128 questions, 1 to 255 options, 1 to 10 levels and unknown fields rejected. model is a free string, and state and instructions accept any string, object or array by design (13 of 15). Examples in Python, TypeScript and curl with a response, and a status table for 400, 401, 404, 405, 413, 429 and 5xx. The guide says error.code changes type between errors (14 of 15). Versioned model IDs and a /v1 path, but a versioned name no longer pins a model. pplx-decider-v1.1-27b and pplx-decider-v1-27b now select v1.2, the guide says a retired name routes to its replacement, and the response echoes the name sent rather than the version that answered. The changelog dates entries by month only (9 of 15, down from 12). 89, down from 90.