On November 12 Perplexity released pplx-decider-v1.3 (built on Qwen3.8-27B, about 26.1B parameters) and the distilled pplx-decider-flash-v1.3 (built on Qwen3.5-4B, about 4.5B). The weights are on Hugging Face under Apache 2.0, and both models are served through the Decisions API and OpenRouter. The new Locate feature extracts verbatim spans by label or instruction and returns character offsets. Perplexity says v1.3 averages 91.6% accuracy across 63 classification tasks, 6.54 points above its production classifiers.

Key Takeaways

  • ✓Two open-weight sizes: v1.3 has about 26.1B parameters (fine-tuned from Qwen3.8-27B) and Flash v1.3 about 4.5B (distilled onto Qwen3.5-4B), both Apache 2.0; running v1.3 locally in BF16 needs about 49 GiB of GPU memory
  • ✓New Locate feature: extracts verbatim spans by label or instruction with start and end character offsets and a score, covering NER, PII detection and extractive QA, and can share a request with classification and scoring questions
  • ✓Classification (vendor-reported): 91.6% mean accuracy across 63 classification tasks, 6.54 points above Perplexity's production classifiers; ahead of Jev 1.14 in all 7 domains, by up to 12.9 points in finance
  • ✓Retrieval and stability: nDCG@10 of 83.99 across 72 retrieval tasks, 1.81 above Qwen3-Reranker-8B; answers changed on only 0.27% of questions under input rewrites, versus 2.69% to 4.84% for Jev 1.14
  • ✓Where to get it: Hugging Face downloads, the Perplexity Decisions API, and OpenRouter, where both v1.3 models are free until November 19
Perplexity Open-Sources pplx-decider v1.3 Decision Models: New Locate Span Extraction, 91.6% Mean Accuracy Across 63 Classification Tasks for the 26B Model, Apache 2.0, Free on OpenRouter Until November 19
🖼️Official Media
Click to view high-res
🧭

Turn your technical choice into a development budget

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Background and the problem

Agent systems make many small decisions: whether to route a request to a large or small model, whether a tool output contains a prompt injection, whether a search result is relevant. Many teams ask a general LLM to generate a text answer, which is slow, costly and inconsistent. Perplexity's Decider series takes another route and returns a probability for each option in a single forward pass. This release follows v1.2 in October.

Architecture and how it works

Decider prunes a generative model's output layer into a decision head that keeps only option tokens such as A, B and C, and reads probabilities at a special marker. It supports yes/no, multiple-choice and ordered-score questions, several per request. v1.3 makes the full-attention layers bidirectional and isolates questions from each other, which makes answers more stable. Training runs in three stages (generalist full fine-tuning, domain LoRA, vision LoRA), then KL distillation into the 4B model. The new Locate feature uses a separate adapter and span head to extract verbatim spans, loaded only for Locate requests so decision quality is unaffected.

Benchmarks and measured results

All figures are vendor-reported: 91.6% mean accuracy across 63 classification tasks, 6.54 points above Perplexity's production classifiers; nDCG@10 of 83.99 across 72 retrieval tasks, ahead of Qwen3-Reranker-8B and Jev 1.14; 88.16% mean accuracy across 8 languages (Flash 86.50%, Jev 1.14 85.41%); an extraction average of 69.0 versus 43.3 for Liquid d1. On one million real Decisions API requests, agreement with frontier LLM judges was 93.98% (v1.2: 93.68%). No third-party reproduction yet.

Getting started

Local use needs Python 3.12+ and about 49 GiB of GPU memory. Pull the weights with snapshot_download, load them with Decider.from_pretrained from pplx_decider, and call decide() with a state and questions; fast=True enables packed batching. The v1.3 request format is not compatible with v1.1 or v1.2, so old prompt builders cannot be reused. Use Flash for high-volume, latency-sensitive routing and the 26B model where mistakes are costly, and tune thresholds on your own labeled set.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

Up NextIBM Releases LLMON, an LLM-Native Markup Language, With Granite 4.1 3B and 8B Preview Models: Reserved Tokens Separate Instructions From Data and Block 47% More Indirect Injection Attacks on OPI Than the Best Frontier Model Tested
Read Now→