Shaduf.Research preview
Jev: Use Cases, Alternatives & Products/Jev 1.14 vs 1.13: IDs and aliases
Access and cost6 routes read · rechecked : 5 of 6 list a 1.14 ID (Opper added) · rechecked : aliases and route listings unchanged · rechecked : aliases unchanged; Cloudflare's catalog lists a 1.14 ID · rechecked : aliases unchanged; 6 of 6 list a 1.14 ID · rechecked : jev-latest moved to 1.14 on TypeSafe's API; Opper's alias still on 1.13 · rechecked : aliases and route listings unchanged (no check between 24 and 30 Oct) · rechecked : aliases and route listings unchanged · rechecked : aliases and route listings unchanged (no check between 31 Oct and 2 Nov) · rechecked : aliases and route listings unchanged (no check between 2 Nov and 7 Nov) · rechecked : aliases and route listings unchanged · rechecked : aliases and route listings unchanged (no check between 8 Nov, 05:24 UTC and 9 Nov, 11:07 UTC) · images read 23 October 2026 · no request sent to any route

Jev 1.14 vs 1.13 (TypeSafe AI): model IDs, jev-latest and aliases by route

When the pool checked search suggestions on , Google, Bing and DuckDuckGo all offered "jev 1.13" and "jev-latest". "jev 1.14", "jev versions" and "jev model version" had no supporting suggestion. A suggestion shows that people search for a phrase, not how many do. On , Google completed "jev latest" to "jev latest version" and "jev latest model" (R23-S40). On , Google completed "jev 1.14 vs" to "jev 1.14 vs 1.13"; Bing and DuckDuckGo returned no completion for "jev 1.14 vs" (R27-S221 to R27-S223). This page lists, for each of six routes, the Jev model IDs you can write, the aliases and what they point to, and whether you can pin a version; it also sets out what TypeSafe's docs say differs between 1.14 and 1.13 and what some public projects say about staying on 1.13 (who stayed on 1.13).

Key finding

Since 24 Oct 2026, jev-latest on TypeSafe's API gives jev-1.14.0; jev-1.13.0 is still callable by its ID, with no deprecation date. Opper's typesafe/jev-latest still gave 1.13 that morning.

DocumentedTypeSafe models page, checked (R23-S05); Opper models API, (R23-S27); other route listings 05:15–05:18 UTC (R23-S22 to R23-S30). Rechecked (models page, R24-S05) and 05:17 UTC (Opper and the other routes, R24-S22 to R24-S30), again (models page, R25-S05) and 05:14 UTC (Opper and the other routes, R25-S24 to R25-S30), again (models page, R26-S05) and 10:54 UTC (Opper and the other routes, R26-S26 to R26-S30), again (models page, R27-S05) and 15:34 UTC (Opper and the other routes, R27-S19 to R27-S23), again (models page, R28-S05) and 05:24 UTC (Opper and the other routes, R28-S40 to R28-S44), and again (models page, R29-S05) and 11:11 UTC (Opper and the other routes, R29-S24 to R29-S28): unchanged. Listings only: no request was sent to any route, so "gives" and "callable" are what the pages state, not tested calls.

The move was first seen on 24 Oct 2026, 05:12 UTC; at 23 Oct 2026, 05:45 UTC jev-latest still pointed to jev-1.13.0. TypeSafe published no dated statement of the move: its blog index lists the same 7 posts as before (latest: the 14 Oct post on 1.14), and its docs changelog address returns HTTP 404 (24 Oct 2026, 05:12–05:13 UTC; R23-S08, R23-S21). Posts on X were not checked. How each of the six routes handles jev-latest: jev-latest by route.

Key finding, 23 Oct 2026: TypeSafe now lists two Jev models: jev-1.14.0 (a preview, available from 14 Oct 2026) and jev-1.13.0. On 23 Oct 2026, 05:45 UTC, jev-latest still pointed to jev-1.13.0 and jev-preview to jev-1.14.0 (TypeSafe models page; no date published for the move). On 23 Oct 2026, 05:23 UTC, all 6 routes on this page list a 1.14 ID (TypeSafe, OpenRouter, Vercel, Netlify, Opper, Cloudflare); these are listings and documented examples, not tested requests. Cloudflare's typesafe/jev-1.14.0 page was first seen by this catalogue on 21 Oct 2026; it may have been listed earlier. On 19 Oct 2026, 5 of the 6 routes listed a 1.14 ID; Cloudflare did not list one at 05:24 UTC. Documented TypeSafe models page and route model APIs, checked ; aliases re-read (R22-S05, R22-S22 to R22-S30, R22-S45; route sources below); earlier checks 19 Oct 2026, 05:22–05:24 UTC (R19-S05) and 21 Oct 2026, 05:11–05:13 UTC (R21-S05, R21-S29)

The six routes come from the route matrix rows that serve TypeSafe's Jev; not a survey. The pool read public pages and model APIs only: it sent no request to any route and made no Jev call, so what each route actually serves is not tested. A versioned ID can be written for 1.14 on 6 of 6 routes as listed: TypeSafe direct, Netlify and Opper (patch level), Vercel (patch level, new since 14 Oct), OpenRouter (minor version only) and Cloudflare (its typesafe/jev-1.14.0 page shows example requests that write typesafe/jev-1.14.0). For 1.13 it is 5 of 6: Cloudflare lists only the unversioned typesafe/jev, and OpenRouter's IDs carry no patch number (typesafe/jev-1.13). Listings and documented examples, checked 23 Oct 2026, 05:23 UTC; no request with any of these IDs was tested (R22-S22 to R22-S30).

jev-latest now gives jev-1.14.0, and jev-preview also gives jev-1.14.0; TypeSafe says "There is no preview build available right now" (TypeSafe models page, checked 9 Nov 2026, 11:07 UTC; R29-S05; unchanged since first seen 24 Oct 2026, 05:12 UTC, R23-S05; also checked 8 Nov 2026, 05:17 UTC, R28-S05, 7 Nov 2026, 15:29 UTC, R27-S05, 2 Nov 2026, 10:47 UTC, R26-S05, and 31 Oct 2026, 05:11 UTC, R25-S05; no check between 8 Nov, 05:18 UTC and 9 Nov 2026, 11:07 UTC). jev-1.13.0 is still listed with no deprecation date (models page, docs changelog page and blog, checked 9 Nov 2026, 11:07 UTC; R29-S05, R29-S11, R29-S09; also 8 Nov 2026, R28-S05, R28-S11, R28-S09, 7 Nov 2026, R27-S05, R27-S11, R27-S09, and 2 Nov 2026, R26-S05, R26-S09). On 23 Oct 2026, 05:45 UTC, jev-latest still gave jev-1.13.0 and jev-preview gave jev-1.14.0 (checked 23 Oct 2026, 05:19 UTC, re-read 05:45 UTC; alias table unchanged from 16 Oct to 23 Oct; also read 21 Oct 2026, 05:11 UTC, 19 Oct 2026, 05:22 UTC and 18 Oct 2026, 05:17 UTC). TypeSafe's 14 Oct post said jev-latest would move to 1.14 "in a week"; the move was first seen on 24 Oct 2026, 05:12 UTC (it had not happened at 23 Oct 2026, 05:45 UTC). TypeSafe has published no 1.13 deprecation date; the post says it intends "60 days warning" first (R23-S05, R23-S09; 23 Oct: R22-S05, R22-S09; 21 Oct: R21-S05, R21-S09; 19 Oct: R19-S05, R19-S09; 18 Oct: R18-S05, R18-S09).

Change, 7 Nov 2026: the page title was "Jev 1.14, 1.13 and jev-latest (TypeSafe AI): model IDs and aliases by route"; it now leads with "Jev 1.14 vs 1.13", the phrase Google completed from "jev 1.14 vs" on 7 Nov 2026, 15:34 UTC (R27-S221). The address is unchanged. Added: who stayed on Jev 1.13, and why (8 public GitHub items, Reported), and a 7 Nov line on the models page's input and question-type rows (what changed with Jev 1.14, image fields by route).

Change, 24 Oct 2026: the key finding said TypeSafe lists jev-1.14.0 as a preview and that jev-latest still pointed to jev-1.13.0 (23 Oct 2026, 05:45 UTC); that finding is kept above as the 23 Oct finding. The alias line now gives the 24 Oct check, the "in a week" lines give the time the move was first seen, the jev-latest by route table is added, the TypeSafe row of the route table is updated, and "preview" is dropped from the page title.

Change, 23 Oct 2026: the key finding said 5 of 6 routes list a 1.14 ID (19 Oct 2026, 05:24 UTC) and that a versioned ID can be written on 5 of 6 routes, with Cloudflare unversioned only. On 23 Oct 2026, 05:23 UTC, 6 of 6 list a 1.14 ID; a versioned ID can be written on 6 of 6 for 1.14 and 5 of 6 for 1.13 (Cloudflare lists only typesafe/jev for 1.13). The alias lines are re-dated (aliases unchanged), and the route image fields are added (image fields by route).

Change, 21 Oct 2026: the Cloudflare row adds the catalog page for typesafe/jev-1.14.0, first seen by this catalogue on 21 Oct 2026; it may have been listed earlier (the 16, 18 and 19 Oct checks read the address without .0, which serves the generic models index). The alias line is re-dated; the aliases are unchanged.

Change, 18 Oct 2026: the key finding said 4 of 6 routes list a 1.14 ID, with Cloudflare and Opper not listing one (16 Oct 2026, 05:25 UTC). Opper now lists typesafe/jev-1.14.0.

Change, 16 Oct 2026: the key finding said 4 of 6 routes take a versioned ID and that jev-latest and jev-preview both point to jev-1.13.0 (true at every read from 6 Oct to 14 Oct 2026, 16:48 UTC). TypeSafe released Jev 1.14 under jev-preview on 14 Oct, and Vercel now lists versioned IDs.

Who stayed on Jev 1.13, and why (Reported)

