Perplexity
•
Decider V1.2
•
Released 
October 2026

Perplexity
Decider V1.2

Perplexity's 27B decision model returns typed probabilities for classification, routing and rubric grading instead of generated text.

Modality:
Text
model ID
perplexity/pplx-decider-v1.2

Output Speed *

N/A
tok/s

Intelligence Index *

N/A
/ 100

Context Window *

262144
tokens

Input price

0.06
Anytoken

Output price

0
Anytoken
Typed Probabilities Instead of Text: Perplexity's 27B Decision Model Decider V1.2 (pplx-decider-v1.2) is Perplexity's 27B decision model. It is built on a Qwen3.8-27B backbone and released under Apache 2.0. It does not write text. It reads text, JSON or images as state and returns probabilities for yes/no, multiple-choice or rubric-scored questions, so your code can threshold the numbers. It is the larger default in the Decider family, above Decider Flash V1.2. It suits routing, moderation, claim verification and rubric grading, especially when several questions about one input must be answered in a single pass. Add Decider V1.2 to your routing pipeline

Performance

Joint Questions, One Pass: Where Decider V1.2 Earns Its Place

Decider V1.2 reads the state and every question in one sequence, so answering several questions about the same input costs about as much as answering one. Perplexity reports a Decision Index score of 68.09 for this joint configuration, up from 62.30 for v1.1. Perplexity runs that benchmark itself and added official training splits to v1.2's training data, so treat the gain as directional. In production, multi-label triage such as team, blocked status and frustration score needs one request instead of several.

Benchmarks

ClaimBench: Near-Perfect Claim Checking Against 10-K Excerpts

Vals AI's ClaimBench tests 1,960 claims against 10-K excerpts, labeled supported, contradicted or unsupported. Decider V1.2 scored 99.69%. It ranked second among decision models on the October 23, 2026 leaderboard, behind d1-ultra. It scored 98.5% on subtle contradictions, the hardest category. Reported latency was 1.23 seconds per claim, against 5.06 for Claude Haiku 5.5. Escalating low-confidence claims to Haiku 5.5 reached 99.85% accuracy. These are single-domain finance results, so validate thresholds on your own labeled data.

Output Speed

*
N/A
tok/s

Intelligence Index

*
N/A
/ 100

MMLU *

Broad world knowledge and problem-solving
0
%

GPQA *

PhD-level scientific reasoning across physics, biology, chemistry.
0
%

HLE *

Adherence to multi-step structured instructions.
0
%

LiveCodeBench *

Tool-calling reliability in long agentic loops.
0
%

Technical Specifications

What the model supports

Decider V1.2 accepts text, JSON and images and returns typed probabilities rather than tokens. The Perplexity API documents a 256K-token input limit, but training used sequences up to about 32K tokens, so longer inputs are only spot-checked. Images are resized to 1.6 megapixels and use about 1,600 sequence positions each, so several large images consume context quickly. There is no maximum-output setting because the model generates no text.
Verified Specifications — 
Decider V1.2
*
Input modalities
Text
output modalities
Text
Context window
262144
 tokens
Maximum output tokens
235929
Reasoning
No
Knowledge cutoff
October 2026
Pricing (standard)
0.06
 AnyTokens in
 / 
0
 AnyTokens out

Comparison

Decider V1.2 or Decider Flash V1.2 for Production Decisions?

Both models use the same Decisions API, request format and text and image support, and output tokens are free on both. Flash is a 4B model distilled from the 27B Decider models. Decider V1.2 is the 27B default. In Perplexity's October 19, 2026 test, a request of about 248,000 input tokens took 53 seconds on Decider V1.2 and 16 seconds on Flash. The decision depends on how nuanced each judgment is and how many questions you ask per input. Perplexity advises testing both on labeled data.

Dimension
Decider V1.2
Decider Flash V1.2r
Context window *
262144
tokens
262144
tokens
Output speed *
N/A
tok/s
N/A
tok/s
Intelligence Index *
N/A
N/A
Input pricing
0.06
AnyToken
0.06
AnyToken
Output pricing
0
AnyToken
0
AnyToken
Knowledge cutoff *
October 2026
October 2026

Choose Decider V1.2 when judgments are nuanced, such as detailed rubric grading or checking claims against long source text. Also choose it when a wrong answer is costly, or when you ask three or more questions about one state, because it bills the state once. Choose Decider Flash V1.2 for high-volume decisions with clear criteria like routing, labeling and filtering. It also fits single-question requests and latency-sensitive paths. Its smaller footprint is easier to self-host. Keep Flash only if it meets your accuracy bar.

Limitations & Trade-offs

Where Decider V1.2 falls short

