What this Jev API endpoint provides
Jev is a TypeSafe System One decision model designed to answer bounded questions with typed outputs. The decisions-api.pro Jev API provides a hosted System One route at POST /v1/systemone. It authenticates with a Decisions API key and returns answers keyed by the question IDs in your request.
This hosted endpoint is a service integration. It is distinct from calling TypeSafe directly or using OpenRouter’s own API key and endpoint. Your usage, credentials, and account relationship depend on the route you choose.
Write questions around a defined answer space
Use Choice when your code needs one outcome from a finite set, Noul for a yes/no proposition, and Score for an ordered rubric. State can be text or structured JSON, and each question supplies instructions and criteria. Clear criteria make the result easier to validate and evaluate.
Call the Decisions API Jev endpoint
Create an API key in your Decisions API account, keep it in a server-side secret store, and send a bearer-authenticated request. The model alias shown below is the alias configured for this service; it is not a promise that the same identifier works with every Jev provider.
curl -X POST https://decisions-api.pro/v1/systemone \
-H "Authorization: Bearer $DECISIONS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"state": "A customer reports two charges for one order.",
"model": "jev-latest",
"questions": {
"route": {
"type": "choice",
"instructions": "Which team should handle this case?",
"criteria": {
"billing": "Payment, refund, or duplicate charge",
"technical": "Product malfunction or technical issue",
"account": "Login or account access"
}
}
}
}'Evaluate decisions before automating actions
Inspect the answer and probability fields, handle HTTP errors and insufficient credits, and choose thresholds using representative labeled data. A model response should not by itself authorize a refund, account change, or other consequential action; keep deterministic checks and human review where appropriate.