Try Jev in your browser
Best for: Learning what Jev returns before creating an API account.
- No visitor signup or API key
- Real Jev model
- Editable State and typed Questions
- Visible answer probabilities
JEV GETTING STARTED
You can try Jev online, call it through the TypeSafe API, use an official SDK, or give your coding agent the TypeSafe skill. Choose the path that matches what you want to do.
00 / START HERE
Start in the browser to understand the output, or move directly to the integration path that matches your project. The no-signup note applies to this independent Jev Playground tutorial; Direct API and SDK access require your own TypeSafe account and API key.
Best for: Learning what Jev returns before creating an API account.
Best for: Server-side integrations and production workflows.
POST https://api.typesafe.ai/v1/systemonejev-latestBearer API keyTypeSafe account → check API-key access → first request
Best for: Python or JavaScript/TypeScript applications.
pip install typesafe-sdknpm install @typesafe-ai/sdkBoth official clients read TYPESAFE_API_KEY from the environment.
Best for: Building a Jev integration with Codex, Claude Code, or another supported coding agent.
npx skills add typesafe-ai/skills --skill typesafe-aiclaude plugin marketplace add typesafe-ai/skills
claude plugin install typesafe@typesafe-aiThe skill teaches the coding agent current TypeSafe API patterns and integration conventions. It does not turn Jev into a coding agent.
Trying Jev here uses this independent Playground's server-side access, so visitors need neither a signup nor an API key. Building with TypeSafe Direct starts at the TypeSafe Console and requires an account with API-key access. TypeSafe's September 15 launch announcement described early access and a waitlist; today its SDK docs link directly to key creation. That does not establish immediate API access for every account.
Jev is hosted: there is no TypeSafe Jev model to download for local use. HTTP needs no SDK; the Python and JavaScript SDKs are client libraries, and the Agent Skill gives a coding agent integration guidance. None is the model itself.
| Goal | Start here |
|---|---|
| I just want to try Jev | Jev Playground |
| I want to add Jev to my app | TypeSafe API |
| I write Python or JavaScript | Official SDK |
| I want Codex/Claude to help integrate it | TypeSafe Agent Skill (opens in a new tab) |
LIVE PLAYGROUND TUTORIAL
The rest of this tutorial teaches State, Question, decision types, probabilities, and the application boundary through the live browser Playground. For API or SDK integration, use the paths above.
No TypeSafe account is needed for this Jev Playground tutorial.
For a worked agent-history decision, try the editable Context Compaction tool.
For a bounded code-change review, screen an editable diff and inspect original hunks.
To find evidence in text you provide, search original passages without a generated answer.
LIVE PLAYGROUND TUTORIAL · 01 / RUN YOUR FIRST DECISION
The Support Routing example is already loaded. Its State describes a duplicate subscription charge. Its Choice question asks which team should handle the request, with four allowed answers. No setup. No TypeSafe account. Example ready.
The example is already filled in. Click Run Jev first. You do not need to change anything.
Give Jev a state and a typed question.
Run it to see the decision and probabilities.
Run the loaded example, then edit the inputs or choose another example to experiment.
The Playground sent the visible State and typed Question to the real Jev model. Jev selected one of the four choices and returned its probability distribution. The result panel renders that live response; this tutorial does not predict or hard-code the answer. Actual probabilities can vary between evaluations.
02 / WRITE THE STATE
State describes the situation at decision time. Include the facts that separate one answer from another. Clear evidence matters more than length; you do not need prompting tricks or a long persona.
“The customer says they were charged twice for their monthly subscription and wants one duplicate charge refunded.”
Names the event, product context, and requested outcome.“A customer has a problem. Think carefully and act as an expert support manager.”
Adds a role, but leaves out the evidence needed to route the request.03 / ASK ONE DECISION
A good Question has a decision your application recognizes. Ask what you need to choose, verify, or score—not for an essay about the situation.
“Which team should handle this customer request?”
One decision, paired with Billing, Technical, Sales, and Other.“Tell me what you think.”
Combines classification and response writing without a bounded answer.04 / CHOOSE THE ANSWER TYPE
Use for a proposition such as “Was a refund issued?” The result is P(true), shown as Yes and No probabilities.
Use for routing or classification. You define 2–10 distinct choices; Jev selects one and may return probabilities for them.
Use an ordered rubric. This Playground uses five named levels, from 0 to 4; Jev may return a fractional score between them.
Jev Playground presents yes/no judgments as Boolean. TypeSafe's Direct API calls the native yes/no primitive Noul. The Playground keeps Boolean in its interface; there is no Noul button here. Compare the API question types.
05 / READ PROBABILITIES
Probabilities show Jev’s distribution over the allowed answers. They express its estimated preference among those answers; they are not a guarantee of correctness. Your application decides when to act, ask for review, or gather more evidence based on its own risk, costs, and evaluation results.
Illustrative distributions for reading the interface; they are not saved Jev results or recommended universal thresholds.
06 / TRY YOUR OWN INPUT
Return to the live Playground, keep Support Routing selected, and replace the State and Question below. Run it again, then compare the returned choice and distribution with your first run.
“My account is locked and I cannot sign in.”
Changing one fact at a time makes the comparison easier to understand. The exercise does not prescribe which option Jev must select.
NEXT / TRY THE OTHER PRESETS
Evaluates how likely it is that the supplied state says a refund was issued.
Places an incident on an ordered rubric from No urgency to Critical.
Both presets are already available above. Select one, read its State and Question, then run it as-is before editing.
07 / ASK MORE THAN ONE QUESTION
In the Playground, choose Multiple questions and load Agent Action Gate. The preset sends one shared State with three independent questions: whether important data is at risk, whether confirmation is required, and which next action to choose.
One answer is not automatically used as context for another. Your software combines the returned decisions under its own policy. See the browser agent worked example for a complete decision boundary.
08 / JEV DECIDES. SOFTWARE ACTS.
Chooses Billing
YOUR SOFTWAREAssigns the ticket after checking queue rules.
Returns a high P(true) for refund issued
YOUR SOFTWAREShows the status or requests review; it does not issue money.
Returns CLICK e3
BROWSER CODEValidates the current page and performs the click.
09 / COMMON MISTAKES
30-SECOND CHEAT SHEET
BEGINNER FAQ
Try it online in this no-signup Playground, call the Direct API with a TypeSafe account and API key, use an official Python or JavaScript SDK, or give a supported coding agent the official TypeSafe skill.
Yes. Jev Playground lets you use the interactive tutorial without supplying a TypeSafe account or API key. Usage limits apply. Try Jev now.
No. Jev Playground provides its own server-side access for this interactive tutorial.
Yes. Direct TypeSafe API access requires your own TypeSafe account and API key. Open the Jev API guide.
Sign in at the TypeSafe Console. The September 15 launch described early access and a waitlist; current docs link to API-key creation, but Direct API availability depends on your TypeSafe account.
The hosted Jev model does not require local installation. Raw HTTP needs no SDK; Python uses typesafe-sdk, JavaScript uses @typesafe-ai/sdk, and coding agents can optionally install the official TypeSafe Agent Skill.
No. Jev evaluates supplied State against typed Questions and returns bounded answers with probabilities. Read What Is Jev.
Yes, within this independent Playground’s usage limits. TypeSafe API usage has separate published pricing. See Jev pricing.
State is the information Jev reads before deciding, such as a customer message, incident report, record, agent status, or page description.
Choice selects one supplied option. Boolean is Jev Playground’s yes/no surface and returns P(true); the TypeSafe Direct API calls its native yes/no primitive Noul. Compare the API types.
It means the displayed distribution strongly favors that answer after rounding. It is not a guarantee that the answer is correct.
Yes. Multiple Questions mode sends focused Questions with one shared State. Jev evaluates each independently; your application decides how to combine the answers. See the browser agent example.
Jev returns decisions. Your software validates permissions and policy, chooses any threshold or review path, and performs the action.
The Jev API guide covers authentication, request contracts, SDK examples, response handling, and errors. Open the Jev API guide.
READY TO BUILD?
The API guide covers the real request contract, server-side key handling, response shapes, and failure states.
Read the Jev API guide