Perplexity · Provider documented
Perplexity Decider v1 27B
A decision model with downloadable Apache 2.0 model files and a dedicated online API. It accepts text and images and gives confidence scores for fixed answers. The provider’s tests are not comparable independent results, and its launch date is not confirmed here.
First reviewed 2026-10-02 · Checked 2026-10-15. The launch date has not been confirmed.
We still need comparable independent tests. You can compare the confirmed features and limits below, but we cannot yet give this version an Agent Fit or Practical Value rating. Test it on records with known answers, including cases that should go to a person.
What you can use today
Token prices measure the small pieces of text the model reads or produces. Capacity is the amount the service accepts in a request; check the limits below for any fallback to another model. A dash means the rate is unverified.
Exact provider API ID: pplx-decider-v1-27b. The dedicated Decisions API accepts text, JSON and images and supports 1–128 named questions in a request. It returns typed probabilities; no chat tool-calling interface or adjustable reasoning-effort sweep is established.
Public documentation accepts any Perplexity API key. This review made no private-key inference request.
The Decisions API accepts fewer than 262,144 total input tokens, including state, images and all questions; this is an input cap, not a chat prompt-plus-output context allowance.
Output: Yes/no probabilities, bounded choices and rubric scores. Compare decision models, limits and input costs ↗
Perplexity charges $0.04 per million input tokens, using the count returned with each answer. Answers are free, with no extra fee per request. Background information, all questions and images count as input. Caching is not confirmed. Use actual billed usage and the model named in each response to check your estimate.
Provider release and specifications ↗
Check availability and plans ↗
Test it before switching
Give each model the same examples, tools and definition of success. Record correct outcomes, response time, retries and total cost. Check whether confidence scores match the answers you can verify.
Compare caching and long-context costs ↗