Skip to main content
Jev is TypeSafe’s flagship model and the first System One model. Every model on this page is served by the same endpoint, POST /v1/systemone. The request’s model field selects which one handles the call; see the API reference for the full request shape.

Current models

Jev 1.14 is the newest Jev release, available from October 14, 2026.
  • Price: You pay per input token. Output tokens are free. A Btok is a billion tokens and an Mtok is a million tokens.
  • Context length: Two limits, the per-request context and the per-question context. See Context length. To raise both, see Long context.
  • Input: Jev reads natural-language text, sent as a string, a JSON object, or an array of text values. It does not accept audio or video. Convert those into text or structured fields before you send them as state. See State for the shapes state accepts.

Context length

Jev ingests the state once and evaluates every question against it in parallel. A request has to fit two context limits:
  • Per-request context (per_request_context): the state plus all questions combined.
  • Per-question context (per_question_context): the state plus any one question.
There is no separate limit on the number of questions in a request. Any number of questions is allowed as long as the request fits both limits. See Speculative fan-out for packing many questions into one request, and Jev 1.13 jaggedness for how accuracy shifts as the state grows. To raise both limits, see Long context.

Long context

Long context is off by default and works on both Jev 1.14 and Jev 1.13. To turn it on, send the TypeSafe-Danger-Zone-Long-Context: true header with each request that needs it. With the header, the per-request context and the per-question context are both 262k tokens. Requests without the header keep the default limits in the table above.
Long context costs the same per token as any other request. It is slower and less accurate than staying within the default limits, so turn it on only for requests that need it.

Rate limits

Rate limits are set per organization. Your organization’s current limits are in the developer console. Limits are measured in tokens per second and requests per second. A request over either limit returns 429 Too Many Requests. Our client SDKs retry these requests by default, waiting longer between each attempt, and follow the retry-after header when the response includes one. If you call the HTTP API directly, see Handling rate limits. Higher limits are available on custom and enterprise plans. Contact sales@typesafe.ai.

Aliases

An alias is a model name that points to a versioned model ID. Send it in the model field the same way you send a model ID. An alias moves when a new release ships, so its answers can change without any change to your code. Each response’s model field gives the versioned ID that answered, so you can log which model produced each result. If you have tuned confidence thresholds against one version, send that version’s ID instead of the alias, and switch to the new version when you are ready.

Customizing Jev

Jev is not fine-tuned or LoRA-adapted with customer data. It is trained with RLCD to return calibrated decisions, and the same weights serve every account. You shape its answers to your domain through the request rather than through per-account weights:
  • Put your proprietary content, records, and reference material in the state field. See State.
  • Encode your domain rules and boundary cases in the instructions and criteria of each question. See How to build with TypeSafe and Advanced: structure.
  • Decompose broad judgments into atomic questions and combine the outputs in code. See Composite scoring and the AutoResearch cookbook for training a downstream classical model on Jev’s probabilities.

Language support

Jev accepts natural-language text. English is the primary training language and where accuracy is currently best. Other languages, including CJK scripts, are handled but not equally well; test on your own content before relying on Jev for a non-English workload, and pay close attention to Confidence when routing.

Data handling

Jev is not trained on customer requests or responses. See Legal for the Data Processing Agreement, the Privacy Policy, and details on zero data retention (ZDR) for enterprise customers.

Listing models

GET /v1/models returns the names your account can send in the model field, each with a description and a release date. It currently lists the aliases. Versioned IDs such as jev-1.14.0 are accepted by the model field whether or not they appear in the list.
array
required
One entry per model or alias.
See the Python and JavaScript SDK references for the full method signatures.