> For the complete documentation index, see [llms.txt](https://docs.aimlapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aimlapi.com/api-references/decision-models.md). # Decision Models Decision models do not generate text. You give them a piece of content (the **state**) and a set of typed **questions**, and they return a typed answer for each question together with calibrated probabilities. They are built for the places inside an application where a fast, predictable, machine-readable verdict matters more than prose: routing, classification, triage, moderation gates, A/B triggers. Compared with prompting an LLM for JSON, a decision model answers in a fraction of the time, cannot produce anything outside the question schema, and reports how confident it is instead of writing a number into free text. ## Question Types | Type | Question | Answer | | -------- | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------- | | `noul` | A yes/no question. | `noul` — probability that the answer is "yes" (0–1). | | `choice` | Pick exactly one option from `criteria`. | `choice` — the selected key, plus a probability for every option and a `confidence`. | | `score` | Rate the state against ordered levels. | `score` — expected level index (may be fractional), a probability per level, the `legend` and a `confidence`. | | `box` | Where something is in an image. | `box` — the four edges as fractions of the width and height, plus a `confidence`. Jev 1.14 only; experimental. | The `state` can be a plain string, a JSON object, or an array of texts. Images are supported by [Jev 1.14](/api-references/decision-models/typesafe/jev-1.14.md) and [d1](/api-references/decision-models/liquid-ai/d1.md), passed in `assets` rather than in `state`; audio and video are not supported. {% hint style="warning" %} The question types above are the ones Jev and d1 take. [GPT-6 Luna](/api-references/decision-models/openai/gpt-6-luna.md) answers on the same endpoint but with **a different request shape**: the content goes in `input` rather than `state`, `questions` is an array of named items rather than an object, and its yes/no type is `predicate` rather than `noul`. Sending one model the other's shape is a `400`, so check the model's page before you switch `model`. {% endhint %} ## Pricing Decision models are billed by input tokens only; output tokens are reported in `usage` but are free. See the [pricing page](https://aimlapi.com/ai-ml-api-pricing) and the model card for current rates. ## Example: Triaging a Support Ticket ```powershell curl https://api.aimlapi.com/v1/decisions \ -H "Content-Type: application/json" \ -H "Authorization: Bearer " \ -d '{ "model": "typesafe/jev", "state": "Help! My payments have been failing for 3 days and nobody answers support.", "questions": { "is_urgent": { "type": "noul", "instructions": "Does this convey urgency?" }, "department": { "type": "choice", "instructions": "Which team should handle this?", "criteria": { "billing": "Payments, invoicing, refunds", "technical": "Bugs, outages, integrations", "sales": "Pricing, upgrades, new accounts" } }, "frustration": { "type": "score", "instructions": "How frustrated is the customer?", "criteria": ["Calm", "Frustrated", "Very angry"] } } }' ``` Every key from `questions` comes back under `answers` with a typed result: ```json { "model": "jev-1.14.0", "answers": { "is_urgent": { "type": "noul", "noul": 0.96 }, "department": { "type": "choice", "choice": "billing", "confidence": 0.98, "probabilities": { "billing": 0.99, "technical": 0.01, "sales": 0 } }, "frustration": { "type": "score", "score": 1.21, "confidence": 0.69, "legend": { "0": "Calm", "1": "Frustrated", "2": "Very angry" }, "probabilities": { "0": 0, "1": 0.79, "2": 0.21 } } }, "usage": { "input_tokens": 406, "output_tokens": 73 } } ``` ## All Available Decision Models
Model ID + API Reference linkDeveloperContextModel Card
typesafe/jevTypeSafe AI262 144Floating — always the current Jev
typesafe/jev-1.14TypeSafe AI262 144Current; adds images and box
typesafe/jev-1.13TypeSafe AI262 144Previous release, pinned
liquid/d1Liquid AI32 768No output tokens; reads images
openai/gpt-6-lunaOpen AI1 050 000Different request shape; also a chat model
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.aimlapi.com/api-references/decision-models.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.