Jev version guide · release notes read October 15, 2026
Jev 1.14.0
The new Jev preview: what TypeSafe changed, the three experimental features that shipped with it, when jev-latest moves, and how to call it.
TypeSafe released jev-1.14.0 on October 14, 2026 under the jev-preview alias. For text decisions it is the same hosted System One model with small improvements, the largest in languages other than English. Alongside it TypeSafe opened three "danger zone" features behind request headers: images anywhere in a request, a box question type for locating something in an image, and a 262k-token context. This page collects every published fact about the version in one place, with the date it was read.
Version, aliases and lifecycle
From TypeSafe’s release post of October 14, 2026 and its model documentation.
- Version
- jev-1.14.0, released October 14, 2026
- Aliases
- jev-preview resolves to jev-1.14.0 now; jev-latest still resolves to jev-1.13.0 and switches to 1.14.0 about one week after release, as read on October 15, 2026
- What changed
- TypeSafe describes the release as small, subtle improvements to everything, with the largest expected gain in multilingual support. No flagship capability change for text decisions
- Developer
- TypeSafe
- Model class
- System One: typed decisions, no text generation
- Lifecycle
- jev-1.13.0 stays available; TypeSafe intends 60 days of warning before deprecating it and 30 days for 1.14.0, with a written deprecation policy to come
The danger zone: images, box and long context
Opt-in request headers on the TypeSafe API. TypeSafe’s own words: they are better than what exists, will keep improving, and are still too jagged to vouch for in production.
- Images
- Header TypeSafe-Danger-Zone-Images: true. Images go in a top-level assets map (PNG or JPEG, base64 or multipart) and are referenced by key from the state, the instructions or the criteria. Works on jev-1.13.0 as well as 1.14.0; billed at the text input-token price
- Image limits
- 16 MiB per image, 256 to 1,568 pixels per side, 78,400 to 2,458,624 total pixels, still images only; 32 MiB per request before and after the references are expanded
- Box type
- A fourth question type, "box", returns the smallest rectangle around a target in an image as top, bottom, left and right fractions of the image plus a confidence. Only jev-1.14.0 answers it, and it needs the images header
- Long context
- Header TypeSafe-Danger-Zone-Long-Context: true raises both limits from 64k per request and 32k per question to 262k tokens. Same price per token; TypeSafe says it is slower and less accurate than staying within the defaults
- Status
- TypeSafe calls these "dreamer-ready", not production-ready, and does not vouch for them in automation. On Jev AI, jev-1.14.0 is served for text decisions; the danger-zone headers are not forwarded yet
TypeSafe also added an opt-in that lets it inspect your queries to find model weaknesses. It states that it still does not train on customer requests.
Pricing and limits
TypeSafe’s published figures and how the same model is billed on Jev AI.
- TypeSafe list price
- $0.042 per million input tokens, the same as 1.13.0; output tokens are free
- Context window
- 64k tokens per request and 32k for the state plus the longest single question by default; 262k with the long-context header on TypeSafe directly
- On Jev AI, playground
- 1 credit per run, any length
- On Jev AI, API
- Metered on input tokens: 1 credit per 1,000,000 input tokens, the same rate as jev-latest and jev-1.13.0
- Welcome credits
- 20 on a new account
Rate limits are published per organisation in the TypeSafe console and adjust dynamically. Jev AI plans and credit packs are on the pricing page.
TypeSafe’s internal measurement
Published with the release and labelled by TypeSafe itself "Warning: AI benchmarks. Please don’t trust them." It includes only open-weight rivals, because TypeSafe keeps its validation set private, and TypeSafe notes the numbers are likely biased toward its own models and may not be consistent next time. JevBench v1.7.46 has not measured 1.14.0 yet.
| Model | Intelligence (higher is better) | Calibration error (lower is better) |
|---|---|---|
| jev 1.14.0 | 60.0 | 1.6 |
| jev 1.13.0 | 58.9 | 1.8 |
| kev-27b | 46.7 | 17.8 |
| pplx-decider-v1.1-27b | 46.0 | 35.0 |
| clef | 44.3 | 11.2 |
| clef-flash | 38.8 | 19.1 |
| kev-4b | 36.9 | 10.3 |
| d1-3b | 33.8 | 19.9 |
TypeSafe’s cost chart places both Jev versions at roughly $130 per million queries, Clef Flash near $150, pplx-decider near $270, Clef near $900 and kev-27b near $3,500. For an independent measurement of 1.13.0 against hosted and open systems, see the JevBench results page and the Jev 1.13.0 guide.
Call 1.14.0 on Jev AI
Name jev-1.14.0 to opt in now, jev-preview to follow TypeSafe’s newest build, or keep jev-latest and receive 1.14.0 when TypeSafe moves the alias. The request below is in Spanish because multilingual decisions are where TypeSafe expects the biggest gain.
curl --fail-with-body https://jev-ai.pro/api/v1/systemone \
-H "Authorization: Bearer $JEV_AI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "jev-1.14.0",
"state": "Cliente: quiero cancelar y que me devuelvan el mes que no he usado.",
"questions": {
"intent": { "type": "choice", "instructions": "What is the customer asking for?",
"criteria": { "cancel": null, "refund": null, "both": null, "other": null } },
"urgent": { "type": "noul", "instructions": "Does this need a reply today?" }
}
}'Create the key on the Jev API page. The official TypeSafe SDK works against this endpoint with its base URL set to https://jev-ai.pro/api; the documentation has the full request and response reference.
A box question on TypeSafe
The experimental features need the danger-zone headers, which Jev AI does not forward yet, so this example goes to TypeSafe directly with a TypeSafe key.
curl --fail-with-body https://api.typesafe.ai/v1/systemone \
-H "Authorization: Bearer $TYPESAFE_API_KEY" \
-H "Content-Type: application/json" \
-H "TypeSafe-Danger-Zone-Images: true" \
-d '{
"model": "jev-1.14.0",
"assets": { "photo": { "type": "image", "format": "jpg", "data_base64": "/9j/4AAQ..." } },
"state": "A shelf photo: `photo`",
"questions": {
"mug": { "type": "box", "instructions": "the coffee mug in `photo`" }
}
}'
# answer: { "mug": { "type": "box", "box": { "top": 0.25, "bottom": 0.82, "left": 0.44, "right": 0.84 }, "confidence": 0.92 } }Coordinates are fractions of the image with the origin at the top-left corner, so left < right and top < bottom. The same assets map and header let a photo stand in for text in the state, in a question’s instructions, or as an example image inside the criteria of a choice, score or yes/no question.
Jev 1.14.0 FAQ
What is new in Jev 1.14.0?
TypeSafe describes it as small, subtle improvements across the board rather than a flashy release, with the largest gain expected in multilingual decisions. Its own internal measurement moves intelligence from 58.9 to 60.0 and calibration error from 1.8 to 1.6 against 1.13.0. The visible new capability is the box question type, which only 1.14.0 answers.
Is jev-1.14.0 the same as jev-latest?
Not yet. On October 15, 2026 jev-latest still resolves to jev-1.13.0 and jev-preview resolves to jev-1.14.0. TypeSafe said jev-latest moves to 1.14.0 about one week after the October 14 release. Pin jev-1.13.0 if you want the old answers to stay stable, or jev-1.14.0 to opt in early.
When is Jev 1.13.0 deprecated?
No date is set. TypeSafe says 1.13.0 stays available for a while and that it intends to give 60 days of warning before formally deprecating it, with 30 days of warning for 1.14.0 when its turn comes. A deprecation policy is to be published first.
Can Jev 1.14 read images?
On TypeSafe directly, yes, as an experimental feature: send the header TypeSafe-Danger-Zone-Images: true, put PNG or JPEG files in a top-level assets map and reference them from the state, the instructions or the criteria. The same works on 1.13.0. On Jev AI, Jev 1.14.0 is a text model for now; Clef, Clef Flash and Jev-Omni are the image-capable options in the playground and API.
What is the box question type?
A question that returns where something is in an image: the smallest rectangle around the target as top, bottom, left and right fractions between 0 and 1, measured from the top-left corner, plus a confidence between 0 and 1. It is the first Jev type that is not a yes/no, choice or score decision, and it is only answered by jev-1.14.0 with the images header set.
How long can the context be?
By default 64k tokens per request and 32k for the state plus the longest single question, as before. With TypeSafe-Danger-Zone-Long-Context: true both limits rise to 262k tokens at the same price per token. TypeSafe kept the default low on purpose: long, noisy state makes every model less accurate, and it recommends filtering before sending.
How much does Jev 1.14 cost?
The same as 1.13.0: $0.042 per million input tokens on TypeSafe with free output tokens. On Jev AI it costs 1 credit per playground run or 1 credit per 1,000,000 input tokens through the API, with 20 welcome credits on a new account.
How does Jev 1.14.0 score on JevBench?
JevBench v1.7.46 has not measured 1.14.0 yet; its Jev row is 1.13.0. The only published comparison is TypeSafe's internal measurement above, which covers open-weight rivals and which TypeSafe itself says not to believe entirely. This page will quote the benchmark once a release includes 1.14.0.
Sources
Read on October 15, 2026; figures can change.
Jev is developed by TypeSafe. Jev AI is an independent playground and API; accounts, keys and balances here belong to Jev AI.