Perplexity released pplx-decider-v1.1-27b (Apache-2.0, fine-tuned from Qwen3.8-27B) on Hugging Face. It returns typed, probability-calibrated answers instead of text. Overall Decision Index is 61.56 vs 56.4 for v1 and 57.9 for Jev, and it is served via the Perplexity Decisions API.
Key Takeaways
- ✓Overall Decision Index 61.56: +5.16 over v1 (56.4) and +3.66 over Jev (57.9) on the same Qwen3.8-27B backbone
- ✓Categories: Language 69.45, Retrieval 61.26, Tools 78.88, Knowledge 48.18 (still below Jev's 51.4)
- ✓Gains come mainly from lifting the causal mask on full-attention layers plus more training data incl. tasksource
- ✓Decision head is a BF16 [255, 5120] readout, not a full-vocab lm_head; ~49 GiB of weights on a CUDA GPU
- ✓Hosted via POST /v1/decisions with noul / choice / score questions, many per request (docs)

Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Perplexity's pplx-decider-v1.1-27b is an Apache-2.0 open-weights decision model fine-tuned from Qwen3.8-27B. Instead of generating text it outputs calibrated probabilities over the candidates you define, via a BF16 [255, 5120] readout head rather than a full-vocab lm_head. Versus v1, it lifts the causal mask on full-attention layers and trains on more data (including tasksource), raising the overall Decision Index from 56.4 to 61.56, ahead of Jev at 57.9 (Language 69.45, Retrieval 61.26, Tools 78.88, Knowledge 48.18; all vendor-reported). Self-hosting needs Python 3.12+ and a CUDA GPU for ~49 GiB of weights, using the bundled DecisionModel code to reproduce evaluated behavior. Alternatively call POST https://api.perplexity.ai/v1/decisions with a state and named noul/choice/score questions. Good fit for agent intent routing, RAG relevance checks, and rubric grading.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.