Skip to main content

TypeSafe Jev API

Jev is TypeSafe’s System One model. It does not generate text: you send content and typed questions, and get answers with probabilities (and confidence where applicable). Programs can branch on those scores without parsing prose. Host: https://api.omniall.ai · Auth Authorization: Bearer sk-...
Models: jev-1.14.0 · jev-preview · jev-latest
Full schemas and playground: API Reference → Chat → TypeSafe / Jev.

Question types

One request can mix types. Extra questions do not change other answers — each question is independent over the same content.

Quick start (TypeSafe official)

TypeSafe SDK: set base_url to https://api.omniall.ai/typesafe (key = your Omniall API key).

Quick start (OpenAI Decisions)

OpenAI SDK (openai Python ≥ 3.26 / JS ≥ 7.30): base_url=https://api.omniall.ai/v1, then client.decisions.create(...).

When to use it

  • Ticket / form routing (team or next action)
  • Priority and risk scoring
  • Moderation / output checks (compliance, grounded citations)
  • Agent control (which tool to call, whether to escalate)
Use probability and confidence thresholds: high confidence → automate; low → human review.

Limits & tips

  • Default context: 64k tokens; state/input + longest question ≤ 32k. Optional header TypeSafe-Danger-Zone-Long-Context: true raises both to 262k (preview; slower / less accurate).
  • Images: TypeSafe official needs TypeSafe-Danger-Zone-Images: true + assets; Decisions can send input_image (auto-enables images). PNG/JPEG only; 256–1568 px per side; ≤ 16 MiB each.
  • English works best; other languages are usable but less accurate — validate on your data.
  • Probabilities are rounded to two decimals; sums may be 0.99 instead of 1.0 — no need to renormalize.
Admin channel setup: create a TypeSafe channel (type 68), Base URL https://api.ephone.ai (or your upstream), and enable jev-* models for the user group.