kettei-core for a support ticket and the question “Which team should handle
this ticket?” (quickstart):
top is the likeliest outcome and p_top its probability. The models only score the outcomes
you listed. They never write text of their own, so your code always gets one of your outcomes,
with numbers it can act on.
What you can build
- Route work: which team should take a ticket, and how urgent it is.
- Guard actions: whether a tool call an agent wants to make is risky, or whether a message tries to override its instructions.
- Check AI output: whether an answer is supported by its sources, or relevant to the question.
How it works
1
Describe a decision
Write a question and the answers you allow. A decision can be a yes or no question, a choice
of one category, or a rating on a scale (core concepts).
2
Send it with your text
Call
POST /v1/decide with the text and up to 128 decisions about it. Each decision gets
its own answer.3
Act on the answer
Read each answer’s probabilities, or add a policy so the answer tells you what to do, such as
sending an unclear case to a person (read results).
A probability says how strongly the model favours an answer over the others you listed. It is
not a guarantee that the answer is right. Test your decisions on examples whose answers you know
before you let them act on their own.
Try it
The playground in the console runs decisions without an account, and has ready-made examples to start from.Open the playground
Pick an example, change the question and see each answer’s probability.
Next steps
Quickstart
Install a client and get your first answer in a few minutes.
Core concepts
Decisions, outcomes, probabilities, models and families.
Improve a decision
Use your own examples to make a decision more accurate.
Pricing
What decisions, fine-tuning and keeping a model ready cost.
