Perplexity Open-Sources a 27B Decision Model

October 1, 2026
Diagram of the decision flow: a state with a question and fixed options goes into pplx-decider-v1-27b, which returns a typed answer with probabilities, such as yes/no, a probability for each option, or a rubric score

On October 1, 2026, Perplexity opened a Decisions API and released the model behind it, pplx-decider-v1-27b, as open weights under Apache 2.0. It reads text, JSON or images and answers yes/no, multiple-choice and scored questions with a probability for each option, without generating text, which makes it a decision model. It's fine-tuned from Qwen3.8-27B.

Why it matters

When an agent decides where to route a request or whether to retry, that's a classification problem, and a typed decision model handles it more cheaply and with bounded outputs than a general language model does. Perplexity's docs price this one at $0.04 per million input tokens with free output. AI Weekly reports that Jev is listed at $0.042, so the two cost about the same, and Perplexity's weights are open.

The headline score needs context. Perplexity's model card reports an overall 85.71% on an 11-task panel, against 84.51% for Jev. The panel is Perplexity's own and was measured through the Perplexity API. Jev scored higher on some individual tasks, and on JevBench public hard the model card lists 73.27% for Jev and 70.30% for Perplexity's model. A 1.2-point average difference on a vendor's panel doesn't tell you which model is better on your data. That's why we measure candidates on a client's own labeled examples, as in our Jev and Laya comparison, and fine-tune the one that fits. See the decision models page for the full set of measurements.

Key technical notes

  • 27B parameters, Apache 2.0, with a 262,144-token context window. The Decisions API accepts images in the state alongside text, per the docs.
  • Choice questions take up to 255 options, and the model returns a probability for each.
  • The evaluation covers 11 tasks and 7,210 samples. Perplexity reports 85.71% for its model, 84.51% for Jev and 74.76% for the Qwen3.8-27B base model.
  • The API allows 10 requests per second per organization. Latency is about 2 seconds for a few hundred tokens and about 23 seconds near the input limit, which is slower than the small decision models released the same day.
  • Models of this class return a probability, but whether that probability is calibrated is a separate question. We tested it for Jev in Can you trust Jev's confidence?.

Sources