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

When the pool checked search suggestions on 6 Oct 2026, 05:19 UTC, 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. 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.

Model IDs and aliases on each route

Rechecked 7 Oct 2026, 05:19 UTC: 6 of 6 routes list the same IDs and alias targets as on 6 Oct. One fetch per route, 05:19:14–05:19:16 UTC; the table below keeps the 6 Oct read. Documented (sources R10-S21, R10-S25, R10-S26, R10-S50, R10-S28, R10-S46, R10-S29, R10-S47, R10-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.

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)
• Preview: "jev-preview currently points to the same model as jev-latest. There is no preview build available right now."
• Response: The response's model field "reports the versioned ID that answered" (TypeSafe direct).
• History: The models page lists one version, jev-1.13.0, with no "previous versions" or deprecation text. TypeSafe's docs changelog.md returned HTTP 404 (05:15:35 UTC). The pool has not seen a Jev version change: there has been one version so far.

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 on TypeSafe direct and Netlify; typesafe/jev-1.13.0 on Opper; typesafe/jev-1.13 on OpenRouter (minor version only). TypeSafe's own wording: "If you have tuned confidence thresholds against a specific version, pin that version's ID instead of the alias." See confidence thresholds.
2. On Vercel and Cloudflare you cannot pin. Neither source states which Jev version the unversioned ID serves. 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.
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, today jev-latest and jev-preview point to the same model on TypeSafe's models page and in Opper's catalogue. Netlify lists both without stating targets. Recheck the models page before you rely on an alias target.

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). Documented 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.