API
Endpoint, request shape, SDKs, aliases, and the first working call.
Jev API Action Fields | TypeSafe Jev System One
Actions are verbs your code executes after Jev answers. The API does not document an action field that runs tools.
Jev API Api Testing | TypeSafe Jev System One
Test Jev integrations with the Playground, official examples, and fixture-based contract tests — not live keys on jev.pro.
Jev API Async Jobs | TypeSafe Jev System One
Async Jev jobs are your workers. The public API is a synchronous POST /v1/systemone.
Jev API Batch Endpoint | TypeSafe Jev System One
There is no documented Jev batch HTTP endpoint — batch many questions or loop states yourself.
Jev API Bulk Imports | TypeSafe Jev System One
Bulk import of states is your ETL plus a paced loop of official evaluation calls.
Jev API Cite Endpoint | TypeSafe Jev System One
Citation checks are Choice questions over source text. No documented Jev cite endpoint.
Jev API Classify Endpoint | TypeSafe Jev System One
Classification uses Choice (or Noul) on POST /v1/systemone — not a separate classify URL.
Jev API Confidence Fields | TypeSafe Jev System One
Choice and Score answers include confidence and probabilities. Noul returns only noul.
Jev API Content Types | TypeSafe Jev System One
Jev evaluation requests use application/json. State is text-shaped JSON — no image or audio content types.
Jev API decision endpoint
POST /v1/systemone field table, jev-1.13 vs jev-1.13.0, and what the response model id means. Cite docs.typesafe.ai only.
Jev API error envelope
JSON error body plus a symptom tree. 402 and customer_verification are channel callouts, not a cloned per-status IA.
Jev API Evaluate Endpoint | TypeSafe Jev System One
Evaluate with the documented System One route. An extra /evaluate URL is not in the public API reference.
Jev API Evidence Fields | TypeSafe Jev System One
Evidence lives in state you send. Jev responses do not document a separate evidence array.
Jev API Explain Endpoint | TypeSafe Jev System One
Jev does not document an explain endpoint. It does not generate reasoning text — log probabilities instead.
Jev API Extract Endpoint | TypeSafe Jev System One
Extraction is a cookbook pattern (candidates in code, Jev selects). No documented extract HTTP route.
Jev API Feedback Endpoint | TypeSafe Jev System One
No documented Jev feedback HTTP route. Store reviewer labels in your system; Jev is not fine-tuned per customer.
Jev API Health Endpoint | TypeSafe Jev System One
TypeSafe does not document a public Jev health route — probe via GET /v1/models or a canary evaluation.
Jev API Human Review Fields | TypeSafe Jev System One
Human-review fields belong in your review API. Jev returns confidence you can use to hold a case.
Jev API Idempotency Keys | TypeSafe Jev System One
Idempotency for Jev is an application concern — the public API reference does not document idempotency keys.
Jev API Metadata Fields | TypeSafe Jev System One
Put your metadata in state or in your database. The public Jev request schema does not document a metadata bag that changes inference.
Jev API Moderate Endpoint | TypeSafe Jev System One
Moderation is Choice/Noul/Score questions you define — there is no documented Jev moderate endpoint.
Jev API Pagination | TypeSafe Jev System One
System One responses are not paginated. List-style pagination is not documented on the evaluation API.
Jev API Policy Endpoint | TypeSafe Jev System One
Policy decisions are your rules on Jev answers. No documented policy HTTP endpoint.
Jev API Rate Limits | TypeSafe Jev System One
Published Jev rate limits: 250,000 tokens/second and 1,200 requests/minute. 429 when exceeded; limits can change.
Jev API Replay Endpoint | TypeSafe Jev System One
Replay a Jev decision by storing the original request and calling POST /v1/systemone again. No documented replay route.
Jev API request schema
Developer field table for state, model, and questions — including structured instructions and jev-1.13 vs jev-1.13.0.
Jev API Response Schema | TypeSafe Jev System One
Learn the documented Jev response schema: resolved model, answers map, and token usage.
Jev API response shape
OpenAPI-style map of Jev answers: noul, choice, score, usage, and the jev-1.13 vs jev-1.13.0 model field.
Jev API Retry Semantics | TypeSafe Jev System One
Retry Jev 429 and 529 with exponential backoff. Official SDKs implement RetryPolicy; do not retry 401 or 422.
Jev API Route Endpoint | TypeSafe Jev System One
Routing is an application pattern: Jev Choice/Noul plus your handlers. No documented /route endpoint.
Jev API Score Endpoint | TypeSafe Jev System One
Scoring uses the Score primitive on the System One endpoint, not a dedicated score HTTP route.
Jev API Sdk Integration | TypeSafe Jev System One
Integrate official TypeSafe SDKs: typesafe-sdk (Python) and @typesafe-ai/sdk (JavaScript).
Jev API Search Endpoint | TypeSafe Jev System One
Jev is not a search API. Use your retriever, then score hits with System One questions.
Jev API Status Endpoint | TypeSafe Jev System One
There is no documented Jev job-status endpoint. Persist status in your store after POST /v1/systemone.
Jev API Streaming Endpoint | TypeSafe Jev System One
Jev has no documented streaming evaluation endpoint. Use the synchronous System One JSON response.
Jev API Timeouts | TypeSafe Jev System One
Configure Jev client timeouts via official SDKs. The HTTP error table does not define a timeout status code.
Jev API Trace Identifiers | TypeSafe Jev System One
Trace Jev calls with your correlation ids. The public API does not document a required trace header.
Jev API Validate Endpoint | TypeSafe Jev System One
Validation is 422 on the wire plus your own checks. No documented Jev validate endpoint.
Jev API Versioning | TypeSafe Jev System One
Jev versioning: /v1/ on the HTTP path and jev-* model aliases. Pin versioned model ids when thresholds matter.
Jev API Webhook Signatures | TypeSafe Jev System One
Verify signatures on webhooks you receive. TypeSafe does not document a Jev webhook signature scheme.
Jev errors and retries
401, 422, 429, and 529 are the documented HTTP failures. Official SDKs back off; raw HTTP must do the same.
Jev models and aliases
jev-1.13.0 is the versioned model. jev-latest and jev-preview currently resolve to it. Pin versions when thresholds matter.
Jev request format
Required fields: model, state, questions. Each question has type, instructions, and type-specific criteria.
Jev response format
Responses echo a resolved model id, an answers map keyed like your questions, and token usage.
The Jev HTTP endpoint
One evaluation URL: POST /v1/systemone. List aliases with GET /v1/models. Same host: api.typesafe.ai.
The TypeSafe agent skill
Official skill for Claude Code and other agents: batch questions, use primitives, stop one-call-per-question habits.
TypeSafe JavaScript SDK
npm install @typesafe-ai/sdk on Node 20+. TypeSafeClient.systemOne infers answer types from your questions.
TypeSafe Python SDK
pip/uv install typesafe-sdk. TypeSafeClient and AsyncTypeSafeClient read TYPESAFE_API_KEY and default to jev-latest.
Your first Jev API call
POST https://api.typesafe.ai/v1/systemone with a bearer key, jev-latest, a state string, and one Noul.