Now available: GPT-6 Luna Decisions

Try the model

PERPLEXITY / OPENROUTER

Perplexity Decider V1.1 27B

Perplexity's newer 27B decision checkpoint classifies, routes and scores shared text, JSON or images with typed answers and probabilities.

perplexity/pplx-decider-v1.1-27b
TextJSONImages

New accounts get 100 credits. The playground and API share one balance.

Context window

262,144

tokens · provider-listed maximum

OpenRouter input price

$0.02 / 1M

per million input tokens

OpenRouter output price

$0 / 1M

output tokens are free upstream

This site's input rate

300

credits per million input tokens · minimum 1 per successful request

JEV / SYSTEM ONE

Uses the Jev decision playground

OpenRouter describes V1.1 as succeeding Decider V1 with the same API contract. This service sends the shared state and Choice, Score or Noul questions through the Decisions endpoint and validates the typed answers.

SPAN / NOUL

How it differs from Span

Span accepts only Noul behavior questions and requires text or a specific input/output conversation object. This model also accepts Choice and Score questions, with text, generic JSON objects, or arrays as state. Use the Jev playground for this broader decision contract.

Three structured answer types

Choice returns a named option and its probability distribution. Score returns a value on an ordered scale with probabilities. Noul returns the probability of a yes/no condition. Multiple questions share the same state.

choicescorenoul

Upstream context: 262,144 tokens. Text, JSON and image inputs are supported. Add up to 4 PNG, JPEG or WebP images (4 MiB each, 8 MiB total, 16 MP each); complete image requests may use 13 MiB, while text and questions stay within 32 KiB. Up to 8 questions; Choice: 2–255 options; Score: 2–10 ordered levels.

OpenRouter lists text and image input for this model. Image attachments use this service's shared image preparation and validation.

Input and output credits

OpenRouter lists $0.02 per million input tokens and $0 for output. This service charges 300 credits ($0.03) per million actual input tokens, including questions and processed images, rounded up per successful request with a minimum of 1 credit ($0.0001). Web, API and evaluation share this rate. Output tokens add no charge; failed calls release the credit reservation.

max(1, ceil(input_tokens × 300 / 1,000,000))

A successful request with 1,000 input tokens costs 1 credit; 5,000 input tokens cost 2 credits. Output tokens add no charge. Failed calls release the credit reservation.

Verified October 10, 2026: text, object and array state with all three answer types, contrasting red/blue images and four-image requests. Provider prices and token usage match the published $0.02/M input rate. Actual credits fit the reservation in these probes. These checks verify compatibility, not model accuracy.

Try Perplexity Decider V1.1 in the decision playground

The Jev workbench below starts with this model selected. Try a recipe, edit the state and questions, or export API code. This page stores its browser draft separately from other model pages and the main playground.

What do you want to decide?

Choose a task to load its input and rules. Loading examples uses no credits.

Perplexity Decider V1.1 27B ↗Span · behavior evaluation ↗

Images verified through OpenRouter on October 6, 2026. Text, JSON and image inputs are supported. Add up to 4 PNG, JPEG or WebP images (4 MiB each, 8 MiB total, 16 MP each); complete image requests may use 13 MiB, while text and questions stay within 32 KiB. The text-state cap does not include image bytes.

Text or JSON shared by all questions; attach images below on vision models.

Images 0/4

Image input

Embedded images stay in this page until you leave or refresh. Saved configurations and history keep image metadata; API URL references are retained and may expire.

Advanced question settings

Questions 1/8

Which team should handle this ticket? Use other when no option fits.Choice

Options

Maximum credit budget: 1 credits

We reserve this budget before the model runs, then charge actual usage and return the difference. Failed calls are refunded.

New account? Receive 100 credits once. Short requests typically use 1 credit; longer inputs can use more.

100 welcome credits · one balance for web & API

Draft saved in this browser · Your draft will be restored after sign-in.

Your current configuration stays in this browser tab for the setup flow.

ILLUSTRATIVE EXAMPLE · NO CREDITS USED

“I was charged twice this morning. Please refund the duplicate payment today.”

One input → structured decisions

Choice

Billing

Route to the billing queue

Yes / no

96%

Probability of an urgent request

Score

2.8 / 3

Urgency on a 0–3 scale

Static illustration of the output format. Values are not a live model response or a measure of accuracy.

Web runs and saved configurations are private to your account. API history stores usage only. Embedded image pixels are omitted from drafts, configurations and history; metadata and missing-image counts remain. Add the images again before replaying. API URL references may expire. API setup exports local-file code without storing pixels.Usage ↗

Your draft will be restored after sign-in.

Use the same decision API

Send model, state, and questions to Decisions API's /v1/systemone endpoint with an API key created here. Set model to perplexity/pplx-decider-v1.1-27b; answers are in data.result.answers and token usage is in data.result.usage.

// Server-side JavaScript (Node 20+ or Bun). Set DECISIONS_API_KEY.
const response = await fetch("https://decisions-api.dev/v1/systemone", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.DECISIONS_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
  "model": "perplexity/pplx-decider-v1.1-27b",
  "state": "I was charged twice for order A-4471. Please refund the duplicate payment.",
  "questions": {
    "route": {
      "type": "choice",
      "instructions": "Which team should handle this ticket? Use other when no option fits.",
      "criteria": {
        "billing": "Payments, charges and refunds",
        "technical": "Bugs and product errors",
        "account": "Login and account access",
        "other": "None of these teams"
      }
    }
  }
}),
});
const body = await response.json();
if (!response.ok || body.code !== 0) throw new Error(body.message);
console.log(body.data.result.answers);
console.log(body.data.creditsUsed);