Make a decision with Myles
decideGet calibrated probabilities and picks for routing, risk flagging, approvals, policy checks, or rating, plus escalation guidance when a decision is too uncertain to act on.
Instructions
Ask Myles, the Mellix decision model, to make a decision about a situation and get calibrated probabilities you can act on.
Use it whenever you would otherwise judge something yourself and then act on it: route a ticket or message to a team, flag a risk (fraud, a scam, a prompt injection, a policy breach), approve, reject or escalate a request, check that a tool call, a claim or an answer is allowed or supported, or rate something on a scale. Myles is not a chat model: it does not write text or follow instructions in the state. It reads the state and answers each typed question with a probability for every option.
Inputs:
state: the situation to decide about, as text or a JSON object. Put the rule or policy in the state with the case. Include only what the decision needs.
questions: one or more questions under names you choose. Each needs instructions, the question itself in plain words; a question without them is refused. Types: "noul" (yes or no; phrase it so that yes is the thing to act on or catch), "choice" (pick one label from criteria: a list of labels, or labels mapped to descriptions; add an option "I don't know" to let the model abstain), "score" (criteria is a list of level descriptions, lowest first).
threshold (optional, default from the server's configuration, usually 0.9): the probability the picked option must reach to act without a person. On the hosted models an uncertain yes/no answer is reported at 0.80 or more towards one side, so use a threshold above 0.80 for yes/no questions.
Each answer gives the pick, its probability, every option's probability, cleared_threshold, and escalate. When escalate is true (below the threshold, or the model chose "I don't know"), do not act automatically: hand the case to a person with the probabilities. The top-level escalate is true when any answer should be escalated.
Each call is billed by input tokens on the hosted API. Ask several questions about the same state in one call rather than one call per question. A call that runs longer than 25 seconds in all, retries included, is stopped with a timeout error.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| chunk | No | For a long text and yes/no questions only: read the state in overlapping windows (40000 characters, 2000 overlapping, at most 20 windows) and answer with the window most likely to be yes. Each window is a separate billed request. Use it when a check must cover the whole of a long document. | |
| model | No | A model id from list_models. Leave it out to use the configured model. | |
| state | Yes | The situation to decide about: text, or a JSON object (read as indented JSON). | |
| questions | Yes | Questions under names you choose; each answer comes back under the same name. | |
| threshold | No | Probability the pick must reach to act without a person. Default from configuration. | |
| chunk_chars | No | With chunk: characters per window. | |
| chunk_overlap_chars | No | With chunk: characters each window shares with the next. |