1
No text generation. Perplexity states that the Decisions API does not write replies, generate code or explain its reasoning. Decider V1.2 returns numbers only, and it is not a drop-in chat model. Workflows that need a rationale, a drafted response or a multi-step plan still need a language model next to it. Use Decider V1.2 as the classification or gating step, and hand cases that need explanation to a generative model.
2
Grouped questions influence each other. All questions in a request share one sequence and attend to one another. Perplexity reports that grouping helps when questions are facets of one decision. Scoring independent candidates together can cost about 3 points of accuracy, against about 0.4 for one candidate per request. For reranking or independent labels, send separate requests. If a request exceeds the input limit, the API splits questions into groups and bills the state again for each group.
3
Probabilities still need threshold validation. Perplexity reports calibration error of about 0.05 on held-out decision datasets, so outputs remain somewhat over-confident. Its v1.2 training data also includes official training splits of several benchmarks, so Perplexity-run gains may not transfer. A MindStudio hands-on test gave only 65.9% toward the wrong answer on a clear image failure case. It also skewed negative on ambiguous text. Calibrate on labeled data and review uncertain cases.
4
Long inputs are slower and less validated. Training used sequences up to about 32K tokens, and Perplexity has only spot-checked longer requests. In its October 19, 2026 test, a request of about 248,000 input tokens took 53 seconds, and timeouts return a 504 error. Chunk long documents, keep states short where latency matters, and size client timeouts to input length. For latency-critical paths, consider Flash.

Best-Fit Workloads

Where this model earns its place

01

Multi-field ticket triage

‍
Decider V1.2 answers several questions about one message in a single pass, and the joint format costs about as much as one question. A support message can return a team assignment, a blocked yes/no and a frustration score together. In MindStudio's example, the team call came back at 99.8% confidence. This fits helpdesk routing and workflow dispatch where code acts on thresholds. Review low-confidence, idiomatic or sarcastic messages, where hands-on tests showed lopsided negative scores.

02

Claim verification against source text

‍
On Vals AI's ClaimBench, Decider V1.2 scored 99.69% at labeling claims as supported, contradicted or unsupported by 10-K excerpts. It reached 98.5% on subtle contradictions. Perplexity names checking a claim against long source text as a use case for this larger model. This fits compliance review, filing QA and grounding checks on generated reports. Instruct it to judge only from the supplied excerpt, and validate on your own document types.

03

Confidence-gated LLM cascades

‍
Each answer carries a probability, so you can accept confident decisions and escalate the rest. Vals AI's cascade handled 99.7% of claims with Decider V1.2 alone and sent the remainder to Claude Haiku 5.5. Combined accuracy was 99.85%. This fits high-volume review pipelines where a language model is only needed for ambiguous cases. You need a held-out labeled set to tune the threshold, and you should revalidate it whenever the model version changes.

04

Rubric grading and moderation

‍
Score questions return a probability for each level of an ordered rubric, plus an expected score. Choice questions support up to 255 options, and images can be part of the state. Perplexity recommends the larger model for detailed rubric grading. This fits evaluating LLM outputs and moderation queues. The model gives no explanation for a grade, and vision outputs need calibration on your own images.

Pricing in anytokens via AnyAPI
Input
0.06
₳
Output
0
₳
Cache write
—
₳
Cache read
—
₳

Integration

Access Decider V1.2 via AnyAPI.ai

Access Decider V1.2 through AnyAPI.ai using a unified API built for multi-model AI applications. Integrate Decider V1.2 without maintaining a separate provider-specific connection, and keep the flexibility to test, switch, or combine models as your application requirements evolve.

01

One API integration

Access Decider V1.2 and other AI models through the same API workflow instead of maintaining separate integrations for every provider.

02

Easy model switching

Test Decider V1.2 against alternative models or switch models as your performance, capability, or cost requirements change without rebuilding your application around another provider API.

03

Flexible for production

Use Decider V1.2 from experimentation through production while keeping your AI stack flexible as workloads, traffic, and model requirements evolve.

04

Multi-model applications

Use Decider V1.2 for the workloads where it performs best and combine it with other models for tasks that require different capabilities, performance, or efficiency.

Frequently Asked Questions

Answers to common questions about integrating and using this AI model via AnyAPI.ai

Decider V1.2 is Perplexity's 27B open-weight decision model, built on Qwen3.8-27B. It reads text, JSON or images and returns probabilities for yes/no, multiple-choice or rubric-scored questions instead of generating text. It succeeds Decider V1.1 27B with the same API contract but a new joint request format, so v1.1-style prompts are not compatible.

The Perplexity API documents a 256K-token input limit, and the open weights have a 262,144-position limit. Perplexity trained on sequences up to about 32K tokens, so longer inputs are only spot-checked. Maximum output tokens does not apply, because the model returns probabilities rather than generated text.

Yes. Decider V1.2 accepts images alongside text and JSON, resized to at most 1.6 megapixels, with each large image using about 1,600 sequence positions. Output is still probabilities, not captions. Perplexity reports better vision scores than v1.1, but a hands-on test showed weak confidence on a clear failure case, so validate on your own images.

Use Decider V1.2 for nuanced judgments, detailed rubrics, or three or more questions per input, since it bills the state once. Use Flash, a 4B model, for high-volume decisions with clear criteria. Flash bills the state once per question. Both models have free output tokens. Run both on labeled data and keep Flash only if it meets your accuracy bar.

Vals AI measured 99.69% accuracy for Decider V1.2 on ClaimBench, a 1,960-claim test against 10-K excerpts. It ranked second among decision models on the October 23, 2026 leaderboard behind d1-ultra, and scored 98.5% on subtle contradictions. Results are specific to financial claim verification, so tune thresholds on your own data.

* Benchmark data source: Artificial Analysis artificialanalysis.ai