Glossary: jev-latest
jev-latest is an alias for the current official Jev release (TypeSafe’s System One decision model). On the public models page we used, it pointed at jev-1.13.0, same as jev-preview. That mapping is vendor snapshot language — aliases move when TypeSafe ships. You send the string in the request model field on POST /v1/systemone. You do not send system_one as a model id.
This glossary entry is for builders who already heard of Jev / System One and need a citable definition before they fit thresholds on a moving alias. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. Confirm the models table on docs.typesafe.ai. We do not sell or issue API keys.
How it shows up
SDK examples default to jev-latest. The response model field reports the versioned id that actually answered. Pin jev-1.13.0 (or the current versioned id) once you tune thresholds or measure calibration. Do not send the truncated marketing line jev-1.13 unless the models page lists it.
GET /v1/models currently lists aliases, descriptions, and release dates. Versioned IDs are still accepted on evaluate whether or not they appear in that list. System One is the class; Jev is the first public instance; jev-latest is how you ask for “whatever official Jev is today.”
RLCD is TypeSafe’s name for training — not a flag you toggle when the alias moves. A silent alias move can change distributions under a fitted confidence threshold. Log response.model and usage in a decision trace. Schema-safe ≠ factually correct regardless of which id answered.
Pricing, rate limits, and context windows on the models page are vendor claims. Confirm there. This site does not invent ship dates for 1.14.
Contrast
jev-latest vs jev-1.13.0. The first is a moving pointer. The second is a pin. Production floors belong on a pin.
jev-latest vs jev-preview. On the snapshot we read, both resolved to jev-1.13.0. There is no separate preview build until TypeSafe ships one. Confirm the models page.
jev-latest vs System One. System One is the product class and the HTTP path (/v1/systemone). jev-latest is a model alias.
jev-latest vs Gateway spellings. typesafe-ai/jev is a Gateway model id in third-party docs, not the first-party model field.
Common mistakes
- Fitting ECE and τ on the alias, then blaming “drift” after a release.
- Sending
jev-1.13without checking the models page. - Assuming
jev-previewis a different checkpoint today. - Treating homepage speed multiples as an SLA for 1.13 — label vendor-reported numbers.
- Expecting jev.pro to announce 1.14. Watch official docs.
See also
FAQ
Is jev-preview a different model today?
Not on the snapshot we read — both aliases resolved to jev-1.13.0. Confirm on the models page.
Should production use the alias?
Use the alias to explore. Pin a versioned id when floors are fitted.
Is jev-1.13 (no .0) valid?
Treat it as the marketing line unless the models page lists it as an alias.
When will 1.14 ship?
We will not invent a date. Watch the models page.
Limits
This is a jev.pro working definition. jev-latest is a TypeSafe alias. Alias targets are vendor snapshot language and can change. We do not invent search volume. Schema-safe answers are not 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.