LAB / 01 · TYPED DECISIONS
See how Jev AI helps apps decide what to do next
Jev returns a category, score, or probability for questions about your input. Your application rules decide what to do with those answers. Try a customer message example, then explore routing, context selection, and evidence checks.
- 3answer types
- 6interactive experiments
- 18linked public projects
Independent lab · No account required · Synthetic samples included

LAB / 02 · TRY JEV
Try Jev on a customer message
Start with the prepared message and run it as-is, or replace it with your own. No account is required.
YOUR INPUT
A customer message
JEV WILL ANSWER
What is this customer message primarily about? If several topics appear, choose the one tied to the customer’s main request.
choiceHow urgent is the customer’s need, based only on the impact and timing stated in the message?
scoreDoes the customer still have an unresolved problem or an explicit request that needs a follow-up?
booleanEdit questions Answer types stay fixed
- BILLCharges, payments, invoices, refunds, pricing, or subscription billing.
- TECHA product feature is broken, failing, unavailable, or behaving unexpectedly.
- ACCOSign-in, password, profile, access, permissions, or account administration.
- OTHEThe main topic does not fit billing, technical support, or account administration.
- 0No action is needed.
- 1A routine question or low-impact request.
- 2A problem affects use, but no clear deadline or major blockage is stated.
- 3Core work is blocked or a near-term deadline is stated.
- 4A severe outage, active loss, or similarly serious interruption is happening now.
- TThe message contains an unresolved issue, unanswered question, or explicit request.
- FThe message says the matter is resolved or contains no request requiring a response.
JEV’S ANSWERS
Category, urgency, and follow-up
Probability-weighted rubric position, not a percentage or confidence score.
- 0
No action is needed.
- 1
A routine question or low-impact request.
- 2
A problem affects use, but no clear deadline or major blockage is stated.
- 3
Core work is blocked or a near-term deadline is stated.
- 4
A severe outage, active loss, or similarly serious interruption is happening now.
Jev returns typed signals your support system can use. This example does not send a reply or create a ticket.
View JSON & provider details +
PROVIDER CONFIDENCE · SEPARATE FROM ANSWER PROBABILITY
Message category 79%Urgency 62%{
"origin": "illustrative-example",
"input": {
"message": "I was charged twice for this month’s subscription. Could you check the second charge and refund it?"
},
"questions": {
"category": {
"type": "choice",
"instructions": "What is this customer message primarily about? If several topics appear, choose the one tied to the customer’s main request.",
"criteria": {
"billing": "Charges, payments, invoices, refunds, pricing, or subscription billing.",
"technical-support": "A product feature is broken, failing, unavailable, or behaving unexpectedly.",
"account": "Sign-in, password, profile, access, permissions, or account administration.",
"other": "The main topic does not fit billing, technical support, or account administration."
}
},
"urgency": {
"type": "score",
"instructions": "How urgent is the customer’s need, based only on the impact and timing stated in the message?",
"criteria": [
"No action is needed.",
"A routine question or low-impact request.",
"A problem affects use, but no clear deadline or major blockage is stated.",
"Core work is blocked or a near-term deadline is stated.",
"A severe outage, active loss, or similarly serious interruption is happening now."
]
},
"needsFollowUp": {
"type": "boolean",
"instructions": "Does the customer still have an unresolved problem or an explicit request that needs a follow-up?",
"criteria": {
"true": "The message contains an unresolved issue, unanswered question, or explicit request.",
"false": "The message says the matter is resolved or contains no request requiring a response."
}
}
},
"answers": {
"category": {
"type": "choice",
"choice": "billing",
"probabilities": {
"billing": 0.88,
"technical-support": 0.03,
"account": 0.05,
"other": 0.04
}
},
"urgency": {
"type": "score",
"score": 2.4,
"probabilities": {
"0": 0.01,
"1": 0.08,
"2": 0.48,
"3": 0.36,
"4": 0.07
}
},
"needsFollowUp": {
"type": "boolean",
"probability": 0.97
}
},
"providerConfidence": {
"category": 0.79,
"urgency": 0.62
},
"run": null
}LAB / 03 · WHAT IT IS
What the Jev model does
Many applications need a specific answer: a category, a score, or an estimate of whether something is true. A chat model can answer in prose, but the application then has to extract the value it needs.
With Jev, you provide an input — such as a ticket, message, draft, or proposed tool call — and define the questions it should answer. Jev returns values in the requested answer types, without a paragraph to parse.
You can inspect the returned values and probabilities. Your own code decides whether to act, ask for review, or do nothing.
LAB / 04 · THE THREE QUESTIONS
The three answer types
Jev returns
Ask multiple questions about the same input in one call.
Choice: pick an option
Pick one option from a named set you define — which team owns this ticket, which tool the agent should reach for next, which of your routes fits. You get the selection plus a probability across every candidate.
Up to 255 options.
Score: rate on a scale
Place the state on an ordered rubric you write out in plain language, from lowest to highest. Useful for severity, urgency, risk, or quality. The result can land between levels, because it is a probability-weighted position rather than a single pick.
Rubrics of 2–10 levels.
Boolean: estimate yes or no
Estimate how likely a statement is to be true. You get a number between 0 and 1, not a flat yes — 0.97 and 0.51 mean very different things to a policy, and collapsing them to true throws away the part that mattered.
Probability, not a verdict.
LAB / 05 · HOW IT WORKS
How to use Jev answers in your app
- 1
Provide input and questions
Send the data Jev should evaluate and define the choices, scoring scale, or yes-or-no questions you need answered.
- 2
Review answers and probabilities
Look at the selected value and its probabilities separately from any confidence information returned by the provider.
- 3
Decide what your app does
Set thresholds in your code. You can change whether an answer triggers an action or human review without running the model again.
LAB / 06 · FIT
When Jev AI is useful
Jev is useful when an application repeatedly needs to choose from defined options, score an input, or estimate a yes-or-no answer. Test its answers against your own examples before using them in a workflow.
- Routing and triage. Send a ticket, email, or event to the right queue, with low-confidence cases held back for a person.
- Agent next steps. Evaluate which tool to use next, or whether an agent should retry, ask for help, or stop.
- Review before an action. Flag a proposed tool call for confirmation or review before your application executes it.
- Content checks. Ask several classification or scoring questions about one message in a single call.
LAB / 07 · EXAMPLES
Explore six interactive Jev examples
IDEA / REVIEW
Check a Startup Idea's Assumptions
Enter a startup idea to see which customer, problem, and differentiation claims still need evidence. This does not predict success.
DRAFT / REVIEW
Check a Draft's Tone and Clarity
Enter a draft to see scores for tone and clarity, then compare versions. The tool does not rewrite your text.
AGENT / SIMULATOR
Simulate an Agent's Next Action
Choose a goal in a fictional settings app and watch Jev select the next allowed action, for up to six steps.
TASK / ROUTING
Route a Task to the Right Path
Enter a task to see which route Jev selects and whether your app rules allow that route or require review.
CONTEXT / SELECTION
Select Relevant Context
Enter a task and context blocks to see which blocks stay relevant. Required instructions remain pinned.
CLAIM / EVIDENCE
Compare a Claim with Supplied Evidence
Enter a claim and evidence you provide to see whether the evidence supports, contradicts, or does not address it. The tool does not search the web.
LAB / 08 · START BUILDING
Use Jev AI with TypeScript
Call Jev through AI SDK 7’s evaluation interface and read its structured answers directly. Keep the rules that decide your application’s next action in your own TypeScript code.
Read the quickstartimport { experimental_evaluate as evaluate } from 'ai';
const result = await evaluate({
model: 'typesafe-ai/jev',
state: { task, routingContext },
questions: { route, complexity, externalSideEffect },
maxRetries: 0,
});
// Model signal ≠ application authority
const action = applyPolicy(result.answers);LAB / 09 · COMMON QUESTIONS
Common questions about Jev
What is Jev AI?
Jev is an evaluation model from TypeSafe AI, released in September 2026. It reads text or structured data you provide and returns a choice, a score on a defined scale, or a probability for a yes-or-no question. Your application can use those answers to decide what happens next. Jev AI Tools is this independent site for trying it.
How is Jev AI different from GPT or Claude?
Chat models produce text, which an application may need to parse before using. Jev returns a choice, score, or probability directly. It is suited to those defined answer types; use a text-generating model when you need a summary, explanation, or draft.
Can I try the model here without an account?
Yes. You can inspect the sample results without an account. When Live runs are available, anonymous visitors receive 10 trial credits. Live availability also depends on the site's shared service limits.
When should I use a different model?
Use a text-generating model for summaries, rewrites, explanations, code, or open-ended answers. Jev evaluates supplied text or structured data; it does not interpret images. Choice questions allow up to 255 options, and scoring scales have two to ten levels.
LAB / 10 · PUBLIC PROJECTS
Public projects using Jev
These links lead to projects and demos by other authors. This site has not reproduced their results.
Browse the ecosystem