Docs
CommunityJev Integrations & Adapters
Concentrate Decisions API
Concentrate's beta /v1/decisions endpoint serves TypeSafe's Jev with the same request and response shapes as TypeSafe's System One API and OpenRouter, returning calibrated probabilities for noul, choice, and score questions.
- Format
- Docs
- Reading time
- 2 min
- Published by
- Community
- Author
- Concentrate
- Last verified
- Oct 2026
- Languages
- PythonJavaScript
- Platforms
- API
- Capabilities
- Requires API key
Highlights
- POST /v1/decisions at https://api.concentrate.ai/v1/decisions with a Bearer key; the examples use model jev-1.13.0.
- Request and response shapes match TypeSafe's System One API and OpenRouter's Decisions API; routing fields are ignored, not rejected.
- Noul returns a 0-to-1 probability, choice returns the option, a distribution, and confidence, and score takes one to ten ordered levels.
- The model returns canonically as typesafe/jev-1.13.0; a sample shows input_tokens 283 and output_tokens 23, and output tokens are not charged.
- The response id is the Response ID the logs page shows, which support asks for when you get in touch.
Watch out
The endpoint is in beta and is a third-party route to TypeSafe's model, so credentials, billing, and availability are Concentrate's. The recorded reference states no pricing, rate limits, or data-handling terms, and the model shown in every example is jev-1.13.0.
Questions about this entry
Short answers drawn from the linked project or page.
A calibrated probability for each question, not generated text. The body carries an id, the model in provider/model form such as typesafe/jev-1.13.0, answers keyed by your question ids, and usage with input and output token counts.
Three: noul for a yes/no probability, choice to pick one option from a map of option names to descriptions, and score to place the state on an ordered array of one to ten level descriptions.
Yes. Both accept structured JSON: a string, an object, or an array with any JSON values inside, so criteria can carry nested context rather than a single sentence. For a choice, an option description can be null when the name is self-explanatory.
No. The request and response shapes are identical to TypeSafe's System One API and OpenRouter's Decisions API, so a client written against either works by pointing it at /v1/decisions, and unimplemented fields such as routing are ignored.
It comes back in canonical provider/model form, for example typesafe/jev-1.13.0, and the id field is the Response ID shown on the logs page, which is what support asks for when troubleshooting.
No. A noul answer is just the probability of yes, because the probability is the answer; choice answers include optional confidence and a probability distribution, and score answers include a distribution, a legend, and confidence.
It details request parameters, the three question types, and response shapes, but states no pricing, rate limits, or redaction, ZDR, and HIPAA terms; those sidebar pages are outside the captured reference and stay unverified here.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
X: Jev 1.14 is now on OpenRouter
X: Jev lands on the Vercel AI Gateway
X: Jev as an LLM guardrail inside Agentgateway
YouTube: Greg Isenberg and Ryan Vogel on the businesses Jev unlocks, and a path in through the Vercel AI Gateway.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.