Every successful decision reports the input tokens the model processed:
Krun One scores the options you send. It does not generate a completion, so there are no output tokens, and usage has no output_tokens field.
- Tokens are counted with the Krun One tokenizer, by the model itself. They are not estimated.
- Each question is scored as its own sequence: the context plus that question’s options.
input_tokens is the sum over all questions in the request.
- Adding questions to a request adds tokens, because the context is read once per question.
For example, the single-question request in the Quickstart used 49 input tokens. A request with three questions about a similar context used 141.
input_tokens can be null in the rare case that the model backend does not report it.
Tokens and quotas
Projects can have a monthly input-token quota and a monthly decision quota. Each question in a request counts as one decision. Only successful requests count toward quotas. See Rate limits and quotas.
Keep context focused on the text the decision depends on. Shorter contexts and fewer, clearer options use fewer tokens.
