Updated

Desk

The Jev API is a POST to /v1/systemone, and the key comes from a TypeSafe account.

The Jev API is TypeSafe's HTTP endpoint for its System One model. A client POSTs state and typed questions to https://api.typesafe.ai/v1/systemone and reads back a Choice, a Score, or a Noul. On jev-1.14.0 a Box returns four edges. Jev Day 2026 is the October 14, 2026 release. On October 16, at 08:19 UTC, one Box for every vehicle returned one rectangle, n = 3, and type array returned HTTP 400. The API key is a credential from a console.typesafe.ai account. On October 6, 2026 this desk signed in to a new one. Available credits were $0.00. The key is not printed here. The model itself is described on what Jev is.

What is the Jev API?

It is one path, POST /v1/systemone, on api.typesafe.ai.

The caller sends unstructured state and one or more questions whose answers were declared up front. TypeSafe says those questions are sampled together. The model does not write a paragraph. OpenRouter's listing uses a different path, POST /api/alpha/decisions. Venice documents POST /api/v1/decisions, and also /systemone for a base-URL swap. LiteLLM's proxy exposes POST /typesafe/v1/systemone. The public doors are collected on access.

Where do I get a Jev API key?

A Jev API key is issued to a TypeSafe console account at console.typesafe.ai.

On September 20 TypeSafe posted that the waitlist was gone and that new accounts started with $5 of credit. On September 22 it paused new signups and said existing accounts continue. On September 24 it said signups were still closed. On September 27 at 22:30 UTC it posted that capacity had increased, that signups were open, and that new signups no longer get free credits. On October 6, 2026, at 17:05 UTC, a new console account showed available credits of $0.00. On October 8, 2026 the same signed-in console still showed available credits of $0.00, no payment method, and no billing history. The thread is signups paused, then reopened. The September 20 credit is the waitlist post.

Gateway credentials are not that console key. A Vercel deploy uses an OIDC token. Venice uses the same key as its chat and image APIs. LiteLLM keeps the TypeSafe key on the proxy and gives clients a virtual key. Jevflake stores the TypeSafe key as a Snowflake secret and lets SQL callers use jev_noul, jev_choice, and jev_score without seeing it. That package is Jevflake.

What does one call return?

On October 15, 2026, Date header 01:22:13 GMT, a POST with model jev-latest returned HTTP 200 and named jev-1.13.0. A POST with model jev-preview the same second named jev-1.14.0.

The October 15 state was "Help! My payouts have been failing for 3 days." The body asked is_urgent and department. On jev-1.13.0, is_urgent returned 0.95. department selected billing, with probabilities 0.88, 0.12, and 0.0, and confidence 0.82. Usage was 361 input tokens and 57 output tokens. On jev-1.14.0, urgency stayed 0.95 and billing was 0.86 at confidence 0.79. The September 30 three-question POST, which also named jev-1.13.0, included a Score for frustration at 1.04 and used 426 input tokens. Vercel, Cloudflare, Netlify, OpenRouter, Venice, and LiteLLM were not called. Date headers 03:03:53 GMT to 03:03:56 GMT, six POSTs with model jev-preview named jev-1.14.0. Four payouts tickets in English, Chinese, Spanish, and Japanese came back at language confidence 1.0, all billing. Chinese frustration scored 1.37 at confidence 0.44. Date headers 06:16:20 GMT to 06:16:44 GMT, 32 POSTs plus GET /v1/models. jev-latest still named jev-1.13.0. Three Chinese payouts tickets on jev-1.14.0 scored frustration mean 1.30 at mean confidence 0.54. Date header 11:04:52 GMT, jev-latest still named jev-1.13.0. Date header 14:57:05 GMT, jev-latest still named jev-1.13.0. Date headers 08:49:11 GMT to 08:49:40 GMT October 26, jev-latest and jev-preview named jev-1.14.0. An 850 by 850 PNG in state used 2,238 input tokens. OpenRouter listed typesafe/jev-1.14. This desk did not call OpenRouter. The October 15 pair is on Jev Day 2026 and in the FAQ.

What else accepts a Jev-shaped call?

Several hosts list Jev, and each one publishes its own quota.

Vercel AI Gateway lists typesafe-ai/jev. Cloudflare Workers AI serves typesafe/jev. Netlify's changelog says to install @typesafe-ai/sdk inside Functions. OpenRouter's beta listing is ~typesafe/jev-latest, at TypeSafe's public price, on an alpha decisions endpoint. Venice's beta uses the same $0.042 rate and the 64k / 32k split. MotherDuck's prompt_jev() runs on paid plans. The launch story is the September 15 announcement those listings followed. Stories tagged for products and gateways are grouped under ecosystem and product.

Do I need a Jev API key?

Yes, for TypeSafe's own endpoint at api.typesafe.ai. Vercel, Cloudflare, Netlify, OpenRouter, Venice, and LiteLLM issue their own credentials. A gateway quota is not a console key.

Does jev-latest stay on one model?

Date headers 08:49:11 GMT to 08:49:40 GMT October 26, POSTs with jev-latest and jev-preview named jev-1.14.0. Opened that hour, the models page says both aliases point at jev-1.14.0. On October 15, 2026, Date header 14:57:05 GMT, a POST with model jev-latest named jev-1.13.0, and a POST with model jev-preview named jev-1.14.0. OpenRouter's ~typesafe/jev-latest page already linked Jev 1.14. This desk did not call OpenRouter.

Are new signups open?

On September 27, 2026 at 22:30 UTC TypeSafe posted that signups were open again, and that new signups no longer get free credits. On October 6, 2026, at 17:05 UTC, this desk signed in to a new console account. Available credits were $0.00.