Tutorial · API quickstart
The smallest useful Jev request.
The public System One API takes a state plus one or more typed questions. Your API key stays on the server and the response is structured for software to consume.
1. Send state and questions
Put the facts relevant to the decision in state. Each entry in questions has a stable key, a supported type, instructions, and type-specific criteria when needed.
curl https://api.typesafe.ai/v1/systemone \
-H "Authorization: Bearer $JEV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "jev-latest",
"state": "A customer reports two posted charges for one order.",
"questions": {
"queue": {
"type": "choice",
"instructions": "Which team should handle this?",
"criteria": {
"billing": "Payments, refunds, and invoices",
"technical": "Product bugs"
}
}
}
}'2. Keep the output typed
Do not turn the result back into an open-ended chat response unless your product actually needs prose. The useful part of Jev is that your code can act on a known answer shape and inspect uncertainty.
3. Apply your own policy
Jev supplies a judgment. Your application remains responsible for authorization, thresholds, human review, and any external side effect.