WHAT IS A DECISION MODEL
A decision model answers narrow, multiple-choice questions instead of generating open-ended text. You give it a state that describes the current situation and a set of questions about that state. It returns a probability for each answer option, scoring all questions in parallel. A generative LLM produces its answer one token at a time. That makes it flexible, but slow and expensive when all you need is a choice between a few options. A decision model skips text generation and only scores the options, so each decision is faster and cheaper. A decision model can’t write code, compose messages, or explain its reasoning. Use it as a fast decision layer next to your LLM, not as a replacement. The LLM sets up the state and acts on the result; the decision model makes the call.WHEN TO USE A DECISION MODEL
Decision models fit high-volume decisions where speed and cost matter:- Agent guardrails: check each action an agent proposes, such as exposing secrets, deleting data, or sending data outside your network, before it runs.
- Content moderation: classify large volumes of user content against your policies.
- Routing: pick which tool, workflow, or model handles a request.
- Automated testing and navigation: choose the next action in a game, UI, or browser session.
API INTERFACE
You send each decision as one request. The request holds the state to evaluate and the questions to answer about it. The response holds one answer per question.REQUEST
Each question has a
type, instructions that state the question, and criteria that describe the possible answers. There are three question types:
instructions and each criteria description can be a plain string, or a JSON object or array of structured guidance.
RESPONSE
The fields in each answer depend on the question type:
Response
AVAILABLE MODELS
Iris
Call and fine-tune the Iris decision model.