Gemini Decision 1 vs pplx-decider-flash

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-flash 75

Read as a hosted model API, the same endpoint as pplx-decider. 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 Flash on 16 October, so the endpoint's 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 the API's 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, pplx-decider on the same feed), so the 17 October 8 is brought into line (15). The guide states 10 requests a second per organisation shared with the 27B model, and since 17 October publishes token limits for each model, 4,000,000 a minute and 240,000,000 an hour for Flash (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). No beta label in the guide, the reference or the OpenAPI description at version 1.0.0, 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-flash 68

Read for a model API, on the same account, keys and terms as pplx-decider. Project API keys are shown once, can be revoked, and can be generated and revoked through two documented endpoints, per the 9 October check. No per-key scopes or spending limits were found (22 of 30). The API terms say Perplexity will not use Customer Content to train 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. No retention period for decision inputs is stated, the reading pplx-decider and typesafe-jev got for the same gap (13 of 20). The endpoint returns only probabilities and never fetches a URL, and the card says literal special tokens in user content are neutralised in the published inference code. The hosted docs have no guidance on adversarial input (6 of 15). Responses carry x-request-id and token usage, and admins see usage per key in the console. No audit log was found (10 of 15). security.txt on www.perplexity.ai is valid until 31 December 2027, the security page names a public vulnerability disclosure programme, a private Bugcrowd bounty, annual penetration tests and SOC 2 Type II, and the trust centre is script-drawn and was not read (17 of 20). 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-flash 38

No x402, MPP or L402 in the guide, the reference, the pricing page or llms.txt (0). The price is published without a login, $0.01 per million input tokens with free output and no per-request fee (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 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. 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-flash 65

Read for a hosted model with open weights, on the decision-model lines (notice 0 to 12, churn 0 to 8) as pplx-decider. Flash v1.2 was committed on 16 October 2026 and announced in the changelog under October 2026, and Perplexity added a Q8_0 GGUF build in its own perplexity-ai/pplx-decider-flash-gguf-v1.2 repository on 18 October (30). The guide states that a retired version's name routes to its replacement, announced in the changelog, with no notice period, and on 16 October the 27B v1.1 and v1 names were moved to v1.2 the day it shipped (3 of 12). Flash has one version, and the pplx-decider-flash-latest alias can move. Between 17 October and 1 November grouped questions on the unchanged pplx-decider-flash-v1.2 name went from being answered together to being answered and billed one by one, so the same request can now get different answers. That is model churn, read as Clef-flash's context cut and pplx-decider's routed names were (2 of 8). 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 (v0.46.1, 23 October) and TypeScript SDK (v0.41.0, 22 October) carry Decisions methods (14 of 15). The repository pins its requirements (torch 2.14.0, transformers 5.17.0) and has an Apache-2.0 pyproject.toml, with no lock file or CI, and its card still calls the repository private (6 of 10). The weights repository's only later commit, on 19 October, adds a tag to the card. 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-flash 89

The same documentation as pplx-decider, which covers both models. An OpenAPI 3.1.0 description of POST /v1/decisions in docs.perplexity.ai/openapi.json, listed in llms.txt and embedded in the reference page (25). llms.txt with Markdown twins of the guide, the reference and five cookbook pages (10). The guide says what a decision model is and what it does not do, and when to pick Flash over the 27B model, with a per-model note on when grouping questions hurts. No page lists languages (18 of 20). 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 is free-form by design (13 of 15). Examples in Python, TypeScript and curl and a status table for 400, 401, 404, 405, 413, 429 and 5xx (14 of 15). A versioned name and an alias, a /v1 path and a changelog dated by month. The guide says a retired name routes to its replacement, and the response echoes the name sent rather than the version that answered (9 of 15). 89.