# What is Jev? A simple guide to Jev AI

A plain-English guide to the AI model that helps software choose what happens next.

> By Saad Bin Shafiq, founder of Nodes · Sep 19, 2026
> Canonical: https://www.nodes.inc/blog/what-is-jev-ai

**Answer:** Jev is an AI model from TypeSafe AI that helps software make decisions. Give it text and a clear question, and it returns a choice, a score, or a probability. For example, it can help decide which team should handle a customer message. Your software then decides what to do with that answer.

---
TypeSafe describes Jev as a model for focused decisions inside software. You supply the information and define the question; the application receives an answer it can use for its next step. [TypeSafe introduction](https://docs.typesafe.ai/introduction).

You can understand the idea without writing code. Start with a message that a business receives every day.

## What does Jev do? A simple example

A customer sends this message:

> My card was charged twice. Please help me get the extra payment back.

Your support software needs to decide where to send it. You give Jev the message and ask: which team should handle this?

You also provide the allowed answers: billing, technical support, sales, or needs review.

In this example, billing is the sensible choice. The software could then put the message in the billing queue. A person checks the account and decides whether a refund is due.

That is an illustration, not a result from a live Jev test. The distinction matters: understanding a refund request does not prove that a duplicate charge happened or that a refund is allowed.

Jev handles a small judgment inside the process. The rest of the process still needs records, rules and someone responsible for exceptions.

## Who made Jev?

TypeSafe AI announced Jev in early access on September 15, 2026. The company calls it its first public **System One model**. [TypeSafe launch announcement](https://typesafe.ai/blog/introducing-system-one-models-and-jev).

System One is TypeSafe's name for models built to answer focused questions inside software. Think of the quick judgment a person might make when reading a short message: is this about a payment, or is the customer having trouble logging in?

The model takes the information you supply and evaluates the question. TypeSafe calls that supplied information the **state**. In our example, the state is the customer's message. [System One documentation](https://docs.typesafe.ai/concepts/system-one).

You do not need to learn the terminology to get started. The basic pattern is: information in, question asked, answer returned.

## How does Jev work?

You define the kind of answer you need before making the request. Jev supports three question types:

| Type | What it answers | Example |
|---|---|---|
| Choice | Which option fits? | Billing, technical support, sales, or needs review |
| Score | Where does this fall on a scale you define? | Calm, frustrated, or very upset |
| Noul | How likely is the answer to be yes? | Is the customer asking for a refund? |

For a Choice, Jev returns the selected option and probabilities for the options. For a Score, it returns a number along your defined scale, which can fall between levels. Both include a confidence value.

A Noul returns a number from zero to one. Near one means the model thinks yes is likely. Near zero means no is likely. Near the middle means uncertainty. It has no separate confidence field.

You can ask several questions about the same message in one request. Each question is evaluated independently against the supplied information. [Question types and answers](https://docs.typesafe.ai/primitives).

## Jev vs a chatbot: what is the difference?

Jev returns answers in a form your application can use directly. It does not write an email, produce a paragraph explaining its reasoning, or generate an app. TypeSafe documents those limits in its [System One guide](https://docs.typesafe.ai/concepts/system-one).

Choose the tool based on the result you need:

| Your task | A useful approach |
|---|---|
| Pick a support queue from an agreed list | Try Jev |
| Draft a helpful reply to the customer | Use a text-generating model |
| Calculate the amount of a duplicate payment | Use ordinary code and payment records |
| Decide whether a refund is permitted | Apply the business's rules and required review |

These parts can work together. Jev might suggest the queue. A writing model might draft a reply. The help desk stores the case, and the billing team checks the payment.

You do not have to replace your whole system to test one of those steps.

## How to use Jev: a beginner's guide

### 1. Open the playground

Start with TypeSafe's [quick-start guide](https://docs.typesafe.ai/introduction/quickstart) and follow its link to the playground. Sign in. TypeSafe launched with early access, and its [website](https://typesafe.ai/) still shows a waitlist as of September 19, 2026. Access may depend on your account.

The playground is the easiest place to see what a question produces before connecting it to an application.

### 2. Paste a sample message

Use a made-up message for your first experiment. The duplicate-charge example above is enough.

Put it in the state field. Avoid adding a long company history or unrelated documents. Give the model what it needs to answer this question.

### 3. Ask one clear question

Choose a Choice question. Ask which support queue should receive the message.

Define the options in plain language:

- **Billing:** charges, invoices, payments and refunds.
- **Technical support:** broken features or problems using the product.
- **Sales:** questions about buying the product.
- **Needs review:** unclear requests or messages that do not fit another queue.

The last option gives the model somewhere useful to put a message that does not fit. Otherwise, you are asking it to choose among answers that may all be unsuitable.

### 4. Check the result against your own answer

Look at the choice and the probabilities. Then change the message and try again.

For example, try a login problem, a pricing question, and a message that mentions both a payment and a broken feature. Include a vague request such as “Can someone help me?”

Decide how you want those cases handled before judging the model. If your own team disagrees on the correct queue, clarify the routing rule first.

### 5. Connect it to software after testing

Developers can get an API key from TypeSafe's dashboard and call its API. An API is the way one program asks another service to do something. TypeSafe provides Python and JavaScript clients, plus a direct HTTP example in its quick-start guide.

Start by recording Jev's suggested queue beside the queue your team chooses. This lets you find mistakes before the suggestions control routing. Keep a review path for unclear cases.

## How much does Jev cost?

As checked on September 19, 2026, TypeSafe lists **$0.042 per million input tokens**, with **free output tokens**. Tokens are small pieces of text that the service uses to measure input. They are not the same as words. [Current models and pricing](https://docs.typesafe.ai/models).

The input includes the information and questions you send. A longer request costs more than a shorter one. Free output does not mean the whole request is free.

Treat the API bill as one part of the cost. Connecting a help desk, checking errors and handling exceptions also take work. For a first trial, measure how many messages reach the right team and how much correction the process needs.

**How fast is Jev?**

TypeSafe reports response times of 70 to 500 milliseconds in its launch material. Those are vendor-reported results, and your experience can vary with the request and network conditions.

The company also publishes large speed and cost comparisons from its own workflow evaluations. It says the headline gains are likely toward the high end of real-world gains. [Launch results and caveats](https://typesafe.ai/blog/introducing-system-one-models-and-jev).

For the support example, test the time from receiving a message to putting it in the correct queue. That is the delay your team experiences.

## Can Jev make mistakes?

Yes. Returning an allowed answer does not make that answer correct.

TypeSafe documents weaknesses with arithmetic, counting and date comparisons. It also warns that irrelevant information and text written to steer the model can affect answers. Keep exact calculations in code and test difficult examples. [Published limitations](https://docs.typesafe.ai/model-jaggedness/jev-1.13).

Confidence needs care too. For Choice and Score, it summarizes how concentrated the probabilities are. It is not a guarantee that an answer is right. Set your review rules using results from your own task. [How confidence works](https://docs.typesafe.ai/confidence).

For our billing example, a confident classification can help send the message to the right team. Permission to issue a refund comes from the business's rules.

## Frequently asked questions about Jev AI

**Can Jev read images or listen to audio?**

The current model accepts text. Images, audio and video need to be converted into text or suitable fields before Jev evaluates them. See TypeSafe's [input specifications](https://docs.typesafe.ai/models).

**Can Jev replace an AI agent?**

Jev can supply a decision within an agent's workflow. The surrounding application still needs to manage tools, actions and the information needed for the next step. Start with a narrow job such as choosing among available handlers.

**Do I need a knowledge graph to use Jev?**

No. A single message is enough for the example in this guide. A [knowledge graph](/blog/what-is-a-knowledge-graph) becomes relevant when a question needs connected company records and history. Our guide to [the context layer](/blog/context-layer-is-the-moat) explains why that information matters alongside model quality.

## Where does Jev fit into a business workflow?

At Nodes, the practical question is what the whole process needs to make a useful decision. You can inspect that broader approach on our [platform page](/platform). For a Jev experiment, begin with one queue, clear options and examples your team can check.

## Sources

Product details were checked against TypeSafe's documentation on September 19, 2026. The support scenario is illustrative; this guide does not report a hands-on benchmark or a Nodes integration with Jev.

- [Introduction](https://docs.typesafe.ai/introduction)
- [Launch announcement and performance caveats](https://typesafe.ai/blog/introducing-system-one-models-and-jev)
- [Question types](https://docs.typesafe.ai/primitives)
- [Quick start](https://docs.typesafe.ai/introduction/quickstart)
- [Models and pricing](https://docs.typesafe.ai/models)
- [Confidence](https://docs.typesafe.ai/confidence)
- [Known limitations](https://docs.typesafe.ai/model-jaggedness/jev-1.13)
- [System One](https://docs.typesafe.ai/concepts/system-one)

*Saad Bin Shafiq is the founder of Nodes, serving data-sensitive enterprises.*