Typed questions
Use Choice, Score, or Noul to define the answer space before the request reaches the model.
Jev AI API
Jev AI API turns application state into typed decisions, probabilities, and confidence signals your backend can use for routing, scoring, guardrails, and review.
INPUT STATE
Three deploys have failed and production is returning 500s.
choiceClassify the next action
confidenceProbability-backed signal
needs_humanEscalate when risk is high
One state. Multiple typed questions. A response your code can inspect.
Build with the API
Start with a real state, define the smallest useful question, and pass the structured result into the service that already owns the next action.
POST /v1/systemone
A minimal server-side request to the Jev AI API
curl -X POST https://thejevai.com/v1/systemone \
-H "Authorization: Bearer $JEV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "typesafe/jev-1.13",
"state": "Three deploys failed and production is returning 500s.",
"questions": {
"needs_human": {
"type": "noul",
"instructions": "Does this need human review now?"
}
}
}'
// Read data.result.answers.needs_human.noul
// and data.creditsUsed in your serviceOne request, clear output
Start with state, choose a Jev model, and describe the questions your product needs answered. The result comes back in a predictable shape for routing, scoring, guardrails, and review.
Use Choice, Score, or Noul to define the answer space before the request reaches the model.
Create and rotate keys from your Jev workspace, then keep them in server-side environment variables.
Inspect credits used and request usage so you can estimate the cost of a workflow before expanding it.
Read answers by question ID and let your own code decide whether to route, queue, block, or ask a person.
Ask several related questions against the same state without chaining separate calls for every signal.
Use Jev for bounded judgment while your service owns authentication, thresholds, retries, and final actions.
From input to action
Jev handles the judgment in the middle. Your existing services still choose the model, apply policy, and decide when a person needs to step in.
Use Jev Playground with a real low-risk state and refine the question until the output is useful.
Create a key in your Jev workspace and store it outside source code, browser bundles, and logs.
Use probabilities and confidence as signals, while your permissions, thresholds, and business rules own the final action.
Jev AI API questions
The Jev AI API turns a state plus typed questions into structured decisions, probabilities, and confidence signals that your backend can route, score, review, or use in guardrails.
Jev supports Choice for classification and routing, Score for ordered ratings, and Noul for yes-or-no decisions. Multiple questions can be evaluated against the same state in one request.
No. Jev provides a bounded judgment. Your application remains responsible for authentication, thresholds, retries, permissions, audit logs, and the final action.
Jev AI platform
Start with one controlled decision.
Jev performs the bounded judgment. Your service remains responsible for authentication, input minimization, retries, rate-limit handling, thresholds, audit logs, and the final action.