Questions and answers

Every call to POST /v1/decide has the same shape:

context + questions  →  answers

context is the text to decide on, such as a user message, a ticket or an agent step.
questions is a map of the decisions you want about that context, keyed by ids you choose.
answers has one answer per question, under the same ids, in the same order.

Questions

{
  "context": "Customer wants to return an item.",
  "questions": {
    "department": {
      "type": "choice",
      "options": {
        "shipping": "Shipping and delivery issues",
        "returns": "Returns and refunds",
        "billing": "Billing and payment issues"
      }
    }
  }
}

Each question has:

Field	Required	Description
id (the key)	Yes	Your name for the question, like `department`. 1 to 100 characters. Returned as the key in `answers`.
`type`	Yes	Always `"choice"`: pick one option. It is the only question type today.
`options`	Yes	Map of option id to description, 2 to 64 options.
`task_type`	No	`"intent"` (default) or `"tool"` for tool routing.

Options

Option ids are yours. Use the ids your code already understands, like transaction_charged_twice or calendar_search. Krun returns them exactly as sent, in choice and in probabilities. Option ids can be 1 to 200 characters. The description is optional:

With a description, like "returns": "Returns and refunds", the model reads it to understand the option. Descriptions can be up to 1,000 characters.
Label-only, with "" or null, the model uses the option id alone. Use readable ids, like lost_or_stolen_card.

The choice between the two changes how reliable abstention is. See Abstention status.

Duplicate question ids or option ids, unknown fields and question types other than choice are rejected with 400 INVALID_REQUEST before any inference runs.

Answers

{
  "model": "krun-one-v0",
  "answers": {
    "department": {
      "type": "choice",
      "choice": "returns",
      "confidence": 0.967536,
      "probabilities": {
        "shipping": 0.011351,
        "returns": 0.978886,
        "billing": 0.009763
      },
      "abstain": false,
      "abstention_status": "advisory"
    }
  },
  "usage": {
    "input_tokens": 49
  }
}

Field	Description
`type`	`"choice"`.
`choice`	The selected option id, or `null` when the model abstains.
`confidence`	Top-1 probability minus top-2 probability. See Confidence and probabilities.
`probabilities`	Probability per option id, in request order.
`abstain`	`true` when `confidence` is below the abstention threshold. `choice` is then `null`.
`abstention_status`	`"calibrated"` or `"advisory"`: how much to trust `abstain`. See Abstention.

The response also has model, the model that answered, and usage.input_tokens. See Usage and tokens. The request id is not in the body. It is in the X-Request-ID response header, and the Python SDK exposes it as result.request_id.

Several questions per call

A request can carry up to 16 questions about the same context. They are answered together, in one model job. See Multiple questions.

Overview

Concepts

Guides

SDKs

API Reference

Resources

Questions and answers

Questions

Options

Answers

Several questions per call

​Questions

​Options

​Answers

​Several questions per call

Questions

Options

Answers

Several questions per call