Decider V1.1 27B is Perplexity’s updated decision checkpoint. It evaluates supplied content against a defined question and produces probabilities over the valid answers. Its native artifact has a decision readout rather than a full-vocabulary language-generation head. The useful result is a bounded decision distribution and its interpreted answer, not an open-ended explanation or a general chat response.
Perplexity identifies this model as an update of Decider V1 27B that retains the same backbone, with changes to the attention setup and more training data. Its backbone is Qwen3.8-27B. The V1.1 edition should retain its own name and configuration rather than being described as an interchangeable copy of the earlier checkpoint.
The published example supplies a row containing a state and a typed choice question. The question includes instructions and criteria whose keys are the semantic answers and whose descriptions define when each applies. The model predicts probabilities, then the producer’s answer helper interprets those probabilities for the question. The inference example can process a list of rows, with one decision tied to each row’s evidence and question.
For request routing, provide the actual message and relevant context, then define the departments or categories available. An illustrative task might distinguish an integration failure, an access problem and a request for product information. Make each description precise enough to settle a borderline case, and retain the option definitions with the result. A category distribution can then support a routing decision or a review step when alternatives remain close. The model’s chosen result does not itself execute the workflow action.
The native implementation accepts images alongside the state and question, using image-file inputs, in-memory images or encoded image data. For a document image or screenshot, supply the visual evidence and ask a closed question whose options describe the relevant outcomes. Identify the visible feature that matters and provide the text context needed to interpret it. For example, classify whether a pictured item belongs to one of the supplied product categories rather than asking the decision model to write a complete product description.
The processor preserves aspect ratio during resizing and rounds image sides to multiples of 32 pixels. The documented processed area begins at 65,536 pixels and is bounded by a configurable maximum; its default is 4,194,304 pixels, or 2048 by 2048. Each 32-by-32 patch contributes one visual token, so that default permits up to 4,096 visual tokens for an image. These figures describe the producer’s native image preparation, not a general application upload contract.
The documented prepare step requires the text and all images in one decision to fit within 8,192 tokens. Oversized input is rejected rather than silently truncated. Several images share that budget with the written state and question. Reduce irrelevant source text or the image-size cap when preparing a combined decision, while retaining the detail that determines the answer.
The training and reported evaluation setup capped images at 512 by 512, corresponding to 262,144 pixels and up to 256 visual tokens. The configurable inference cap can retain more detail, but the card warns that higher resolution is outside that training distribution and uses more memory and processing time. A larger image setting is therefore not a guarantee of a better decision. Keep the input preparation consistent with the question and inspect whether the needed visual feature is represented clearly.
The native checkpoint’s full-attention layers use a saved noncausal attention mode, while its linear-attention layers retain their own behavior. The maker states that default causal inference does not reproduce the evaluated setup. Its prediction implementation applies the saved calibration temperature; if logits are used directly, that temperature is applied once and the probabilities are normalized over the current valid candidates. These details belong to the exact decision profile and should be preserved when interpreting its numerical outputs.
The separate decision readout also distinguishes this artifact from a generative export. A conversion to a vocabulary-based generation interface needs an explicit mapping and must preserve the attention behavior. Prepare closed questions for the native decision profile; use a suitable generation model when the task needs chat, code, explanations or tool requests.
A useful final artifact keeps the state, question, allowed answers and resulting distribution associated. Define the question around evidence actually present, review ambiguous cases against that evidence, and use labeled examples from the intended task to decide how numerical outputs should affect routing or classification. The model supplies decision probabilities; the criteria and the surrounding application determine how those probabilities become a useful action or recorded label.
", "aboutText": "Decider V1.1 27B is Perplexity’s updated decision checkpoint. It evaluates supplied content against a defined question and produces probabilities over the valid answers. Its native artifact has a decision readout rather than a full-vocabulary language-generation head. The useful result is a bounded decision distribution and its interpreted answer, not an open-ended explanation or a general chat response.\n\n### What changes in the V1.1 edition\n\nPerplexity identifies this model as an update of Decider V1 27B that retains the same backbone, with changes to the attention setup and more training data. Its backbone is Qwen3.8-27B. The V1.1 edition should retain its own name and configuration rather than being described as an interchangeable copy of the earlier checkpoint.\n\n### State, question and valid answers\n\nThe published example supplies a row containing a state and a typed choice question. The question includes instructions and criteria whose keys are the semantic answers and whose descriptions define when each applies. The model predicts probabilities, then the producer’s answer helper interprets those probabilities for the question. The inference example can process a list of rows, with one decision tied to each row’s evidence and question.\n\nFor request routing, provide the actual message and relevant context, then define the departments or categories available. An illustrative task might distinguish an integration failure, an access problem and a request for product information. Make each description precise enough to settle a borderline case, and retain the option definitions with the result. A category distribution can then support a routing decision or a review step when alternatives remain close. The model’s chosen result does not itself execute the workflow action.\n\n### Text and image evidence\n\nThe native implementation accepts images alongside the state and question, using image-file inputs, in-memory images or encoded image data. For a document image or screenshot, supply the visual evidence and ask a closed question whose options describe the relevant outcomes. Identify the visible feature that matters and provide the text context needed to interpret it. For example, classify whether a pictured item belongs to one of the supplied product categories rather than asking the decision model to write a complete product description.\n\nThe processor preserves aspect ratio during resizing and rounds image sides to multiples of 32 pixels. The documented processed area begins at 65,536 pixels and is bounded by a configurable maximum; its default is 4,194,304 pixels, or 2048 by 2048. Each 32-by-32 patch contributes one visual token, so that default permits up to 4,096 visual tokens for an image. These figures describe the producer’s native image preparation, not a general application upload contract.\n\n### Combined input limits and resolution scope\n\nThe documented prepare step requires the text and all images in one decision to fit within 8,192 tokens. Oversized input is rejected rather than silently truncated. Several images share that budget with the written state and question. Reduce irrelevant source text or the image-size cap when preparing a combined decision, while retaining the detail that determines the answer.\n\nThe training and reported evaluation setup capped images at 512 by 512, corresponding to 262,144 pixels and up to 256 visual tokens. The configurable inference cap can retain more detail, but the card warns that higher resolution is outside that training distribution and uses more memory and processing time. A larger image setting is therefore not a guarantee of a better decision. Keep the input preparation consistent with the question and inspect whether the needed visual feature is represented clearly.\n\n### Attention, readout and probability calibration\n\nThe native checkpoint’s full-attention layers use a saved noncausal attention mode, while its linear-attention layers retain their own behavior. The maker states that default causal inference does not reproduce the evaluated setup. Its prediction implementation applies the saved calibration temperature; if logits are used directly, that temperature is applied once and the probabilities are normalized over the current valid candidates. These details belong to the exact decision profile and should be preserved when interpreting its numerical outputs.\n\nThe separate decision readout also distinguishes this artifact from a generative export. A conversion to a vocabulary-based generation interface needs an explicit mapping and must preserve the attention behavior. Prepare closed questions for the native decision profile; use a suitable generation model when the task needs chat, code, explanations or tool requests.\n\nA useful final artifact keeps the state, question, allowed answers and resulting distribution associated. Define the question around evidence actually present, review ambiguous cases against that evidence, and use labeled examples from the intended task to decide how numerical outputs should affect routing or classification. The model supplies decision probabilities; the criteria and the surrounding application determine how those probabilities become a useful action or recorded label.", "editorialOverlay": { "copy_fields": null, "copy_sha256": null, "copy_source": null, "html_sha256": "cb92bc5807f903ebe9e5b518aa74fa5470d815388ce67b55b22862a3b11da64e", "module_sha256": "ee9dc1c50b1e6a8fb7fa062030fcb4646b9aaaeb08be513b723a5a92a7290f06", "raw_model_unchanged": true, "schema": "ailoot-native-model-editorial-v1" }, "locale": "en", "methods": [ { "html": "perplexity/pplx-decider-v1.1-27bPerplexity’s Decider V1.1 27B evaluates a supplied state and question and returns probabilities across the allowed answers. Its native decision checkpoint supports text and images, with a dedicated readout and documented input preparation limits rather than a free-form text-generation contract.
This description covers the model’s capabilities. Available in Ailoot inputs, outputs and options are listed for the selected method below.
Decider V1.1 27B is Perplexity’s updated decision checkpoint. It evaluates supplied content against a defined question and produces probabilities over the valid answers. Its native artifact has a decision readout rather than a full-vocabulary language-generation head. The useful result is a bounded decision distribution and its interpreted answer, not an open-ended explanation or a general chat response.
Perplexity identifies this model as an update of Decider V1 27B that retains the same backbone, with changes to the attention setup and more training data. Its backbone is Qwen3.8-27B. The V1.1 edition should retain its own name and configuration rather than being described as an interchangeable copy of the earlier checkpoint.
The published example supplies a row containing a state and a typed choice question. The question includes instructions and criteria whose keys are the semantic answers and whose descriptions define when each applies. The model predicts probabilities, then the producer’s answer helper interprets those probabilities for the question. The inference example can process a list of rows, with one decision tied to each row’s evidence and question.
For request routing, provide the actual message and relevant context, then define the departments or categories available. An illustrative task might distinguish an integration failure, an access problem and a request for product information. Make each description precise enough to settle a borderline case, and retain the option definitions with the result. A category distribution can then support a routing decision or a review step when alternatives remain close. The model’s chosen result does not itself execute the workflow action.
The native implementation accepts images alongside the state and question, using image-file inputs, in-memory images or encoded image data. For a document image or screenshot, supply the visual evidence and ask a closed question whose options describe the relevant outcomes. Identify the visible feature that matters and provide the text context needed to interpret it. For example, classify whether a pictured item belongs to one of the supplied product categories rather than asking the decision model to write a complete product description.
The processor preserves aspect ratio during resizing and rounds image sides to multiples of 32 pixels. The documented processed area begins at 65,536 pixels and is bounded by a configurable maximum; its default is 4,194,304 pixels, or 2048 by 2048. Each 32-by-32 patch contributes one visual token, so that default permits up to 4,096 visual tokens for an image. These figures describe the producer’s native image preparation, not a general application upload contract.
The documented prepare step requires the text and all images in one decision to fit within 8,192 tokens. Oversized input is rejected rather than silently truncated. Several images share that budget with the written state and question. Reduce irrelevant source text or the image-size cap when preparing a combined decision, while retaining the detail that determines the answer.
The training and reported evaluation setup capped images at 512 by 512, corresponding to 262,144 pixels and up to 256 visual tokens. The configurable inference cap can retain more detail, but the card warns that higher resolution is outside that training distribution and uses more memory and processing time. A larger image setting is therefore not a guarantee of a better decision. Keep the input preparation consistent with the question and inspect whether the needed visual feature is represented clearly.
The native checkpoint’s full-attention layers use a saved noncausal attention mode, while its linear-attention layers retain their own behavior. The maker states that default causal inference does not reproduce the evaluated setup. Its prediction implementation applies the saved calibration temperature; if logits are used directly, that temperature is applied once and the probabilities are normalized over the current valid candidates. These details belong to the exact decision profile and should be preserved when interpreting its numerical outputs.
The separate decision readout also distinguishes this artifact from a generative export. A conversion to a vocabulary-based generation interface needs an explicit mapping and must preserve the attention behavior. Prepare closed questions for the native decision profile; use a suitable generation model when the task needs chat, code, explanations or tool requests.
A useful final artifact keeps the state, question, allowed answers and resulting distribution associated. Define the question around evidence actually present, review ambiguous cases against that evidence, and use labeled examples from the intended task to decide how numerical outputs should affect routing or classification. The model supplies decision probabilities; the criteria and the surrounding application determine how those probabilities become a useful action or recorded label.
POST /v1/systemonetext, imagedecisions| Field | Type | Requirement | Values & limits | Default |
|---|---|---|---|---|
Fieldmodel | Typestring | RequirementRequired | Values & limits perplexity/pplx-decider-v1.1-27b | Default— |
Fieldprovider | Typeschema | RequirementOptional | Values & limits | Default— |
Fieldquestions | Typeobject | RequirementRequired | Values & limits | Default— |
Fieldsession_id | Typestring | RequirementOptional | Values & limits | Default— |
Fieldstate | Typeschema | RequirementRequired | Values & limits | Default— |
Fieldtrace | Typeschema | RequirementOptional | Values & limits | Default— |
Fielduser | Typestring | RequirementOptional | Values & limits | Default— |
Fieldquestions.<id>.type | Typestring | RequirementRequired | Values & limits noul, choice, score | Default— |
Fieldquestions.<id>.instructions | Typestring|object|array | RequirementRequired | Values & limits | Default— |
Fieldquestions.<id>.criteria | Typeobject|array | RequirementOptional | Values & limits Conditions: choice/score: required; noul: optional. choice criteria is object; score is array with minItems1. | Default— |
Fieldquestions.<id>.criteria.true | Typestring|object|array | RequirementRequired | Values & limits Applies when: noul criteria object supplied | Default— |
Fieldquestions.<id>.criteria.false | Typestring|object|array | RequirementRequired | Values & limits Applies when: noul criteria object supplied | Default— |
noul · Required: state, questions.<id>.type=noul, questions.<id>.instructions
choice · Required: state, questions.<id>.type=choice, questions.<id>.instructions, criteria object
score · Required: state, questions.<id>.type=score, questions.<id>.instructions, criteria array with minItems1
| Parameter | Contract |
|---|---|
Parametercontent_type | Contractapplication/json |
Parameterrequired | Contractmodel, state, questions |
Parametermaterial_types | Contracttext, image |
Parameteroptional_controls | Contractprovider, session_id, trace, user |
Parametermultimodal_input_binding | ContractUse only exact declared state/document representation. Manufacturer image capability alone does not establish a model-specific accepted image carrier. |
Lifecycle: synchronous
Send the exact model ID and retain the complete native response.
Tariff references do not add request options. Supported parameters are listed for the selected method.
Match each charge to the conditions shown. Use one rate for each set of alternative configurations.
| Configuration | Rate schedule | Context tokens, more than | Context tokens, up to and including | Charge |
|---|---|---|---|---|
| ConfigurationBase token rates | Rate scheduleBase rate | Context tokens, more than— | Context tokens, up to and includingNo upper bound | Charge Input · Input tokens $0.00004 / 1K tokens Output · Output tokens $0 / 1K tokens Input · Cache read — / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
| ConfigurationRequest-length tier 1 | Rate schedule— | Context tokens, more than0 | Context tokens, up to and includingNo upper bound | Charge Input · Input tokens $0.00004 / 1K tokens Output · Output tokens $0 / 1K tokens Input · Cache read — / 1K tokens Input · Cache write — / 1K tokens Input · Cache write, 1 hour — / 1K tokens |
Ailoot reserves an estimated amount before a request. After the result, it settles the final charge from measured usage. Streaming settlement uses the final usage record. How reservation and settlement work →
{\n "model": "perplexity/pplx-decider-v1.1-27b",\n "questions": {\n "is_bug": {\n "criteria": {\n "false": "The customer is asking a question or requesting a feature.",\n "true": "The customer describes broken or unexpected product behavior."\n },\n "instructions": "Is the customer reporting a software defect?",\n "type": "noul"\n },\n "team": {\n "criteria": {\n "account": "Login, permissions, or profile issues.",\n "frontend": "Rendering, layout, or browser compatibility issues.",\n "payments": "Checkout, billing, or payment processing issues."\n },\n "instructions": "Which team should own this ticket?",\n "type": "choice"\n },\n "urgency": {\n "criteria": [\n "Can wait for the next release",\n "Should be fixed this week",\n "Blocking revenue right now"\n ],\n "instructions": "How urgent is this ticket?",\n "type": "score"\n }\n },\n "state": {\n "customer_tier": "enterprise",\n "ticket": "My checkout page shows a blank screen after I click Pay. I have tried two browsers."\n }\n}set -eu\n: "${AILOOT_API_KEY:?Set your Ailoot API key}"\n: "${AILOOT_REQUEST_FILE:?Set your actual JSON request file}"\nexport AILOOT_REQUEST_FILE\npython3 - <<'PY_REQUEST'\nimport json,os\nfrom pathlib import Path\np=json.loads(Path(os.environ['AILOOT_REQUEST_FILE']).read_text(encoding='utf-8'))\nif not isinstance(p,dict): raise SystemExit('Request must be a JSON object')\np['model']='perplexity/pplx-decider-v1.1-27b'\nPath('request.json').write_text(json.dumps(p,ensure_ascii=False),encoding='utf-8')\nPY_REQUEST\ncurl --fail-with-body --silent --show-error https://api.ailoot.ai/v1/systemone \\\n -H "Authorization: Bearer $AILOOT_API_KEY" -H 'Content-Type: application/json' \\\n --data-binary @request.json -D response-headers.txt -o result.json\npython3 - <<'PY_RESULT'\nimport json\nfrom pathlib import Path\nprint(json.dumps(json.loads(Path('result.json').read_text()),ensure_ascii=False,indent=2))\nPY_RESULT\njson
Keep every complete returned response, file and content part.
Every supplied question-ID answer with its exact type, noul/choice/score value, confidence, probabilities and legend is retained. Entire original JSON is stored and returned only after settlement.
Preserve original operation and full/partial reply; do not replay POST.
| Field | Type |
|---|---|
Fieldmodel | Typestring |
Fieldid | Typestring |
Fieldprovider | Typestring |
Fieldanswers.<id>.type | Typestring |
Fieldanswers.<id>.noul | Typenumber |
Fieldanswers.<id>.choice | Typestring |
Fieldanswers.<id>.score | Typenumber |
Fieldanswers.<id>.confidence | Typenumber |
Fieldanswers.<id>.probabilities | Typeobject |
Fieldanswers.<id>.legend | Typeobject |
Fieldusage.input_tokens | Typeinteger |
Fieldusage.output_tokens | Typeinteger |
Fieldusage.cost | Typenumber |
| Response | Condition | Next step |
|---|---|---|
Response400 · invalid_request_error | ConditionInvalid required field, representation or value | Next stepCorrect the indicated request field. |
Ailoot Ultra perplexity/pplx-decider-v1.1-27b
Use the method paths shown above.