Perplexity Releases pplx-decider, a 27B Open Model That Replaces Label Parsing
Perplexity shipped an open-weight 27B decision model and a hosted API that returns calibrated probabilities over your options instead of free text.
- Perplexity launched a Decisions API that returns probability distributions instead of text
- Powered by pplx-decider-v1-27b, a Qwen3.8-27B fine-tune released open-weight under Apache 2.0
- Priced at $0.04 per million input tokens with output free; 262k context window
- Three question types: noul (yes/no), choice (pick one), score (rubric level)
- Scores 85.71% across 11 benchmarks, versus 84.51% for Jev and 74.76% for base Qwen
- Strongest on RAGTruth, TabFact, and classification; weaker on commonsense reasoning
Perplexity releases a 27B model for fixed-choice decisions
Perplexity has released pplx-decider-v1-27b, a model that maps text, structured data, or images to probabilities over developer-defined answers. The company published the weights under Apache 2.0 and launched a hosted Decisions API priced at $0.04 per million input tokens, with output unbilled.
The model targets workflows that ask a chat model for a label and then parse its response. Classification, routing, moderation, and rubric-based grading can use numeric probabilities, explicit answer sets, and application-defined thresholds.
A fixed answer space
The API receives content in a state field and evaluates it against one or more named questions. The state can contain text, JSON, or images encoded as base64 data URLs. The API supports three question types:
noul: Evaluates a yes-or-no question and returns the probability of yes from 0 to 1. For an exhaustive binary decision, the probability of no is the complement.choice: Selects among developer-defined options and returns each option’s probability along with the leading choice.score: Evaluates an ordered rubric and returns a probability-weighted expected level.
A single request can apply several questions to the same state. A support request, for example, could be classified by destination team, checked for escalation, and scored for severity without resending the underlying text in separate calls.
The repository’s inference helper exposes the same pattern for local use:
from inference import Decider
model = Decider.from_pretrained("perplexity-ai/pplx-decider-v1-27b")
result = model.predict(
"My Stripe integration keeps failing. Please help ASAP.",
{
"type": "choice",
"instructions": "Which team should handle this request?",
"criteria": {
"billing": "Charges and refunds",
"technical_support": "Integration errors",
"sales": "Questions about buying a product",
},
},
)
print(result)This story is for Pro members
You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.