API · Last updated 2026-09-21

Jev request format

The Jev request format is the JSON body for POST https://api.typesafe.ai/v1/systemone. Required top-level fields are state, model, and questions. Omitting a required field is a 422 class error. The documented header is Content-Type: application/json plus a bearer key — see content types if you were about to send multipart or form-encoded clones of a chat API.

This page is for builders wiring TypeSafe Jev (System One) into agents, routing, or evals. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. We do not sell or issue keys. Confirm field types on docs.typesafe.ai/api.

Top-level body

Field	Required	Role
`state`	Yes	String, object, or array of text
`model`	Yes	`jev-latest` or a versioned / preview alias
`questions`	Yes	Map of your IDs → question objects

state is text only. English is the primary training language. Pre-process images, audio, and video before the call. Unused object keys are billed as input (vendor list price: $0.042 / million input tokens, output free) and can distract jev-1.13.

Vendor-claimed context windows: 64k tokens for state + all questions; 32k for state + the longest question. Filter first.

Question object

Shared: type (choice | score | noul), instructions (string, object, or array).

Choice: criteria map, max 255 options, unordered.
Score: criteria array, 2–10 levels.
Noul: optional criteria.{true,false}.

The map key is echoed on the answer. It is not used in inference — question ids are not sent to the model. Write instructions a person could apply in seconds. Point at nested state with backtick paths when you use structured instructions.

Worked official example

{
  "state": "Help! My payouts have been failing for 3 days.",
  "model": "jev-latest",
  "questions": {
    "is_urgent": {
      "type": "noul",
      "instructions": "Does this convey urgency?"
    }
  }
}

For department routing and frustration scoring, copy the official quick-start multi-question body rather than inventing extra fields. Gotcha: jev-1.13 (no .0) is the marketing line, not a documented alias unless the models page lists it. jev-latest and jev-preview currently resolve to jev-1.13.0 — confirm.

Production pitfalls

Do not invent a sibling metadata bag that is free. Ticket ids belong in state if questions need them.
Do not send a documented batch file body. Many questions, one state, one POST. Multi-row files are your loop.
Do not put signing secrets or raw auth tokens in state.
Schema-safe questions still need your policy. A well-typed Choice is not automatically true in the world.
Gateway/OpenRouter wrappers may rename fields (boolean, input). Those are not this schema.

FAQ

Can I send images in state?

No. Text only.

Do unused state fields cost money?

Yes — billed as input (vendor claim). They can also distract jev-1.13.

Is there a documented batch body?

Many questions, one state, one POST. Multi-row files are your loop — batch pattern.

Are question ids prompts?

No. They key the response. Put the judgment in instructions and criteria.

What this page does not claim

Official TypeSafe status, logos, or support.
That jev.pro sells, issues, or proxies API keys.
Extra first-party HTTP routes beyond POST /v1/systemone and GET /v1/models unless the API reference lists them.
Invented latency SLOs, search volume, or unofficial prices. 1200 RPM and 250k tok/s are vendor claims.
That a schema-constrained answer is automatically factually correct.

Disclaimer

This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.

Sources

API reference