Yes or no, choose, or score: which one?
Yes or no, pick one, or rate it: start with examples, then learn the API names.
Pick the question before learning the API names
Jev answers questions with a defined set of possible answers. Start with the answer you need.
| What do you need? | Support example | Official name | Fields to read |
|---|---|---|---|
| Yes or no? | Does the customer explicitly request a refund? | Noul | noul, the probability of yes from 0 to 1 |
| Which one? | Is this for delivery, refunds, or payment? | Choice | choice, probabilities, confidence |
| How severe? | Is this low, medium, or high severity? | Score | score, legend, probabilities, confidence |
Noul has no separate confidence field and no built-in third “unknown” answer. Review behavior belongs in application code.
Describe a scale, not just numbers
“Rate this customer from 1 to 10” mixes intent, value and risk. Ask separate questions and combine the results in code.
For operational impact, use distinct descriptions: unaffected; degraded with a workaround; essential work blocked. Three levels have indices 0, 1 and 2. A fractional result is a position on that scale, not an automatic percentage.
Give Choice an escape route
Include other when the options may not cover reality. Describe what each confusing category includes and excludes.
Several questions can share a call
Ask about department, refund intent and impact against one state. A later question that depends on an earlier answer still needs application sequencing. Batching does not remove input limits or token costs.
Sources and verification boundary
Reviewed September 19, 2026. Documentation-based guidance, not a live API or business-performance test.
TypeSafe · Choice →TypeSafe · Score →TypeSafe · Noul →TypeSafe · Confidence →