Getting started with JEV
Learn shared state, typed questions, and how to explore JEV online.
Last updated: 2026-09-28
Start with the right destination
This site provides an independent paid Playground for JEV through OpenRouter. It is not affiliated with TypeSafe AI, the model provider. Purchases here fund usage on this site; they do not purchase a provider account or provider API key. You can create a site API key to use the same balance from your own backend.
1. Prepare your context
The state field contains the information a decision should be based on. Start with one short, representative message, such as a support ticket. Every question shares this context. Avoid including personal information or secrets in an external demo.
Our Playground lets you edit an example and inspect JSON locally in your browser. Selecting Run sends your request to our backend and model providers and uses your purchased token balance.
2. Choose the question type
Choice: select from a set of options
Use choice when you have a finite set of destinations or categories. Its criteria is an object mapping option names to descriptions. A null description means the option name alone describes the option. Include an “other” option when your list might not cover every input. The community guide accepts 2–255 options.
Score: rate against ordered levels
Use score when the answer lies on a defined scale. Its criteria is an array of 2–10 descriptions, ordered from low to high. Levels start at 0; three levels represent 0–2. The returned score may lie between levels.
Noul: estimate the probability of yes
Use noul for a yes-probability question. Criteria can be omitted. If supplied, the community guide requires descriptions for both true and false. The noul value is a probability, not a Boolean or an additional confidence field.
3. Write a complete instruction
Put the meaning of your question in instructions, rather than relying on the question ID. For example: “Which team should handle this support ticket?” with billing, technical, and other as options. Clear categories and relevant context make your request easier to assess.
4. Inspect, copy, and try
Sign in, purchase tokens on the pricing page, and run your request in this Playground. Each question temporarily reserves 32,000 input tokens; completed requests settle against actual input usage, and output tokens are free. View deductions and remaining tokens on the usage page. Editing, copying, and downloading JSON do not consume tokens. Exported JSON is a request example, not an API credential.
To integrate this site into your application, follow the API usage guide for key authentication, copyable cURL/Python/Node.js examples, and error handling. The site API and Playground use the same token balance and the typesafe/jev-1.13 model.
5. Review the result
A structured response makes a decision easier for software to consume, but its format does not guarantee factual correctness. Check results against representative examples before using them in a workflow. Plan what should happen when the input is ambiguous or requires human review.
Further reading
- TypeSafe AI — official website
- Community parameter reference
- Community Playground
- Explore resources on this site
Questions about access
For purchases, balances, or Playground questions on this site, contact us. For accounts or purchases made directly with another provider, contact that provider.