How to get access to Jev
Getting access to Jev means joining TypeSafe’s early-access path, then creating a console key (or using a documented gateway). Jev launched in early access on 15 September 2026. The launch post says TypeSafe is “bringing developers off the waitlist as quickly as we can.” Jev is TypeSafe’s System One decision model: text-in, typed-decisions-out.
This page is for builders who already heard of Jev and need a credential path — not a reseller. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. We do not sell, issue, or proxy API keys. This site cannot expedite the queue. Confirm current waitlist and console steps on docs.typesafe.ai. If you need a reading order before you apply, use accessing the unofficial Jev documentation guide.
Steps
- Choose a door. First-party TypeSafe: join the waitlist from typesafe.ai, then open console.typesafe.ai when invited. Vercel AI Gateway: Vercel documents a TypeSafe-compatible API at
https://ai-gateway.vercel.sh/typesafeand the model idtypesafe-ai/jev. You authenticate with an AI Gateway key or Vercel OIDC token — not a TypeSafe first-party alias. - After console access, create a key in the dashboard. Store it as
TYPESAFE_API_KEY. First-party HTTP sendsAuthorization: BearertoPOST https://api.typesafe.ai/v1/systemone. Details: API keys. - Open the official Playground: log in, paste state, add questions. Copy the shape into curl or an official SDK. Do not paste the key into jev.pro.
- Tell procurement the honest envelope: text-in, typed-decisions-out; public list price on the models page; rate limits currently dynamic; data handling and ZDR live on TypeSafe legal pages and your MSA. If they ask for a security whitepaper, send them official legal pages and TypeSafe sales — not a jev.pro PDF.
- Label vendor claims in the same brief. TypeSafe currently lists $0.042 per million input tokens, output free, 250,000 tokens/second, and 1,200 RPM. Those can change.
- Compare doors on Jev channels and channels compared before you mix model ids. First-party setup: Jev on TypeSafe.
Pitfalls
- Buying or requesting a key on this site. There is no checkout. There is no “get key here” button that works.
- Treating Gateway access as a TypeSafe account. It is a different credential and billing surface. Read Vercel’s invoice and TypeSafe’s terms.
- Mixing a TypeSafe bearer token with the Gateway base URL, then filing a 401 as a waitlist bug. 401 means bad or missing auth for that door. Do not retry 401.
- Assuming a self-serve free tier exists because a blog said so. The public models page snapshot we used does not describe one. We will not invent starter credits.
- Sending procurement unofficial speed screenshots as SLAs. TypeSafe’s own speed notes were measured in their evals, not by jev.pro.
After you have a console
The official quick start’s first hands-on surface is the Playground. Then pin a versioned id such as jev-1.13.0 before you tune floors. Neither public path makes jev.pro a reseller. Higher limits, when you need them, are a TypeSafe sales conversation ([email protected] on their models page) — not a ticket we can raise.
English-only public pages on this site will not localize the waitlist copy. If TypeSafe publishes a new access path, believe their docs over this page.
See also
FAQ
Can I buy a key on this site?
No.
Is Gateway access the same as a TypeSafe account?
It is a different credential and billing surface. Read Vercel’s invoice and TypeSafe’s terms.
What if procurement asks for an official security whitepaper?
Send them docs.typesafe.ai legal pages and TypeSafe sales — not a jev.pro PDF.
What this page does not claim
This page does not claim we can invite you, sell a key, or equalize Gateway and first-party contracts. It does not freeze waitlist timing, list price, or RPM.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.