What differs, per TypeSafe's docs. TypeSafe's models page, read , gives jev-1.14.0 and jev-1.13.0 the same price ($0.042 per million input tokens; output free) and the same context limits (64k per request, 32k per question; the long-context header works on both). It lists the input of both versions as "Text, images" and says Jev "also reads PNG and JPEG images anywhere in the request"; this row read "Text" for both on 2 Nov 2026, so it changed between 2 Nov and 7 Nov 2026 (first observed 7 Nov, 15:29 UTC). TypeSafe's images page still says images and Box questions "aren't yet up to our standards to call ready for production" and requires the TypeSafe-Danger-Zone-Images: true header. Box is a question type on Jev 1.14 only ("Box questions need Jev 1.14"). TypeSafe's model changelog, dated October 14, 2026, lists "Better multilingual support" for Jev 1.14; it publishes no multilingual accuracy figures. Documented (R27-S05, R27-S06, R27-S11; no image, Box or long-context request was sent)

What public projects say. Eight public GitHub issues and pull requests about staying on, pinning or comparing jev-1.13 and jev-1.14, or about jev-latest handling, each read on . Titles and quotes are as each page showed them; created dates come from GitHub search results, states from the pages. Reported: these are the projects' own statements; TypeSafe has not confirmed them and the pool has not tested them.

ItemCreatedState (7 Nov 2026)QuoteReason given (Reported)Source
1. bismawy/pi-jev-eye #12 (Issue): "OpenRouter backend is pinned to typesafe/jev-1.13"Open"OpenRouter now lists typesafe/jev-1.14, so anyone on the OpenRouter backend is stuck on the older model, and there's no setting to change it. The TypeSafe backend already uses jev-latest, so the two backends are out of sync."The ID is hard-coded; the issue gives no reason to stay on 1.13. It suggests the alias ~typesafe/jev-latest or a per-backend override.R27-S226
2. ConfusedSky/jev-tests #33 (Issue): "Tune for jev-1.14: it drops quantity words, so the default is pinned to jev-1.13"Open"~typesafe/jev-latest moved from typesafe/jev-1.13 to typesafe/jev-1.14-20261014, and the bench fell from 91% to 85%. The default is pinned to typesafe/jev-1.13 for now (e1376e6), with a bench record on it (618d77b, 95%)."The repository's own benchmark dropped after the alias moved to 1.14; it says its Noul prompting drops quantity words on 1.14.R27-S227; quote re-read 15:40 UTC, R27-S43
3. ConfusedSky/jev-tests #37 (Issue): "Pin the OpenRouter provider behind the jev model"Open"The model is pinned to typesafe/jev-1.13 (DEFAULT_MODEL in shared.ts), but OpenRouter may still route a request to different hosts."Reproducible scores: pinning the version is not enough for this repository, so it also wants to pin the host.R27-S228
4. wdaniel1993/lunate #618 (Pull request (draft)): "fix(opencode-go): serve System One and pin jev-1.13"Open (draft)"the opencode-go preset now serves the System One family and pins jev-1.13; the wizard explains the billing model."No reason found in the page text; the pull request is labelled an "rc.3 review finding".R27-S229
5. therealmodbom/jobadvaisor #51 (Issue): "Content guard: larger eval data, compare Jev 1.14 with 1.13 and Mistral"Open"Thresholds do not transfer between releases, so a version switch needs its own measurement."1.13.0 is the measured default ("caught 12 of 12" in its small eval); the repository will move to 1.14 only after re-measuring on more data.R27-S230
6. vercel/ai #21213 (Issue): "AI Gateway returns the alias as modelId for typesafe-ai/jev, not the resolved version"Open"response.modelId comes back as the alias I sent, and no field anywhere in the result names a version."Alias resolution: through this gateway a caller on the alias cannot tell from the response whether 1.13 or 1.14 answered.R27-S231
7. muthuishere/toolnexus #91 (Issue): "classifier: default base URL + model (jev-latest) returns HTTP 400 Unknown model"Open"The floating alias jev-latest is rejected."Alias resolution: the alias failed in that client's setup, so it used an explicit model ID through OpenRouter.R27-S232
8. tumf/jev-cli #5 (Pull request): "chore: default the openrouter provider to typesafe/jev-1.14"Open"Change the openrouter provider's default model from typesafe/jev-1.13 to typesafe/jev-1.14, the newer Jev release on OpenRouter."The other direction: this repository moves its default off 1.13, citing that 1.14 is listed "with a live endpoint".R27-S233

Over these 8 opened items only: 5 pin, or keep a default on, 1.13 (items 1 to 5); 1 moves its default from 1.13 to 1.14 (item 8); 2 are about how the alias resolves (items 6 and 7). The items come from two GitHub searches run on 7 Nov 2026, 15:34 UTC ("jev-1.13" pin, 2,069 results; "jev-1.14" "jev-1.13", 416 results; R27-S224, R27-S225); those totals include unrelated matches. This is not a survey and does not show how many projects use either version.

The reasons given fall into three kinds: a measured drop after the alias moved (item 2), thresholds tuned on 1.13 (item 5), and IDs written into code that were not updated (item 1). If you tuned thresholds on 1.13, TypeSafe's own advice is to "send that version's ID instead of the alias" (models page); how to pin a version on each route.

What jev-latest gives on each route (24 Oct 2026)

Each route's own listing, read (TypeSafe's models page at 05:12 UTC). These are listings, not tests: no request was sent to any route, so what each alias or unversioned ID returns in a response was not observed. Documented

