Skip to main content
Perplexity AI's new Decider v1.3 interface, showing "Locate" feature and "91.6% Accuracy" metric.

Editorial illustration for Perplexity Releases Decider v1.3 With Locate, Self-Reported 91.6% Accuracy

Perplexity Decider v1.3 Hits 91.6% Accuracy

• 4 min read

Perplexity put out two new models on Hugging Face this week: pplx-decider-v1.3 and a smaller sibling, pplx-decider-flash-v1.3. Both belong to the company's Decider family, open-weight models that don't generate text at all. Instead they take a question with labeled options and return a probability for each one, a format borrowed from TypeSafe's Jev models. The big model runs on Qwen3.8-27B, the Flash version on Qwen3.5-4B, and Hugging Face lists them at 26B and 5B parameters respectively.

The headline addition in v1.3 is Locate, a feature that pulls exact text spans out of an input based on type or instruction rather than just scoring yes/no or multiple-choice questions. Weights are released under Apache 2.0, and both models are already live in Perplexity's Decisions API and on OpenRouter. Deployment needs a CUDA GPU with roughly 49 GiB of BF16 memory for the full model or about 8.5 GiB for Flash, with no quantized builds available yet.

Perplexity's own benchmarks claim the new versions beat Jev 1.14 across most tasks, though the numbers come with some rough edges worth a closer look.

Perplexity has released pplx-decider-v1.3 and pplx-decider-flash-v1.3, the latest versions of its open-weight decision models. Perplexity Decider v1.3 is a decision model that returns probabilities, not generated text. It answers yes/no, multiple-choice and score questions about a text or image input.

Why this matters

Perplexity is betting that a lot of agent plumbing doesn't need a chatbot at all, just a model that scores probabilities and hands back exact text spans. Locate is the tell here: if a decision model can pull the right substring from a contract or a product page without hallucinating around it, that's a cheaper, more auditable replacement for a bunch of regex-and-LLM glue code teams are running today. For builders, the Apache 2.0 weights on Hugging Face matter more than the headline number. You can actually test the 91.6% claim against your own classification tasks instead of trusting a vendor benchmark.

We'd treat the self-reported figures as a starting point, not a verdict. "6.54 points above production classifiers" and "up to 12.9 points in finance" are Perplexity's own comparisons, against its own baselines, on its own task set. That's worth watching once independent evals show up, especially on domain classification where the gaps are largest.

If Locate holds up outside Perplexity's test suite, it's a genuinely useful primitive for retrieval pipelines. If it doesn't, it's another benchmark that reads better than it runs.

Common Questions Answered

What is the key difference between Perplexity's Decider v1.3 models and traditional text-generating language models?

Perplexity's Decider v1.3 models do not generate text at all. Instead, they take a question with labeled options and return probability scores for each option, making them decision-focused models rather than generative models. This format was borrowed from TypeSafe's Jev models and is designed for specific classification and scoring tasks.

What are the parameter sizes and base models for pplx-decider-v1.3 and pplx-decider-flash-v1.3?

The pplx-decider-v1.3 (the larger model) runs on Qwen 3.8-27B with 26B parameters, while the pplx-decider-flash-v1.3 (the smaller sibling) runs on Qwen 3.5-4B with 5B parameters. Both models are available as open-weight models on Hugging Face with Apache 2.0 licensing.

How does the Locate feature in Decider v1.3 improve upon traditional LLM-based approaches for text extraction?

Locate allows the decision model to pull exact text spans from documents like contracts or product pages without hallucinating around the content. This makes it a cheaper and more auditable replacement for the regex-and-LLM glue code that teams currently use, providing more reliable and verifiable results for agent-based applications.

What types of questions can Perplexity's Decider v1.3 answer according to the self-reported accuracy metrics?

Decider v1.3 can answer yes/no questions, multiple-choice questions, and score questions about text or image inputs, with Perplexity self-reporting a 91.6% accuracy rate. The model returns probability distributions across the labeled options rather than generating free-form text responses.

Why does Perplexity believe decision models are important for AI agent development?

Perplexity is betting that much of agent infrastructure doesn't require a full chatbot but rather just a model that can score probabilities and extract exact text spans reliably. This approach reduces hallucination risks, improves auditability, and provides a more cost-effective solution for building agent-based systems compared to traditional LLM-based approaches.

LIVE22:45OpenAI board member warns AI takeover of society could be months away