OpenRouter exposes a dedicated Decisions API route
OpenRouter documents Jev as a structured decision model and provides a dedicated alpha Decisions endpoint. The current direct route is POST https://openrouter.ai/api/alpha/decisions, with the OpenRouter model ID typesafe/jev-1.13. Use OpenRouter’s API key and consult its live API reference for current request requirements.
This route is separate from the familiar chat-completions endpoint. Requests contain state and typed questions, and results are returned as structured answers rather than generated chat prose.
POST https://openrouter.ai/api/alpha/decisions
Authorization: Bearer $OPENROUTER_API_KEY
Content-Type: application/json
{
"model": "typesafe/jev-1.13",
"state": "A customer reports two charges for one order.",
"questions": {
"is_duplicate_charge": {
"type": "noul",
"instructions": "Is this a duplicate charge report?",
"criteria": {
"true": "The customer describes multiple charges for one order",
"false": "The report does not describe a duplicate charge"
}
}
}
}Direct OpenRouter calls and Decisions API.pro are different routes
With a direct OpenRouter integration, your application sends requests to OpenRouter and manages its OpenRouter credentials and billing relationship. With decisions-api.pro, your application calls POST https://decisions-api.pro/v1/systemone using a Decisions API key; this service forwards the decision request to its configured provider and applies its own account and credit handling.
Choose one integration path based on your account, operational requirements, and pricing. The services are independent; Decisions API is not an OpenRouter product and does not imply endorsement or affiliation.
Validate probability signals for your application
Choice can select among developer-defined options, Noul expresses a yes probability, and Score maps the state to an ordered scale. Treat probabilities as model outputs to evaluate—not guarantees. Test on representative examples, select thresholds based on error costs, and retain human approval for high-impact actions.
Use the primary references for current API details
Provider APIs and model identifiers can change. Before shipping a direct OpenRouter client, verify the endpoint, schema, supported parameters, model availability, and current pricing against OpenRouter’s documentation and Jev’s current model listing.