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. 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 September 30, 2026 one POST with model jev-latest returned HTTP 200 and named jev-1.13.0.
The state was "Help! My payouts have been failing for 3 days." The body asked is_urgent, department, and frustration together. is_urgent, a Noul, returned 0.95. department, a Choice, selected billing, with probabilities 0.88, 0.12, and 0.0, and confidence 0.82. frustration, a Score, returned 1.04, with probabilities 0.0, 0.96, and 0.04, and confidence 0.94. Usage was 426 input tokens and 73 output tokens. Vercel, Cloudflare, Netlify, OpenRouter, Venice, and LiteLLM were not called. The same numbers are on access 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?
On September 30, 2026 a POST with model jev-latest returned HTTP 200 and named jev-1.13.0. That is one response, not a promise about the next alias.
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.