---
title: How do I use TypeSafe Jev?
description: Connect TypeSafe Jev and run decision-model evaluators with Choice, Score, and Yes / no questions.
tags: [evaluation, decision-model-providers]
---

# How do I use TypeSafe Jev?

Add a connection with the adapter **typesafe**, choose the upstream that serves Jev, and paste its API key. Then select that connection in a [decision-model evaluator](/docs/evaluation/evaluation-methods/decision-models).

| Upstream          | API key                                                                             | Billing                   |
| ----------------- | ----------------------------------------------------------------------------------- | ------------------------- |
| TypeSafe          | A key from the [TypeSafe console](https://console.typesafe.ai/settings/keys)        | Billed by TypeSafe        |
| Vercel AI Gateway | An [AI Gateway API key](https://vercel.com/docs/ai-gateway/authentication-and-byok) | Billed through AI Gateway |
| OpenRouter        | An [OpenRouter API key](https://openrouter.ai/settings/keys)                        | Billed through OpenRouter |

These upstreams need no base URL or extra headers. Create an account at [typesafe.ai](https://typesafe.ai) to generate a TypeSafe key. Access currently runs through a waitlist on TypeSafe's side. If you already use Vercel AI Gateway or OpenRouter, pick that upstream instead and use its API key.

  Use `jev-latest` to follow new releases, or pin a version such as `jev-1.13.0`
  when an evaluation threshold should stay stable.

Build the JSON state from observation input, output, metadata, tool calls, **Expected Output**, or **Experiment Item Metadata**. Reference those fields in question instructions with backticks, for example ``Compare `output` with `expectedOutput`.`` Jev Score levels require a description.

TypeSafe accepts roughly 32k tokens for the state plus the longest question. Keep the input focused on the data needed for the decision. Jev always picks an answer, so add an `other` or `unclear` option when input may be thin.

  TypeSafe connections are only available to decision-model evaluators because
  Jev cannot generate text.

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/faq/all/decision-model-typesafe-jev.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx @langfuse/cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.