Rechecked : every row below still reads as on 24 Oct (TypeSafe's models page at 11:07 UTC, identical to the 8 Nov copy; the five other routes at 11:11 UTC; R29-S05, R29-S24 to R29-S28). There was no check between 8 Nov, 05:24 UTC and 9 Nov 2026, 11:07 UTC. On Opper, typesafe/jev-latest still gives jev-1.13.0, while TypeSafe's own jev-latest gives jev-1.14.0. Listings and documented examples; no request with any of these IDs was tested. Documented

Rechecked : every row below still reads as on 24 Oct (TypeSafe's models page at 05:17 UTC, identical to the 7 Nov copy; the five other routes at 05:24 UTC; R28-S05, R28-S40 to R28-S44). There was no check between 7 Nov, 15:34 UTC and 8 Nov 2026, 05:17 UTC. On Opper, typesafe/jev-latest still gives jev-1.13.0, while TypeSafe's own jev-latest gives jev-1.14.0. Listings and documented examples; no request with any of these IDs was tested. Documented

Rechecked : every row below still reads as on 24 Oct (TypeSafe's models page at 15:29 UTC, which changed elsewhere on the page but not in its aliases, model IDs or prices; the five other routes at 15:34 UTC; R27-S05, R27-S19 to R27-S23). There was no check between 2 Nov and 7 Nov 2026. On Opper, typesafe/jev-latest still gives jev-1.13.0, while TypeSafe's own jev-latest gives jev-1.14.0. Listings and documented examples; no request with any of these IDs was tested. Documented

Rechecked : every row below still reads as on 24 Oct (TypeSafe's models page at 10:47 UTC, identical to the 31 Oct copy; the five other routes at 10:54 UTC; R26-S05, R26-S26 to R26-S30). There was no check between 31 Oct and 2 Nov 2026. On Opper, typesafe/jev-latest still gives jev-1.13.0, while TypeSafe's own jev-latest gives jev-1.14.0. Listings and documented examples; no request with any of these IDs was tested. Documented

Rechecked : every row below still reads as on 24 Oct (TypeSafe's models page at 05:11 UTC, identical to the 30 Oct copy; the five other routes at 05:14 UTC; R25-S05, R25-S24 to R25-S30). On Opper, typesafe/jev-latest still gives jev-1.13.0, while TypeSafe's own jev-latest gives jev-1.14.0. Listings and documented examples; no request with any of these IDs was tested. Documented

Rechecked : every row below reads as on 24 Oct (TypeSafe's models page at 05:14 UTC, the five other routes at 05:17 UTC; R24-S05, R24-S22 to R24-S30). There was no check between 24 and 30 Oct 2026. Listings and documented examples, checked 30 Oct 2026, 05:17 UTC; no request with any of these IDs was tested. Documented

RouteWhat it publishesjev-latest result as publishedSource
TypeSafe directjev-latest → jev-1.14.0; jev-preview → jev-1.14.0 ("There is no preview build available right now"); jev-1.13.0 listed by its ID, no deprecation dateMoved to 1.14 first seen 05:12 UTC; still jev-1.13.0 at 23 Oct 2026, 05:45 UTCR23-S05
Oppertypesafe/jev-1.13.0 with alias typesafe/jev-latest (model_id jev-1.13.0); typesafe/jev-1.14.0 with alias typesafe/jev-preview; a query for typesafe/jev-latest returns the 1.13.0 entryStill jev-1.13.0 at 05:15:41 UTCR23-S27
OpenRouterVersioned typesafe/jev-1.13 (endpoint typesafe/jev-1.13-20260917) and typesafe/jev-1.14 (endpoint typesafe/jev-1.14-20261014); ~typesafe/jev-latest: "This model always redirects to the latest model in the Jev family", with no endpoint listedTarget not statedR23-S22, R23-S23, R23-S24
Vercel AI Gatewaytypesafe-ai/jev (unversioned; providers digitalocean, typesafe-ai), typesafe-ai/jev-1.13.0, typesafe-ai/jev-1.14.0; model list of 480 IDsNo alias published which version typesafe-ai/jev serves is not statedR23-S25, R23-S26
Netlify AI GatewayOverview lists jev-1.13.0, jev-1.14.0, jev-latest, jev-preview and jev-routerTarget not stated on the overviewR23-S30
Cloudflaretypesafe/jev (unversioned; its example responses show "model": "jev-1.13.0") and typesafe/jev-1.14.0No alias published which version typesafe/jev serves now is not statedR23-S28, R23-S29

Count, 24 Oct 2026, 05:12–05:18 UTC: 1 moved (TypeSafe direct) + 1 still on 1.13 (Opper) + 4 publish no alias target (OpenRouter, Vercel, Netlify, Cloudflare) = 6.

Count, 30 Oct 2026, 05:14–05:17 UTC: unchanged, 1 + 1 + 4 = 6.

Count, 2 Nov 2026, 10:47–10:54 UTC: unchanged, 1 + 1 + 4 = 6 (also 31 Oct 2026, 05:11–05:14 UTC).

Count, 9 Nov 2026, 11:07–11:11 UTC: unchanged, 1 + 1 + 4 = 6 (also 8 Nov 2026, 05:17–05:24 UTC, and 7 Nov 2026, 15:29–15:34 UTC).

Same alias name, different version. On 24 Oct 2026 (05:15 UTC) Opper still mapped its typesafe/jev-latest alias to jev-1.13.0, so the same alias name gave a different version on Opper than on TypeSafe's own API; OpenRouter, Vercel, Netlify and Cloudflare publish no alias target. On Opper, typesafe/jev-latest still maps to jev-1.13.0 (Opper models API, checked 9 Nov 2026, 11:11 UTC; also 24, 30 and 31 Oct and 2, 7 and 8 Nov). Send typesafe/jev-1.14.0 to get 1.14 there, and a versioned ID on any route if the version matters. Documented (each route's own listing; R23-S05, R23-S22 to R23-S30; 30 Oct: R24-S05, R24-S22 to R24-S30; 31 Oct: R25-S05, R25-S24 to R25-S30; 2 Nov: R26-S05, R26-S26 to R26-S30; 7 Nov: R27-S05, R27-S19 to R27-S23; 8 Nov: R28-S05, R28-S40 to R28-S44; 9 Nov: R29-S05, R29-S24 to R29-S28)

What changed with Jev 1.14

TypeSafe published the post "Jev: For the builders AND dreamers" (dated 14 Oct 2026) and updated its models page. What the pages say, checked :

  • Aliases. jev-preview → jev-1.14.0; jev-latest → jev-1.13.0 ("The most recent stable, official release. The default in our client SDKs"). TypeSafe's 14 Oct post said: "jev-latest will be updated to jev-1.14.0 in a week. jev-1.13.0 will be available for a while." It also said it intends "60 days warning before jev-1.13.0 is formally deprecated, and 30 days for jev-1.14.0", and that a deprecation policy will be published first. Documented (models page, R17-S05; TypeSafe blog, R17-S09) The move was first seen on 24 Oct 2026, 05:12 UTC: jev-latest → jev-1.14.0 and jev-preview → jev-1.14.0 (it had not happened at 23 Oct 2026, 05:45 UTC). TypeSafe has published no 1.13 deprecation date, and no deprecation policy page was found on its blog index or models page (24 Oct 2026, 05:12 UTC; R23-S05, R23-S08, R23-S09). If you tuned thresholds on 1.13, send jev-1.13.0; this restates TypeSafe's own advice to "send that version's ID instead of the alias".
  • Price. jev-1.14.0 and jev-1.13.0: $0.042 per million input tokens ($42 per billion); output free; long context costs the same per token. Unchanged for 1.13 since 28 Sep. Documented (R17-S05)
  • Images (experimental). Text is the default input on both versions. Images are accepted only with the opt-in header TypeSafe-Danger-Zone-Images: true, on both versions. TypeSafe says images and Box "aren't yet up to our standards to call ready for production": experimental, not production-ready per TypeSafe. No audio or video. The post says jev-1.13.0 "was multimodal all along" Reported. (R17-S05, R17-S06, R17-S09)
  • Box questions (experimental, 1.14 only). A bounding-box question type. On 16 Oct 2026 TypeSafe's Box page said: "Box questions need Jev 1.14: send jev-preview or jev-1.14.0" (R17-S20). On 24 Oct 2026: "Box questions need Jev 1.14" (images page); on TypeSafe's API jev-latest, jev-preview and jev-1.14.0 all give 1.14 since 24 Oct; TypeSafe's own image and Box examples send jev-latest (images.md L29, L169, L215; box.md L33; R23-S06, R23-S19). Not production-ready per TypeSafe. Documented
  • Long context (experimental). Default limits on both versions: 64k tokens per request and 32k per question. The opt-in header TypeSafe-Danger-Zone-Long-Context: true raises both to 262k tokens on 1.14 and 1.13. TypeSafe says long context is "slower and less accurate" Reported. (R17-S05)
  • Rate limits. Until at least 14 Oct 2026, 16:46 UTC the models page listed 100K tokens per second and 80 requests per second (R16-S05). On 16 Oct 2026, 05:21 UTC it lists no numbers: "Rate limits are set per organization. Your organization's current limits are in the developer console." The pool has no account, so it cannot see the current numbers. Documented (R17-S05; see errors and rate limits)
  • Quality. TypeSafe says 1.14 brings "small, subtle improvements to everything", with "the largest gain in multi-lingual support". Reported Not tested here.

Documented vs experimental: text questions on both versions are TypeSafe's standard offering. Images (both versions), the Box question type (1.14 only) and 262k long context (both) are opt-in "Danger Zone" features that TypeSafe says are not yet production-ready (R17-S05, R17-S06, R17-S20). No image, Box or long-context request was sent.

Change, 7 Nov 2026: the list above is as read on 16 Oct 2026. Since at least 7 Nov 2026 (first observed 7 Nov, 15:29 UTC; the change happened after 2 Nov, 11:13 UTC) TypeSafe's models page lists the input of both Jev 1.14 and Jev 1.13 as "Text, images" and says Jev "also reads PNG and JPEG images anywhere in the request". The images page still calls images and Box "not yet ... ready for production" and requires the TypeSafe-Danger-Zone-Images: true header. A new "Question types" row lists Choice, Score, Noul and Box for 1.14 and Choice, Score and Noul for 1.13 ("Box questions need Jev 1.14"). The "Language support" section is gone from the models page; TypeSafe's model changelog (entry dated October 14, 2026) lists "Better multilingual support" for Jev 1.14. Documented (R27-S05, R27-S06, R27-S11)

Model IDs and aliases on each route

Rechecked : no alias or listing change since 24 Oct. jev-latest and jev-preview → jev-1.14.0 on TypeSafe's models page (identical to the 8 Nov copy); jev-1.13.0 still listed with no deprecation date (also none on TypeSafe's docs changelog page); Opper's typesafe/jev-latest still points to 1.13.0; OpenRouter, Vercel, Netlify and Cloudflare list the same Jev model IDs as on 24, 30 and 31 Oct and 2, 7 and 8 Nov and state no alias target. There was no check between 8 Nov, 05:24 UTC and 9 Nov 2026, 11:07 UTC. Documented (R29-S05, R29-S09, R29-S11, R29-S24 to R29-S28)

Rechecked : no alias or listing change since 24 Oct. jev-latest and jev-preview → jev-1.14.0 on TypeSafe's models page (identical to the 7 Nov copy); jev-1.13.0 still listed with no deprecation date (also none on TypeSafe's docs changelog page); Opper's typesafe/jev-latest still points to 1.13.0; OpenRouter, Vercel, Netlify and Cloudflare list the same Jev model IDs as on 24, 30 and 31 Oct and 2 and 7 Nov and state no alias target. There was no check between 7 Nov, 15:34 UTC and 8 Nov 2026, 05:17 UTC. Documented (R28-S05, R28-S09, R28-S11, R28-S40 to R28-S44)

Rechecked : no alias or listing change since 24 Oct. jev-latest and jev-preview → jev-1.14.0 on TypeSafe's models page; jev-1.13.0 still listed with no deprecation date (also none on TypeSafe's new docs changelog page); Opper's typesafe/jev-latest still points to 1.13.0; OpenRouter, Vercel, Netlify and Cloudflare list the same Jev model IDs as on 24, 30 and 31 Oct and 2 Nov and state no alias target. There was no check between 2 Nov and 7 Nov 2026. Documented (R27-S05, R27-S09, R27-S11, R27-S19 to R27-S23)

Rechecked : no alias or listing change since 24 Oct. jev-latest and jev-preview → jev-1.14.0 on TypeSafe's models page (identical to the 31 Oct copy); jev-1.13.0 still listed with no deprecation date; Opper's typesafe/jev-latest still points to 1.13.0; OpenRouter, Vercel, Netlify and Cloudflare list the same Jev model IDs as on 24, 30 and 31 Oct and state no alias target. There was no check between 31 Oct and 2 Nov 2026. Documented (R26-S05, R26-S09, R26-S26 to R26-S30)

Rechecked : no alias or listing change since 24 Oct. jev-latest and jev-preview → jev-1.14.0 on TypeSafe's models page (identical to the 30 Oct copy); jev-1.13.0 still listed with no deprecation date; Opper's typesafe/jev-latest still points to 1.13.0; OpenRouter, Vercel, Netlify and Cloudflare list the same Jev model IDs as on 24 and 30 Oct and state no alias target. Documented (R25-S05, R25-S09, R25-S24 to R25-S30)

Rechecked : no alias or listing change since 24 Oct. jev-latest and jev-preview → jev-1.14.0 on TypeSafe's models page; jev-1.13.0 still listed with no deprecation date; Opper's typesafe/jev-latest still points to 1.13.0; OpenRouter, Vercel, Netlify and Cloudflare list the same Jev model IDs as on 24 Oct and state no alias target. There was no check between 24 and 30 Oct 2026. Documented (R24-S05, R24-S22 to R24-S30)

Rechecked : one alias change, on TypeSafe's models page. jev-latest → jev-1.14.0 (it was jev-1.13.0 at 23 Oct 2026, 05:45 UTC); jev-preview → jev-1.14.0; jev-1.13.0 still listed with the same price and context limits as 1.14 and no deprecation date. Opper's typesafe/jev-latest still points to 1.13.0. OpenRouter, Vercel, Netlify and Cloudflare list the same Jev model IDs as in the table below (Netlify's overview also lists jev-router, not noted in earlier reads); none of them states an alias target (jev-latest by route). The table below keeps the 23 Oct read for every row except TypeSafe direct; its other fields were not re-read on 24 Oct. Documented (R23-S05, R23-S22 to R23-S30, listed below)

Earlier recheck, (aliases re-read 05:45 UTC): no listing change since 21 Oct; 6 of 6 routes list a 1.14 ID. On TypeSafe's models page jev-latest → jev-1.13.0 and jev-preview → jev-1.14.0; versioned IDs "such as jev-1.14.0 are accepted by the model field"; no repoint date and no 1.13 deprecation date. OpenRouter lists typesafe/jev-1.13 and typesafe/jev-1.14 (262,144 context; its /models list of 468 IDs still shows only typesafe/jev-router for TypeSafe). Vercel lists typesafe-ai/jev (providers listed: digitalocean, typesafe-ai), typesafe-ai/jev-1.13.0 and typesafe-ai/jev-1.14.0, context field 32,000. Opper's typesafe/jev-latest still points to 1.13.0 and typesafe/jev-preview to 1.14.0. Netlify lists jev-1.13.0, jev-1.14.0, jev-latest and jev-preview. Cloudflare's AI models catalog has two Jev pages: typesafe/jev (1.13-era examples) and typesafe/jev-1.14.0 ("Third-party", 32,000 tokens; images and Box "beta and dreamer-ready, not recommended for production"), whose example requests write typesafe/jev-1.14.0 in a Worker (env.AI.run) and over Cloudflare's REST /ai/run endpoint; the catalog index carries a typesafe/jev-1.14.0 card. The 21 Oct note below says the model is served "through AI Gateway"; on 23 Oct the page text did not mention AI Gateway (outside the site menu), and the difference is not resolved. Amazon Bedrock, Microsoft Foundry (Microsoft Learn's partner-models page), the Workers AI models page and Cloudflare's changelog: no "Jev" or "TypeSafe" string found at 05:23 UTC. The six route rows below are re-dated to this check; the three platforms at the end keep their 18 Oct read. Documented (R22-S05, R22-S09, R22-S22 to R22-S31, R22-S45, listed below)

Earlier recheck, : one change, on Cloudflare. Cloudflare's AI model catalog lists typesafe/jev-1.14.0 as a third-party model served through AI Gateway, with a 32,000-token context window and images and Box marked beta (checked 21 Oct 2026, 05:13 UTC). Its Jev overview page still shows 1.13 examples. First seen by this catalogue on 21 Oct 2026; it may have been listed earlier. Aliases unchanged on TypeSafe's models page and on Opper. OpenRouter (typesafe/jev-1.13 and typesafe/jev-1.14 endpoint files), Vercel (three Jev IDs) and Netlify (jev-1.13.0 and jev-1.14.0) list the same IDs as on 19 Oct. Amazon Bedrock, Microsoft Foundry (Microsoft Learn's partner-models page), the Workers AI models page and Cloudflare's changelog contain no "Jev" or "TypeSafe" string. The table keeps the 18 Oct read times for the other rows. Documented (R21-S05, R21-S09, R21-S22 to R21-S31, listed below)

Earlier recheck, : 5 of 6 routes list a 1.14 ID; no change since 18 Oct (TypeSafe direct, OpenRouter, Vercel, Netlify, Opper); 1 of 6 does not (Cloudflare: /ai/models/typesafe/jev/ still shows jev-1.13.0 examples, and /ai/models/typesafe/jev-1.14/ serves the generic models page). Aliases unchanged: on TypeSafe's models page jev-latest → jev-1.13.0 and jev-preview → jev-1.14.0; on Opper typesafe/jev-latest → 1.13.0 and typesafe/jev-preview → 1.14.0 (both Opper model files byte-identical to 18 Oct). OpenRouter's 1.13 and 1.14 endpoint files are byte-identical to 18 Oct; Vercel's differ only in uptime values. Jev 1.14 was not found on Cloudflare, Amazon Bedrock, Microsoft Foundry (Microsoft Learn's partner-models page) or the Workers AI models page on 19 Oct 2026, 05:24 UTC; the Bedrock model-cards, Foundry partner-models and Workers AI pages contain no "Jev" or "TypeSafe" string, and Cloudflare's changelog has no Jev item. The table below keeps the 18 Oct read times and detail. Documented (R19-S05, R19-S22 to R19-S28, R19-S30 to R19-S38, listed below)

Earlier recheck, : 5 of 6 routes list a 1.14 ID (TypeSafe direct, OpenRouter, Vercel, Netlify, Opper); 1 of 6 does not (Cloudflare). One change since 16 Oct: Opper now lists typesafe/jev-1.14.0 (alias typesafe/jev-preview, 64,000-token context, $0.042 per million input tokens); its typesafe/jev-latest alias still points to 1.13.0 (checked 18 Oct 2026, 05:20 UTC). Opper's model card for 1.14 was created on 16 Oct 2026, 08:08 UTC. Jev 1.14 was still not listed on Cloudflare, Amazon Bedrock, Microsoft Foundry or Workers AI on 18 Oct 2026, 05:20 UTC (for Foundry: Microsoft Learn's partner-models page; the Foundry catalog was last read on 16 Oct). The other rows are unchanged from 16 Oct. Documented (sources R18-S05, R18-S22 to R18-S37, listed below)

Earlier recheck, , after TypeSafe released Jev 1.14 as a preview: 4 of 6 routes list a 1.14 ID (TypeSafe direct, OpenRouter, Vercel, Netlify); 2 of 6 did not list one at 05:25 UTC (Cloudflare, Opper). Vercel now lists patch-level IDs, and OpenRouter's typesafe/jev-1.13 entry now states text and image input with a 262,144-token context. (Documented; sources R17-S05, R17-S22, R17-S23, R17-S26, R17-S27, R17-S28, R17-S29, R17-S30, R17-S31, listed below)

Change, 16 Oct 2026: this table replaces the 6 Oct table as the current one (6 Oct table and earlier rechecks kept below). Three platforms that do not serve Jev are added at the end, because readers ask about them: Bedrock, Foundry and the Workers AI catalog list neither version.

RouteJev 1.14Jev 1.13Can you pin a version?Last read (UTC)Source
TypeSafe directjev-1.14.0 (via jev-latest and jev-preview since the move first seen on 24 Oct 2026, 05:12 UTC). jev-latest: "The most recent stable, official release. The default in our client SDKs". "Jev 1.14 is the newest Jev release, available from October 14, 2026." Change, 24 Oct 2026: until at least 23 Oct 2026, 05:45 UTC this cell said "via jev-preview" only.jev-1.13.0 (by its ID); still listed, no deprecation date Change, 24 Oct 2026: until at least 23 Oct 2026, 05:45 UTC this cell said "via jev-latest".Yes jev-1.14.0 or jev-1.13.024 Oct, 05:12:29 (earlier 23 Oct, 05:19:01 and 05:45:14)TypeSafe models page (R23-S05; 23 Oct: R22-S05; 18 Oct: R18-S05; 16 Oct: R17-S05)
OpenRoutertypesafe/jev-1.14: endpoint page lists provider TypeSafe, created 2026-10-14T23:43:37Z, 262,144 context, text and image input, prompt price 0.000000042 per token. Not in the /models list, which still shows only typesafe/jev-router for TypeSafe.typesafe/jev-1.13: input now text and image; context 64,000 → 262,144; maximum prompt 32,000 → 262,144 (changed since 14 Oct 2026, 16:48 UTC)Minor version only typesafe/jev-1.14, typesafe/jev-1.1323 Oct, 05:23:17–05:23:18endpoints API, typesafe/jev-1.14 (R17-S23); endpoints API, typesafe/jev-1.13 (R17-S22); models API (R17-S26); unchanged on 18 Oct (R18-S22 to R18-S24) and 23 Oct (R22-S22 to R22-S24)
Vercel AI Gatewaytypesafe-ai/jev-1.14.0 listed (provider typesafe-ai; text and image; prompt 0.000000042; context field 32,000)typesafe-ai/jev-1.13.0 listed (same fields); typesafe-ai/jev unchanged (two providers). Vercel's AI Gateway lists a 32,000-token context window for all three Jev IDs (18 Oct 2026). Vercel does not define the field further; TypeSafe's default limits are 64k tokens per request and 32k per question, so the figure matches the per-question limit, not the request limit (which limit Vercel means is not confirmed; R18-S28, R18-S29).Yes typesafe-ai/jev-1.14.0 or typesafe-ai/jev-1.13.0 (new since 14 Oct)23 Oct, 05:23:18–05:23:19models API and endpoints API (R17-S27); versioned endpoints APIs (R17-S28); 18 Oct: R18-S25 to R18-S28; 23 Oct: R22-S25, R22-S26
CloudflareCloudflare's AI models catalog lists typesafe/jev-1.14.0 ("Third-party", 32,000-token context window; images and Box "beta and dreamer-ready, not recommended for production"); its example requests write "model": "typesafe/jev-1.14.0" (Worker env.AI.run and REST /ai/run) (checked 23 Oct 2026, 05:23 UTC; unchanged at 30 Oct 2026, 05:17 UTC, 31 Oct 2026, 05:14 UTC, 2 Nov 2026, 10:54 UTC, 7 Nov 2026, 15:34 UTC, 8 Nov 2026, 05:24 UTC and 9 Nov 2026, 11:11 UTC, R24-S28, R24-S29, R25-S28, R25-S29, R26-S30, R27-S23, R28-S44, R29-S28). Its Jev overview page still shows 1.13 examples. First seen by this catalogue on 21 Oct 2026; it may have been listed earlier. Change, 23 Oct 2026: on 21 Oct this cell said the catalog lists the model "served through AI Gateway"; on 23 Oct the page text did not mention AI Gateway (outside the site menu). Change, 21 Oct 2026: this cell said "Not listed at 18 Oct 2026, 05:20 UTC (also not at 16 Oct)". Those checks read /ai/models/typesafe/jev-1.14/ (without .0), which serves the generic models index.typesafe/jev (unversioned); its page still shows jev-1.13.0 in the example response1.14 only typesafe/jev-1.14.0, as written in the 1.14 page's example requests; for 1.13, unversioned typesafe/jev only. Whether a request with typesafe/jev-1.14.0 is accepted and pins 1.14 was not tested. Change, 23 Oct 2026: this cell said "No: unversioned ID only on the Jev overview page" (21 Oct 2026).23 Oct, 05:23:21Cloudflare model page (R22-S28; 21 Oct: R21-S28; 18 Oct: R18-S30, R18-S31; 16 Oct: R17-S29); Cloudflare catalog page, typesafe/jev-1.14.0 (R22-S29; 21 Oct: R21-S29); Cloudflare AI models index (R22-S45)
Netlify AI Gatewayjev-1.14.0 listed beside jev-1.13.0, jev-latest and jev-previewjev-1.13.0 listed. Netlify does not state alias targets (TypeSafe's statement in the first row applies). On 24 Oct 2026, 05:15 UTC the overview still states no target, so whether Netlify's jev-latest now returns 1.14 was not confirmed (no request sent; R23-S30).Yes jev-1.14.0 or jev-1.13.023 Oct, 05:23:22Netlify AI Gateway overview (R22-S30; 18 Oct: R18-S34; 16 Oct: R17-S31)
Oppertypesafe/jev-1.14.0 listed: alias typesafe/jev-preview, 64,000-token context, $0.042 per million input tokens, release date 2026-10-14; model card created 2026-10-16T08:08:16Z. Change, 18 Oct 2026: not listed at 16 Oct 2026, 05:25 UTC (search for typesafe/jev-1.14.0: 0 results).typesafe/jev-1.13.0; keeps the alias typesafe/jev-latest, which still points to 1.13.0 (also on 24 Oct 2026, 05:15 UTC, after TypeSafe's own jev-latest moved to 1.14; R23-S27). Its typesafe/jev-preview alias moved to 1.14.0.Yes typesafe/jev-1.14.0 or typesafe/jev-1.13.023 Oct, 05:23:19Opper models API, 1.14 (R18-S33); Opper models API, 1.13 (R18-S32); aliases unchanged on 23 Oct (R22-S27)
Amazon BedrockNot listed at 18 Oct 2026, 05:20 UTC (model cards: 0 matches for "typesafe" and "jev"). Marketplace model reference and model-choice page: 0 matches at 16 Oct 2026, 05:21 UTC (not reread on 18 Oct)Not listedNot applicable18 Oct, 05:20:15R18-S36; 16 Oct: R17-S34
Microsoft FoundryNot listed at 18 Oct 2026, 05:20 UTC on Microsoft Learn's models-from-partners page (0 matches). Catalog /catalog/models/jev: "No Data Available" at 16 Oct 2026, 05:21 UTC (not reread on 18 Oct)Not listedNot applicable18 Oct, 05:20:15R18-S35; 16 Oct: R17-S32, R17-S33
Cloudflare Workers AI catalogNot listed at 18 Oct 2026, 05:20 UTC (0 matches for "typesafe" and "jev")Not listed (Jev is on Cloudflare's AI models page, not the Workers AI catalog)Not applicable18 Oct, 05:20:15R18-S37; 16 Oct: R17-S35

Count, 23 Oct 2026, 05:23 UTC: 1.14 listed on 6/6 routes (TypeSafe, OpenRouter, Vercel, Netlify, Opper, Cloudflare). A versioned ID can be written for 1.14 on 6/6 (Cloudflare's 1.14 page shows requests that write typesafe/jev-1.14.0; OpenRouter at minor version only) and for 1.13 on 5/6 (Cloudflare lists only the unversioned typesafe/jev; OpenRouter's typesafe/jev-1.13 carries no patch number). Listings and documented examples, not tested requests.

Count, 19 Oct 2026: unchanged from 18 Oct. Count, 18 Oct 2026: 1.14 listed on 5/6 routes (TypeSafe, OpenRouter, Vercel, Netlify, Opper); not listed on 1/6 (Cloudflare). On 16 Oct 2026: 4/6 (Opper not yet listed). A versioned ID can be written on 5/6 (TypeSafe, Netlify, Opper and Vercel at patch level; OpenRouter at minor version only); unversioned only on 1/6 (Cloudflare typesafe/jev). The three platforms below the six routes are not counted.

Image input fields by route

What each route's listing says about image input, read . These are listings, not forwarding tests: no image was sent to any route. TypeSafe calls image input experimental and opt-in (header TypeSafe-Danger-Zone-Images: true) and says it is not production-ready.

RouteImage field as listedSource
TypeSafe directModels page Input row: "Text" for both versions; images only with the opt-in header, per TypeSafe's images page (23 Oct 2026). Change, 7 Nov 2026 (first observed 15:29 UTC; after 2 Nov, 11:13 UTC): the Input row lists "Text, images" for both versions and says Jev "also reads PNG and JPEG images anywhere in the request"; the images page still calls images and Box "not yet ... ready for production" and requires the opt-in header.R22-S05; 7 Nov: R27-S05, R27-S06
OpenRouter"text+image->decisions" for typesafe/jev-1.13 and typesafe/jev-1.14R22-S22, R22-S23
Vercel AI Gatewaytypesafe-ai/jev-1.13.0 and typesafe-ai/jev-1.14.0: "text+image→text", tag "vision"; typesafe-ai/jev: text onlyR22-S25, R22-S26
Oppertypesafe/jev-1.14.0: "vision", with the description "Experimental images and box questions require TypeSafe-Danger-Zone-Images: true"; typesafe/jev-1.13.0: textR22-S27
Netlify AI GatewayNot stated on the overview pageR22-S30
Cloudflaretypesafe/jev-1.14.0 page: example requests send an image asset with typesafe/jev-1.14.0; the page does not mention the opt-in header (whether Cloudflare adds it is not stated)R22-S29

A route that lists image input is a listing; it does not show that the route forwards TypeSafe's opt-in header. Which SDKs and integrations send images: Jev with images: does your SDK or integration send them?

6 Oct 2026 table and rechecks to 14 Oct 2026 (Jev 1.13 only)

Earlier recheck, : all six routes list the same IDs and alias targets as on 6 Oct (6 of 6 unchanged). The table below keeps the 6 Oct read. TypeSafe's models page, OpenRouter's typesafe/jev-1.13 endpoints document and the Opper document were byte-identical to 13 Oct; the Cloudflare page text was identical, and Netlify's Jev IDs were unchanged (other providers' rows on that page changed); Vercel still lists typesafe-ai/jev with two providers. OpenRouter's /models list still shows only typesafe/jev-router for TypeSafe. Documented (sources R16-S05, R16-S30, R16-S33, R16-S11, R16-S34, R16-S36, R16-S35, listed below; previous rechecks 13 Oct 2026, 05:18 UTC and 12 Oct 2026, 05:12 UTC)

Recheck, 10 Oct 2026, 05:12 UTC: 6 of 6 unchanged; OpenRouter's endpoint then first stated the 64,000-token context with a 32,000-token prompt limit (it stated 32,000 on 8 Oct), matching TypeSafe's own 64k / 32k limits. The previous rechecks, 7 Oct 2026, 05:19 UTC and 8 Oct 2026, 05:14 UTC, were also unchanged (no update was published on 9 Oct; the 9 Oct evidence notes recorded all six route IDs unchanged). (Sources R12-S21, R12-S25, R12-S26, R12-S50, R12-S28, R12-S46, R12-S29, R12-S47, R12-S33, listed below.)

Documented Exact strings as each source showed them. "Read at" is the pool's access time on 6 Oct 2026. Where the source shows no date of its own, the date column says so.

RouteModel IDsAliases and what they point toCan you pin a version?The source's own dateRead at (UTC)Source
TypeSafe directjev-1.13.0, the only model under "Current models". "Versioned IDs such as jev-1.13.0 are accepted by the model field whether or not they appear in the list."jev-latest → jev-1.13.0 ("The most recent stable, official release. The default in our client SDKs"). jev-preview → jev-1.13.0: it "currently points to the same model as jev-latest. There is no preview build available right now."Yes jev-1.13.0undated; read at 6 Oct 2026, 05:15 UTC05:15:34TypeSafe models page (R9-S21)
OpenRoutertypesafe/jev-1.13. Its one provider endpoint is named TypeSafe | typesafe/jev-1.13-20260917. typesafe/jev-router is a separate router product, not a Jev version.~typesafe/jev-latest: "This model always redirects to the latest model in the Jev family"; its page shows "Latest Jev 1.13". No jev-preview alias found on the two model APIs and pages read.Minor version only typesafe/jev-1.13. Whether a patch-level ID or the dated build name is accepted is not stated.Page: "Released Sep 18, 2026". API created: 18 Sep 2026, 00:01 UTC (both IDs)05:15:34; 05:22:38–05:22:40models API, typesafe/jev-1.13 (R9-S25); models API, ~typesafe/jev-latest (R9-S110); model page (R9-S111); Jev guide (R9-S27)
Vercel AI Gatewaytypesafe-ai/jev onlyNone listed. Which Jev version typesafe-ai/jev serves is not stated in the API or on the model page.No unversioned ID onlyModel page: "Release Date 09 / 15 / 2026"; API released: 15 Sep 202605:15:34; 05:24:29models API (R9-S28); endpoints API (R9-S49); model page (R9-S113)
Cloudflare Workers AItypesafe/jevNone listed. The page's example response shows "model" : "jev-1.13.0"; that is an example, not a statement of what is served now. The ID itself is unversioned.No unversioned ID onlyundated; read at 6 Oct 2026, 05:15 UTC05:15:34Cloudflare model page (R9-S29)
Netlify AI Gatewayjev-1.13.0, jev-latest, jev-preview, listed as "Models served directly" for TypeSafe (passed to TypeSafe's own API through @typesafe-ai/sdk)jev-latest and jev-preview are listed, but Netlify does not state their targets (TypeSafe's statement in the first row applies). "systemOne uses jev-latest by default."Yes jev-1.13.0"Last updated: Sep 17, 2026"05:15:35Netlify AI Gateway overview (R9-S51)
Oppertypesafe/jev-1.13.0 (API model_id jev-1.13.0)The API entry for typesafe/jev-1.13.0 carries "aliases":["typesafe/jev-latest","typesafe/jev-preview"], so both point to it in Opper's catalogue at 05:22:40 UTC.Yes typesafe/jev-1.13.0Page: "Verified by Opper on 2026-09-18"; API undated05:15:34; 05:22:40Opper model page (R9-S33); models API (R9-S114)

Count: versioned ID possible on 4/6 routes (TypeSafe, Netlify and Opper at 1.13.0; OpenRouter at 1.13); unversioned only on 2/6 (Vercel typesafe-ai/jev, Cloudflare typesafe/jev). Request shape, price and context per route: route matrix. Vercel's two providers for typesafe-ai/jev and what that means for data: route matrix note and data handling by route.

What TypeSafe says about its aliases

  • Alias rule: "An alias moves when a new release ships, so the answers behind it can change without a change on your side. … pin that version's ID instead of the alias." (models page, read 6 Oct 2026, 05:15 UTC) On 16 Oct 2026 (05:21 UTC) the page reads: "An alias moves when a new release ships, so its answers can change without any change to your code. … If you have tuned confidence thresholds against one version, send that version's ID instead of the alias, and switch to the new version when you are ready." (R17-S05) Same wording on 24 Oct 2026, 05:12 UTC (R23-S05).
  • Preview: since 14 Oct 2026, jev-preview → jev-1.14.0 (models page, 16 Oct 2026, 05:21 UTC; R17-S05). Until at least 14 Oct 2026, 16:46 UTC the page said: "jev-preview currently points to the same model as jev-latest. There is no preview build available right now." That sentence was gone from 16 Oct to at least 23 Oct 2026; on 24 Oct 2026, 05:12 UTC it is back, with both aliases on jev-1.14.0 (R23-S05).
  • Next move: TypeSafe said on 14 Oct 2026 that jev-latest would move to jev-1.14.0 "in a week"; on 23 Oct 2026, 05:45 UTC, it still pointed to jev-1.13.0, and TypeSafe had published no date for the move (blog post dated 14 Oct 2026, R17-S09; models page and post re-read 23 Oct, R22-S05, R22-S09). Until then this was TypeSafe's stated plan, not an observed change. The move was first seen on 24 Oct 2026, 05:12 UTC (it had not happened at 23 Oct 2026, 05:45 UTC). TypeSafe has published no 1.13 deprecation date; the post says it intends "60 days warning" first (R23-S05, R23-S09).
  • Response: The response's model field "reports the versioned ID that answered" (TypeSafe direct).
  • History: Until 14 Oct 2026 the models page listed one version, jev-1.13.0. On 16 Oct 2026 it lists two (jev-1.14.0, jev-1.13.0), with no deprecation date; TypeSafe's post says it intends 60 days' warning before jev-1.13.0 is deprecated and 30 days for jev-1.14.0 (R17-S09). TypeSafe's docs changelog still returned HTTP 404. The exact time the models page changed is known only as between 14 Oct 2026, 16:46 UTC and 16 Oct 2026, 05:21 UTC. The jev-latest move to jev-1.14.0 happened between 23 Oct 2026, 05:45 UTC and 24 Oct 2026, 05:12 UTC; on 24 Oct the page still lists both versions with no deprecation date, and the docs changelog address still returns HTTP 404 (R23-S05, R23-S21).

Documented TypeSafe's GET /v1/models list, which the docs say carries the aliases and a release_date per name, needs a key and was not read.

What to pin

  1. Where a versioned ID is accepted, write it. jev-1.13.0 or jev-1.14.0 on TypeSafe direct and Netlify; typesafe-ai/jev-1.13.0 or typesafe-ai/jev-1.14.0 on Vercel; typesafe/jev-1.13.0 or typesafe/jev-1.14.0 on Opper (1.14 listed when checked on 18 Oct 2026, 05:20 UTC); typesafe/jev-1.13 or typesafe/jev-1.14 on OpenRouter (minor version only); typesafe/jev-1.14.0 on Cloudflare (1.14 only, as written in its 1.14 page's example requests, checked 23 Oct 2026, 05:23 UTC; not tested). TypeSafe's own wording (models page, 16 Oct 2026): "If you have tuned confidence thresholds against one version, send that version's ID instead of the alias, and switch to the new version when you are ready." See confidence thresholds.
  2. On Cloudflare you cannot pin 1.13. For 1.13 Cloudflare lists only the unversioned typesafe/jev on its Jev overview page, and does not state which Jev version typesafe/jev serves; Vercel's unversioned typesafe-ai/jev does not state it either (until 14 Oct 2026 it was Vercel's only Jev ID). On Cloudflare, the documented example response includes a model field ("jev-1.13.0"); if your responses carry it, log it. Whether every Cloudflare response carries it, and whether Vercel's responses report a versioned ID, was not checked. For 1.14, Cloudflare's typesafe/jev-1.14.0 page shows example requests that write typesafe/jev-1.14.0 (checked 23 Oct 2026, 05:23 UTC; the page was first seen by this catalogue on 21 Oct 2026; it may have been listed earlier); whether a request with that ID is accepted and pins 1.14 was not tested (Cloudflare row).
  3. On TypeSafe direct, log the response's model field even when you pin: TypeSafe says it reports the versioned ID that answered.
  4. If you use an alias, on 16 Oct 2026 jev-latest → jev-1.13.0 and jev-preview → jev-1.14.0 on TypeSafe's models page, and TypeSafe says jev-latest moves to 1.14 "in a week". If you tuned thresholds on 1.13, pin jev-1.13.0 before the alias moves. Netlify lists both aliases without stating targets. Recheck the models page before you rely on an alias target. (Until 14 Oct 2026 both aliases pointed to jev-1.13.0.) On 24 Oct 2026, 05:12 UTC both aliases point to jev-1.14.0 on TypeSafe's models page, while Opper's typesafe/jev-latest still pointed to jev-1.13.0 at 05:15 UTC (R23-S05, R23-S27); if your thresholds were tuned on 1.13, send jev-1.13.0.

Documented Advice built from the route sources above; no route was called.

Which model the SDKs send by default

TypeSafe's models page says jev-latest is "The default in our client SDKs" (read 6 Oct 2026, 05:15 UTC; same wording 16 Oct 2026, 05:21 UTC). Documented Package files read on 16 Oct 2026 (nothing installed or run): typesafe-sdk 0.7.5 and @typesafe-ai/sdk 0.7.0 still default to jev-latest, so their default model changes when the alias moves; @ai-sdk/typesafe-ai 3.0.20 lists jev-1.13.0, jev-1.14.0 and jev-latest as model IDs (R17-S37, R17-S38, R17-S39). The registry versions were unchanged on 24 Oct 2026, 05:18 UTC (typesafe-sdk 0.7.5, @typesafe-ai/sdk 0.7.0, @ai-sdk/typesafe-ai 3.0.26; R23-S41); TypeSafe's SDKs were still unchanged (JS @typesafe-ai/sdk 0.7.0, Python typesafe-sdk 0.7.5) when checked on 30 Oct 2026, 05:21 UTC (R24-S35, R24-S36, R24-S39), and @ai-sdk/typesafe-ai 3.0.30 was released on 29 Oct 2026 (this site last read the provider at 3.0.26; not re-read; R24-S35), so a client that sends no model gets jev-latest, which on TypeSafe's API pointed to jev-1.14.0 from the move first seen on 24 Oct 2026, 05:12 UTC (nothing was run). The default of each SDK and framework package was not checked package by package on 6 Oct 2026 (the planned search of @ai-sdk/typesafe-ai, the LangChain packages, Pydantic AI, @effect/ai-typesafe, typesafe-spring-ai and the n8n node was not done). The defaults recorded in earlier source reads are on TypeScript SDK, Python SDK and framework integrations.

What was not verified

  • What each route actually serves: no request was sent to any route, and no agent, SDK or Jev call was run.
  • Whether OpenRouter accepts a patch-level ID (typesafe/jev-1.13.0) or the dated build name (jev-1.13-20260917) as a model ID.
  • Whether Vercel or Cloudflare will move their unversioned IDs to 1.14, and how they would announce it. Not stated on the pages read on 18 Oct 2026, nor on 24 Oct 2026, 05:15 UTC.
  • What a request to Netlify's jev-latest, OpenRouter's ~typesafe/jev-latest, Vercel's typesafe-ai/jev or Cloudflare's typesafe/jev returns since TypeSafe's alias moved: none of these listings states a target on 24 Oct 2026, and no request was sent.
  • The exact time jev-latest moved: between 23 Oct 2026, 05:45 UTC and 24 Oct 2026, 05:12 UTC. No dated statement was found on TypeSafe's models page, blog index, 1.14 post, docs changelog address or llms.txt (24 Oct 2026, 05:12–05:13 UTC; R23-S08, R23-S09, R23-S20, R23-S21); posts on X were not checked.
  • Which limit Vercel's 32,000 context field means (all three Jev IDs, 18 Oct 2026): Vercel does not define the field; it matches TypeSafe's 32k per-question limit, not the 64k request limit. Not confirmed.
  • Whether any route forwards TypeSafe's image opt-in header: the image fields are listings; no image was sent.
  • Any image, Box or long-context behaviour: no request was sent.
  • Route changelogs: only TypeSafe's was checked, and it returned 404. No OpenRouter, Vercel, Cloudflare or Opper changelog was read; Netlify's TypeSafe changelog post was not reread.
  • SDK default models beyond TypeSafe's statement.
  • TypeSafe's keyed GET /v1/models list.

Sources and check times (6 Oct to 9 Nov 2026, UTC)

9 Nov 2026 recheck: read 11:07:31–11:11:43 UTC (no check between 8 Nov, 05:24 UTC and 9 Nov, 11:07 UTC)
  • R29-S05: TypeSafe models page, 11:07:31 (8,177 bytes, identical to the 8 Nov copy): jev-latest and jev-preview → jev-1.14.0 ("There is no preview build available right now"); jev-1.13.0 listed at the same price as 1.14; no deprecation date.
  • R29-S06, R29-S11: TypeSafe images page and docs changelog (11:07:31): both identical to the 8 Nov copies; the changelog still has one entry, "Jev 1.14", dated October 14, 2026; no deprecation listed.
  • R29-S08, R29-S09: TypeSafe blog index, 11:07:34: the same eight posts as on 8 Nov. The blog post on 1.14, 11:07:34: still says jev-1.13.0 "will be available for a while" and promises "60 days warning" before it is deprecated.
  • R29-S24: OpenRouter models API (461 IDs, as on 8 Nov; typesafe/jev-router is still the only TypeSafe ID in that list) and the 1.13 and 1.14 endpoints APIs, 11:11:42: provider TypeSafe, 262,144-token context, $0.042 per million input tokens; unchanged.
  • R29-S25: Vercel AI Gateway models list (498 IDs, as on 8 Nov), 11:11:42: the same three Jev IDs (typesafe-ai/jev, typesafe-ai/jev-1.13.0, typesafe-ai/jev-1.14.0) and 32,000-token context field.
  • R29-S26: Opper model search for typesafe/jev-latest and typesafe/jev-preview, 11:11:42: typesafe/jev-latest is still an alias of typesafe/jev-1.13.0; typesafe/jev-preview is an alias of typesafe/jev-1.14.0.
  • R29-S27: Netlify AI Gateway overview, 11:11:43: the same five IDs (jev-1.13.0, jev-1.14.0, jev-latest, jev-preview, jev-router).
  • R29-S28: Cloudflare model page (typesafe/jev) and catalog page for typesafe/jev-1.14.0, 11:11:43: both online, $0.042 per million input tokens; no deprecation text.
8 Nov 2026 recheck: read 05:17:00–05:24:51 UTC (no check between 7 Nov, 15:34 UTC and 8 Nov, 05:17 UTC)
  • R28-S05: TypeSafe models page, 05:17:00 (8,177 bytes, identical to the 7 Nov copy): jev-latest and jev-preview → jev-1.14.0 ("There is no preview build available right now"); jev-1.13.0 listed at the same price as 1.14; no deprecation date.
  • R28-S06, R28-S11: TypeSafe images page (05:17:00) and docs changelog (05:17:02): both identical to the 7 Nov copies; the changelog still has one entry, "Jev 1.14", dated October 14, 2026; no deprecation listed.
  • R28-S08, R28-S09: TypeSafe blog index, 05:17:06: the same eight posts as on 7 Nov. The blog post on 1.14, 05:17:07: still says jev-1.13.0 "will be available for a while" and promises "60 days warning" before it is deprecated.
  • R28-S40: OpenRouter models API (461 IDs; 460 on 7 Nov; typesafe/jev-router is still the only TypeSafe ID in that list) and the 1.13 and 1.14 endpoints APIs, 05:24:50: provider TypeSafe, 262,144-token context, $0.042 per million input tokens; unchanged.
  • R28-S41: Vercel AI Gateway models list (498 IDs, as on 7 Nov), 05:24:50: the same three Jev IDs (typesafe-ai/jev, typesafe-ai/jev-1.13.0, typesafe-ai/jev-1.14.0) and 32,000-token context field.
  • R28-S42: Opper model search for typesafe/jev-latest and typesafe/jev-preview, 05:24:50: typesafe/jev-latest is still an alias of typesafe/jev-1.13.0; typesafe/jev-preview is an alias of typesafe/jev-1.14.0.
  • R28-S43: Netlify AI Gateway overview, 05:24:51: the same five IDs (jev-1.13.0, jev-1.14.0, jev-latest, jev-preview, jev-router).
  • R28-S44: Cloudflare model page (typesafe/jev) and catalog page for typesafe/jev-1.14.0, 05:24:51: both online, $0.042 per million input tokens; no deprecation text.
7 Nov 2026 recheck: read 15:29:35–15:38:10 UTC (no check between 2 Nov and 7 Nov)
  • R27-S05: TypeSafe models page, 15:29:35 (8,177 bytes; 8,353 on 2 Nov): jev-latest and jev-preview → jev-1.14.0 ("There is no preview build available right now"); jev-1.13.0 listed at the same price as 1.14; no deprecation date. Changed since 2 Nov in other rows: input "Text, images" for both models, a "Question types" row (Box needs Jev 1.14), the "Language support" section removed.
  • R27-S03: TypeSafe quickstart, 15:29:35: lists Box as a primitive ("Where is it in this image?").
  • R27-S06: TypeSafe images page, 15:29:35: "Dreamer-ready. Images and Box questions aren't yet up to our standards to call ready for production"; the TypeSafe-Danger-Zone-Images: true header is still required; two more examples send jev-latest.
  • R27-S221 to R27-S223: search suggestions for "jev 1.14 vs" from Google (suggestqueries, client=firefox, 15:34:03: one completion, "jev 1.14 vs 1.13"), Bing (api.bing.com/osjson.aspx, 15:34:04: none) and DuckDuckGo (duckduckgo.com/ac, 15:34:04: none). A demand signal, not a volume.
  • R27-S224, R27-S225: GitHub issue search (api.github.com/search/issues), 15:34:04–15:34:05: "jev-1.13" pin (2,069 results) and "jev-1.14" "jev-1.13" (416 results); totals include unrelated matches.
  • R27-S226 to R27-S233: the eight GitHub issues and pull requests in who stayed on 1.13, each opened 15:34:15–15:34:19 (links in the table). R27-S43: ConfusedSky/jev-tests #33 re-read 15:40:14, quote present, still open.
  • R27-S08, R27-S09: TypeSafe blog index, 15:38:10: eight posts; the newest, "Don't Call It a Decision Model" (dated 3 Nov 2026), is about naming and has no access, price, alias or deprecation text; the latest release post is still the 1.14 post. The blog post on 1.14, 15:30:34: still says jev-1.13.0 "will be available for a while" and promises "60 days warning" before it is deprecated.
  • R27-S11: docs changelog, 15:29:35: HTTP 200, a new page (HTTP 404 on 2 Nov); one entry, "Jev 1.14", dated October 14, 2026; no deprecation listed.
  • R27-S19: OpenRouter models API (460 IDs; 452 on 2 Nov; typesafe/jev-router is still the only TypeSafe ID in that list) and the 1.13 and 1.14 endpoints APIs, 15:29–15:34: provider TypeSafe, 262,144-token context, $0.042 per million input tokens; unchanged.
  • R27-S20: Vercel AI Gateway models list (498 IDs, as on 2 Nov), 15:34:31: the same three Jev IDs (typesafe-ai/jev, typesafe-ai/jev-1.13.0, typesafe-ai/jev-1.14.0) and 32,000-token context field.
  • R27-S21: Opper model search for typesafe/jev-latest and typesafe/jev-preview, 15:34:31: typesafe/jev-latest is still an alias of typesafe/jev-1.13.0; typesafe/jev-preview is an alias of typesafe/jev-1.14.0.
  • R27-S22: Netlify AI Gateway overview, 15:34:31: the same five IDs (jev-1.13.0, jev-1.14.0, jev-latest, jev-preview, jev-router).
  • R27-S23: Cloudflare model page (typesafe/jev) and catalog page for typesafe/jev-1.14.0, 15:34:31: both online, $0.042 per million input tokens.
2 Nov 2026 recheck: read 10:47:38–10:54:45 UTC (no check between 31 Oct and 2 Nov)
  • R26-S05: TypeSafe models page, 10:47:38 (8,353 bytes), identical to the 31 Oct copy: jev-latest and jev-preview → jev-1.14.0 ("There is no preview build available right now"); jev-1.13.0 listed at the same price and context limits as 1.14; no deprecation date.
  • R26-S08, R26-S09: TypeSafe blog index (the same 7 posts; latest the 1.14 post), 10:47:40, and the blog post on 1.14, 10:48:37: still says jev-1.13.0 "will be available for a while" and promises "60 days warning" before it is deprecated.
  • R26-S11: docs changelog address, 10:48:37: HTTP 404.
  • R26-S26: OpenRouter models API (452 IDs; 456 on 31 Oct; typesafe/jev-router is still the only TypeSafe ID in that list) and the 1.13 and 1.14 endpoints APIs, 10:54:40: provider TypeSafe, 262,144-token context, $0.042 per million input tokens; unchanged.
  • R26-S27: Vercel AI Gateway models list (498 IDs; 499 on 31 Oct), 10:54:41: the same three Jev IDs (typesafe-ai/jev, typesafe-ai/jev-1.13.0, typesafe-ai/jev-1.14.0) and 32,000-token context field.
  • R26-S28: Opper model search for typesafe/jev-latest, typesafe/jev-preview and typesafe/jev-1.13.0, 10:54:45: typesafe/jev-latest is still an alias of typesafe/jev-1.13.0; typesafe/jev-preview is an alias of typesafe/jev-1.14.0.
  • R26-S29: Netlify AI Gateway overview, 10:54:42: the same five IDs (jev-1.13.0, jev-1.14.0, jev-latest, jev-preview, jev-router).
  • R26-S30: Cloudflare model page (typesafe/jev) and catalog page for typesafe/jev-1.14.0, 10:54:42: unchanged, $0.042 per million input tokens.
31 Oct 2026 recheck: read 05:11:10–05:14:02 UTC
  • R25-S05: TypeSafe models page, 05:11:10 (8,353 bytes), identical to the 30 Oct copy: jev-latest and jev-preview → jev-1.14.0 ("There is no preview build available right now"); jev-1.13.0 listed at the same price and context limits as 1.14; no deprecation date.
  • R25-S08, R25-S09: TypeSafe blog index (the same 7 posts; latest the 1.14 post), 05:11:13, and the blog post on 1.14, 05:11:58: still says jev-1.13.0 "will be available for a while" and promises "60 days warning" before it is deprecated.
  • R25-S11: docs changelog address, 05:11:13: HTTP 404.
  • R25-S24, R25-S25: OpenRouter models API (456 IDs, as on 30 Oct) and the 1.13, 1.14 and ~typesafe/jev-latest endpoints APIs, 05:14: IDs and the router wording unchanged.
  • R25-S26: Vercel AI Gateway models list (499 IDs; 500 on 30 Oct) and the typesafe-ai/jev endpoints, 05:14: the same three Jev IDs and 32,000-token context field.
  • R25-S27: Opper model search for typesafe/jev-latest, typesafe/jev-preview and typesafe/jev-1.13.0, 05:14: typesafe/jev-latest is still an alias of typesafe/jev-1.13.0.
  • R25-S28, R25-S29: Cloudflare model page (typesafe/jev; examples return jev-1.13.0) and catalog page for typesafe/jev-1.14.0, 05:14: unchanged, $0.042 per million input tokens.
  • R25-S30: Netlify AI Gateway overview, 05:14: the same five IDs (jev-1.13.0, jev-1.14.0, jev-latest, jev-preview, jev-router).
30 Oct 2026 recheck: read 05:14:33–05:21:02 UTC (no check between 24 and 30 Oct)
  • R24-S05: TypeSafe models page, 05:14:33 (8,353 bytes), compared line by line with the 24 Oct copy: alias table and preview callout unchanged (jev-latest and jev-preview → jev-1.14.0); jev-1.13.0 listed at the same price and context limits as 1.14; no deprecation date.
  • R24-S08, R24-S09: TypeSafe blog index (the same 7 posts; latest the 1.14 post) and the blog post on 1.14, 05:14:33: wording unchanged ("in a week", "available for a while", "60 days warning before jev-1.13.0 is formally deprecated").
  • R24-S20, R24-S21: TypeSafe docs llms.txt (19,809 bytes; not compared line by line) and the docs changelog address (HTTP 404), 05:14:33.
  • R24-S22 to R24-S24: OpenRouter 1.13 and 1.14 endpoints APIs (same endpoints, context and price), the models API (456 IDs at 05:17 UTC; 469 on 24 Oct; the change is in other providers' models) and ~typesafe/jev-latest (wording unchanged; no endpoint listed), 05:17:27.
  • R24-S25, R24-S26: Vercel AI Gateway endpoints for typesafe-ai/jev, typesafe-ai/jev-1.13.0 and typesafe-ai/jev-1.14.0 (same IDs, providers and 32,000-token context), and the models list (500 IDs at 05:17 UTC; 480 on 24 Oct), 05:17:27.
  • R24-S27: Opper model search for 1.13.0 (alias typesafe/jev-latest, model_id jev-1.13.0), 1.14.0 (alias typesafe/jev-preview) and typesafe/jev-latest, 05:17:27.
  • R24-S28, R24-S29: Cloudflare model page (typesafe/jev; examples return jev-1.13.0) and catalog page for typesafe/jev-1.14.0, 05:17:27: unchanged.
  • R24-S30: Netlify AI Gateway overview, 05:17:27: unchanged.
  • R24-S35, R24-S36, R24-S39: npm and PyPI registry documents and TypeSafe's SDK release feeds, 05:20–05:21:02: @typesafe-ai/sdk 0.7.0 and typesafe-sdk 0.7.5, unchanged.
24 Oct 2026 recheck: read 05:12:29–05:18:52 UTC
  • R23-S05: TypeSafe models page, 05:12:29 (8,275 bytes; re-read 05:39 UTC, byte-identical): jev-latest → jev-1.14.0, jev-preview → jev-1.14.0, with the callout "jev-preview currently points to the same model as jev-latest. There is no preview build available right now."; jev-1.13.0 listed at the same price and context limits as 1.14; no deprecation date. Apart from the alias row and the callout, the changed lines only turn relative links into absolute ones.
  • R23-S06 and R23-S19: TypeSafe images page (05:12:30; "Jev 1.13 and Jev 1.14 both accept images. Box questions need Jev 1.14."; examples send jev-latest at L29, L169, L215) and Box page (05:12:33; example sends jev-latest at L33).
  • R23-S08, R23-S09: TypeSafe blog index (7 posts; latest the 1.14 post) and the blog post on 1.14, 05:12:31–05:12:32: still says "in a week", "available for a while" and "60 days warning before jev-1.13.0 is formally deprecated".
  • R23-S20, R23-S21: TypeSafe docs llms.txt (same size as on 23 Oct) and the docs changelog address (HTTP 404), 05:12:33.
  • R23-S22 to R23-S24: OpenRouter 1.13 and 1.14 endpoints APIs, the models API (469 IDs) and ~typesafe/jev-latest (no endpoint listed), 05:15:37–05:18:51.
  • R23-S25, R23-S26: Vercel AI Gateway endpoints for typesafe-ai/jev, typesafe-ai/jev-1.13.0 and typesafe-ai/jev-1.14.0, and the models list (480 IDs; three TypeSafe IDs), 05:15:38–05:15:40.
  • R23-S27: Opper model search for 1.13.0 (alias typesafe/jev-latest, model_id jev-1.13.0), 1.14.0 (alias typesafe/jev-preview) and typesafe/jev-latest (returns the 1.13.0 entry), 05:15:40–05:15:41.
  • R23-S28, R23-S29: Cloudflare model page (typesafe/jev; examples return jev-1.13.0) and catalog page for typesafe/jev-1.14.0, 05:15:42.
  • R23-S30: Netlify AI Gateway overview (jev-1.13.0, jev-1.14.0, jev-latest, jev-preview, jev-router), 05:15:42.
  • R23-S40: search suggestions from Google, Bing and DuckDuckGo, 05:18. A demand signal, not a volume.
  • R23-S41: npm and PyPI registry entries for the SDK packages, 05:18:08.
23 Oct 2026 recheck: read 05:18:59–05:23:23 UTC; models page re-read 05:45:14 UTC
21 Oct 2026 recheck: read 05:11:47–05:13:59 UTC
19 Oct 2026 recheck: read 05:22:23–05:24:19 UTC
  • R19-S05: TypeSafe models page, 05:22:23: jev-latest → jev-1.13.0, jev-preview → jev-1.14.0; no deprecation date (byte-identical to 16 and 18 Oct).
  • R19-S09: TypeSafe blog post on 1.14, 05:22:22: still says jev-latest moves "in a week" and jev-1.13.0 "will be available for a while".
  • R19-S22 to R19-S24: OpenRouter 1.13 and 1.14 endpoints APIs (byte-identical to 18 Oct) and the models API (471 IDs; only typesafe/jev-router for TypeSafe; no ID added or removed), 05:24:15–05:24:16.
  • R19-S25 to R19-S28: Vercel AI Gateway endpoints for typesafe-ai/jev, typesafe-ai/jev-1.14.0 and typesafe-ai/jev-1.13.0 (only uptime values changed) and the models list (context field 32,000 for all three), 05:24:16.
  • R19-S30, R19-S31: Cloudflare model page (jev-1.13.0 examples; no 1.14) and /ai/models/typesafe/jev-1.14/ (generic models page), 05:24:16.
  • R19-S32, R19-S33: Opper 1.13.0 (alias typesafe/jev-latest) and Opper 1.14.0 (alias typesafe/jev-preview), 05:24:17.
  • R19-S34: Netlify AI Gateway overview (lists jev-1.13.0 and jev-1.14.0), 05:24:18.
  • R19-S35 to R19-S38: Microsoft Learn partner models, Bedrock model cards, Workers AI models (no "Jev" or "TypeSafe" string) and the Cloudflare changelog (no Jev item), 05:24:19.
18 Oct 2026 recheck: read 05:17:46–05:20:15 UTC
  • R18-S05: TypeSafe models page, 05:17:46: jev-latest → jev-1.13.0, jev-preview → jev-1.14.0 (byte-identical to 16 Oct).
  • R18-S09: TypeSafe blog post on 1.14 (dated 14 Oct 2026): still says jev-latest moves "in a week".
  • R18-S22 to R18-S24: OpenRouter endpoints APIs for typesafe/jev-1.13 and typesafe/jev-1.14 (byte-identical) and the models API (only typesafe/jev-router for TypeSafe), 05:20:14.
  • R18-S25 to R18-S28: Vercel AI Gateway models API and the endpoints APIs for typesafe-ai/jev, typesafe-ai/jev-1.13.0 and typesafe-ai/jev-1.14.0, 05:20:14: context_window 32000 for all three; only uptime figures changed.
  • R18-S29: Vercel AI Gateway docs, "Models and Providers" (last updated 2026-10-02), 05:20:14: no definition of the context field.
  • R18-S30 and R18-S31: Cloudflare model page (example still jev-1.13.0) and the typesafe/jev-1.14 address (generic catalog page), 05:20:14.
  • R18-S32 and R18-S33: Opper models API for typesafe/jev-1.13.0 (alias typesafe/jev-latest) and typesafe/jev-1.14.0 (alias typesafe/jev-preview, context 64,000, $0.042 per million input), 05:20:14.
  • R18-S34: Netlify AI Gateway overview, 05:20:14: jev-1.13.0 and jev-1.14.0.
  • R18-S35, R18-S36, R18-S37: Microsoft Learn models from partners, Amazon Bedrock model cards, Workers AI catalog, 05:20:15: Jev not listed.
16 Oct 2026 recheck: 16 sources, read 05:21:51–05:26:00 UTC
14 sources, read 05:15:34–05:24:29 UTC
14 Oct 2026 recheck: 7 sources, read 16:46:02–16:48:49 UTC
13 Oct 2026 recheck: 7 sources, read 05:18:51 UTC
12 Oct 2026 recheck: 7 sources, read 05:12:54–05:12:55 UTC
11 Oct 2026 recheck: 6 sources, read 05:17:31–05:18:15 UTC
10 Oct 2026 recheck: 9 sources, read 05:12:20–05:12:21 UTC
8 Oct 2026 recheck: 9 sources, read 05:14:04–05:14:06 UTC
7 Oct 2026 recheck: 9 sources, read 05:19:14–05:19:16 UTC

Search published pools, pages, reports, and evidence.