API · Last updated 2026-09-21

Jev API versioning

There are two version axes. The path is /v1/systemone and /v1/models. The model field selects weights: jev-1.13.0 vs aliases jev-latest / jev-preview (both pointed at jev-1.13.0 on the models page we read). Aliases move when TypeSafe ships.

This page is for builders who searched an extra “endpoint” name while wiring Jev / System One. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. We do not sell or issue keys. Confirm first-party routes on docs.typesafe.ai/api.

The public API reference documents one evaluation route — POST https://api.typesafe.ai/v1/systemone — plus GET /v1/models. This title is not a separate first-party URL in that reference. There is no /v1/version.

Steps

1. Treat /v1 as the HTTP contract.
2. Pin jev-1.13.0 (or current versioned id) once thresholds exist.
3. Log response.model on every call.
4. Upgrade the pin in a controlled diff with a replay.

Request / response shape

Request model is a string. Response model is the resolved versioned id. Do not send jev-1.13 unless listed. SDK examples use jev-latest. Confirm preview vs latest on the models page — same id on our snapshot.

A path bump will not freeze weights. Different pins in canary vs prod without saying so is how floors rot. Primitives do not change with the alias: Choice max 255, Score 2–10, Noul without confidence. Question ids are still not sent to the model. Documented errors stay 401, 422, 429, 529. Official SDKs retry 429/529.

GET /v1/models lists aliases, not a full version catalog. Gateway typesafe-ai/jev is another door’s spelling. Vendor claims (price, 250k tok/s, 1200 RPM, 64k/32k context, launch-post latency) attach to the current public model card — re-read them when you upgrade the pin. Schema-safe answers can still shift when weights move.

When not to chase a version API

Do not poll a /v1/version we will invent. Read the models page and the model field.

Pitfalls

• Believing a path bump will freeze weights.
• Different pins in canary vs prod without saying so.
• Sending jev-1.13 without a models-page listing.
• Treating jev-preview as “safe because it matches latest today.”

See also

• API hub — /v1 paths
• Models and aliases — id table
• Jev 1.13 — current public model
• Version pinning — promotion

FAQ

Is this a documented /v1/version?

No. Read the models page and the model field.

Preview alias?

Currently the same id on our snapshot. Confirm.

SDK default?

Examples use jev-latest.

Does /v1 change when 1.14 ships?

Not in the reference we used. Weights are the model field.

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. List price and rate limits are vendor claims — confirm on models.
• 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.