Can I get a Jev (TypeSafe AI) API key today? Signup, waitlist and free-credit timeline
In its first two weeks Jev went from early access through a waitlist, to open to everyone, to signups paused, to signups reopened without free credit for new users. Some third-party pages still show an old state (four are listed below). This page gives the current status with its source and time, and every earlier change with its primary source.
Jev access status · checked
Available to new users: signups open, but new accounts get no free credit. API operational.
- Signups open since
- . Source: post on X by TypeSafe's CEO: "ANYONE CAN SIGN UP", with free credits "temporarily" disabled for new users. Documented
- API operational since
- , when a "System overload" event on the us-east-1 API endpoint (
api.us-east-1.typesafe.ai) was resolved ("System is back to normal"). The status page shows that endpoint as "Degraded for 1 hour and 15 minutes"; its text does not give the start time (about 20:00 UTC if the stated duration ends at the resolution; an inference, not a stated time). The page's own history lists no event dated after 30 Oct (read 9 Nov 2026, 11:07 UTC). The event before the 30 Oct one was a 45-minute "Elevated Latency" event on the same endpoint, resolved on 14 Oct, 22:52 UTC. The mainapi.typesafe.aientry's last incident was on 28 Sep (as read on 30 Oct). Status page: "All services are online" (last updated 9 Nov 2026, 11:06 UTC; read 11:07 UTC). API uptime over the last 90 days: 99.882% (the page shows three figures without labelling their windows; the third is read as the 90-day figure, as before); 99.883% on 8 Nov. Documented - Conditions for a new account
- No free credit (since 27 Sep). Rate limits: TypeSafe's models page lists no numbers; it says "Rate limits are set per organization" and shows them in the developer console, which the pool cannot see without an account (until 14 Oct the page listed 100K tokens and 80 requests per second; errors and rate limits). List price $0.042 per million input tokens for both
jev-1.14.0andjev-1.13.0, output free, unchanged since 28 Sep. An opt-in header (TypeSafe-Danger-Zone-Long-Context) raises both context limits to 262k tokens at the same price per token; the defaults stay 64k per request and 32k per question. Model aliases: on TypeSafe's APIjev-latestpoints tojev-1.14.0, unchanged since it was first seen on 24 Oct 2026, 05:12 UTC (on 23 Oct 2026, 05:45 UTC it still pointed tojev-1.13.0; TypeSafe published no dated statement of the move), andjev-previewalso points tojev-1.14.0("There is no preview build available right now").jev-1.13.0is still listed with its own ID and price, and no deprecation date is published (versions and aliases). Checked 9 Nov 2026, 11:07 UTC. Documented - How it was checked
- The pool did not see signup itself. On 9 Nov
console.typesafe.aianswered (HTTP 200) on/and/signupwith a sign-in page ("Sign in or create an account through Google or your email") and no waitlist or invitation text, as on 7 and 8 Nov. It showed a sign-in page with no waitlist text on 16, 18, 19, 20, 21, 23, 24, 30 and 31 Oct, returned an HTTP 403 block page on 2 Nov, and returned HTTP 403 until 14 Oct. No form was submitted and the pool has no account, so the status rests on TypeSafe's CEO statement (re-read on 9 Nov), its status page and its docs, not on the pool signing up. - Without a TypeSafe account
- OpenRouter: "There's no waitlist or separate TypeSafe account" (OpenRouter guide, checked 9 Nov 2026, 11:08 UTC). Documented
All checks behind this status (9 Nov 2026, 11:07 UTC)
console.typesafe.ai/and/signup(11:07 UTC): HTTP 200, a sign-in page: "Welcome to TypeSafe Sign in or create an account through Google or your email", with a link to the Master Customer Agreement and the Privacy Policy; no waitlist or invitation text (the same page as on 7 and 8 Nov; on 2 Nov both returned an HTTP 403 block page). Seen as a page only: no form was submitted; the pool has no account, so signup itself was not observed.- CEO post, read through X's public embed endpoint (
publish.x.com, 11:07 UTC): HTTP 200, text unchanged from the 16, 18, 19, 20, 21, 23, 24, 30 and 31 Oct and 2, 7 and 8 Nov reads. It still says "ANYONE CAN SIGN UP" and that free credits are "temporarily" disabled for new users. docs.typesafe.ai/introduction/quickstart.md: HTTP 200, 15,156 bytes, identical to the 8 Nov copy. No waitlist, pause, credit or free-tier text.typesafe.ai: HTTP 200, no "waitlist", "credit", "free", "1.15" or "deprecat" text found.typesafe.ai/blog: HTTP 200, the same eight posts as on 8 Nov; the newest is still "Don't Call It a Decision Model" (dated 3 Nov 2026, about naming), and the newest release post is still "Jev: For the builders AND dreamers" (dated 14 Oct 2026). That post is still online and still says thatjev-1.13.0"will be available for a while" and that TypeSafe intends to give "60 days warning" beforejev-1.13.0is formally deprecated.typesafe.ai/enterprise: HTTP 200, no credit, waitlist, free, "1.15" or deprecation text.status.typesafe.ai(11:07 UTC): HTTP 200. "All services are online", last updated 9 Nov 2026, 11:06 UTC. The page's incident history lists no event dated after 30 Oct; the newest entry is still the 30 Oct "System overload" on the us-east-1 endpoint, resolved 30 Oct, 21:15 UTC. Theapi.typesafe.aientry shows 99.941%, 99.848% and 99.882% (8 Nov: 99.942%, 99.842% and 99.883%), without labelling their windows; the third is read as the 90-day figure, as on earlier days.docs.typesafe.ai/models.md: HTTP 200, 8,177 bytes, identical to the 8 Nov copy.jev-latestandjev-previewpoint tojev-1.14.0, and "There is no preview build available right now" is still there.jev-1.13.0is still listed; both versions cost $0.042 per million input tokens, output free; the long-context header applies to both; rate limits are "set per organization", and higher limits are requested through a "rate limit increase request form" (first seen 30 Oct); no deprecation date is given forjev-1.13.0. The input row ("Text, images" for both models), the "Question types" row (Box needs Jev 1.14) and the removal of the "Language support" section, first seen on 7 Nov, are unchanged.docs.typesafe.ai/images.md,docs.typesafe.ai/changelog.mdanddocs.typesafe.ai/legal.md: HTTP 200, all identical to the 8 Nov copies. The changelog still has one entry, "Jev 1.14", dated October 14, 2026; no Jev 1.15 and no deprecation are listed.docs.typesafe.ai/llms.txt: HTTP 200, identical to the 8 Nov copy (143 links; none added or removed). The cookbook page added on 8 Nov, "Verifying LLM answers against their source" (cookbooks/verify_llm_outputs.md), is still listed. No "1.15", "deprecat" or "OpenCode" text in the docs files read.- AI FrontPage homepage (11:07 UTC): no credit or waitlist text found.
- X search: not available to the pool, so newer TypeSafe or CEO posts could not be searched.
- The previous check was on 8 Nov 2026, 05:17 UTC. There was no check between 8 Nov, 05:18 UTC and 9 Nov 2026, 11:07 UTC; for those hours the status page's own history is the record (no event listed).
jev-latest and jev-preview give jev-1.14.0) are unchanged, and jev-1.13.0 still has no deprecation date. The status page's history lists no event between the two checks. The API uptime figure read as the 90-day window is 99.882% (99.883% on 8 Nov). The console sign-in pages answered with the same sign-in page (HTTP 200). TypeSafe's models, images, quickstart, changelog and legal pages and its docs index (llms.txt) are identical to the 8 Nov copies.
Yes. Anyone can sign up at console.typesafe.ai again since 27 September 2026, but new accounts get no free credit for now, so you pay the list price ($0.042 per million input tokens) from the first request. If you do not want a TypeSafe account, OpenRouter serves Jev with its own key and states that no waitlist or separate TypeSafe account is needed. The pool has not signed up itself: console.typesafe.ai showed a sign-in page on 16, 18, 19, 20, 21, 23, 24, 30 and 31 Oct and again on 7, 8 and 9 Nov, returned HTTP 403 until 14 Oct and on 2 Nov (a block page; the sign-in page could not be read that day), and the pool has no account, so the status rests on TypeSafe's CEO statement, its status page and its docs. A Hacker News user wrote on 28 Sep (13:33 UTC) that they "made typesafe.ai account and put down $5"; the comment does not say whether any credit was offered. No second first-hand report has appeared since. Reported
Access for new users since launch, 15 Sep–9 Nov 2026 (latest checks 8 and 9 Nov 2026)
- Early access from a waitlist (15–20 Sep)
- Open to everyone (20–22 Sep)
- Signups paused (22–27 Sep)
- Open, no free credit for new users (from 27 Sep)
Segment lengths follow the dated TypeSafe posts in the timeline below. Existing accounts kept working during the pause. The last segment runs to 9 Nov 2026. The latest checks were on 8 Nov (05:17 UTC) and 9 Nov 2026 (11:07 UTC), with no check between them; the signup and credit sources show no contrary statement dated between the checks.
What to do now
- Direct: sign up at
console.typesafe.aiand create a key. Expect no free credit as a new user until TypeSafe says otherwise. - Through a gateway: OpenRouter needs only an OpenRouter key ("There's no waitlist or separate TypeSafe account"). Vercel AI Gateway, Cloudflare Workers AI, Netlify and Opper each need their own account. Compare them on Where to use Jev.
- Do not buy from lookalike sites. Several sites resell Jev at 3–16× the list price. Check any site against official vs reseller first.
Is Jev free or paid?
Paid. TypeSafe lists $0.042 per million input tokens, with output tokens free; new accounts get no free credit (the CEO called this temporary on 27 Sep; no restoring statement found). No free tier or trial was found on TypeSafe's homepage, Enterprise page, blog (including the 14 Oct Jev 1.14 post and the 3 Nov post on naming), quickstart or models page (checked 9 Nov 2026, 11:07 UTC). The price is the same for jev-1.14.0 and jev-1.13.0. OpenRouter lists the same input price (14 Oct). Documented
Sources: R29-S05 (price for both model IDs; models page), R29-S02 (CEO post), R29-S07 (homepage), R29-S10 (Enterprise page), R29-S08 (blog index), R29-S09 (Jev 1.14 post), R29-S03 (quickstart), all 9 Nov: no free tier or trial found on those pages (8 Nov: R28-S05, R28-S02, R28-S07, R28-S10, R28-S08, R28-S09, R28-S03; 7 Nov: R27-S05, R27-S02, R27-S07, R27-S10, R27-S08 with the 3 Nov post, R27-S09, R27-S03; 2 Nov: R26-S05, R26-S02, R26-S07, R26-S10, R26-S08, R26-S09, R26-S03; on 2 Nov the only "free" text on the models page was "Output tokens are free"). R16-S30 (OpenRouter, 14 Oct). Lookalike sites that call Jev "free" are not a source; see official vs reseller. Cost per decision: worksheet.
Is Jev free? TypeSafe's credit and a third-party route, kept apart
From TypeSafe: new accounts get no free credit. Signups are open; the CEO called the credit pause temporary on 27 Sep 2026, and no contrary statement was found (checked 9 Nov 2026, 11:07 UTC). Documented
Separately, a third-party route; not run by TypeSafe: OpenCode's docs list jev-1.13-free at "Free" input and output per 1M tokens, "available on OpenCode for a limited time", used with an OpenCode Console key under OpenCode's own terms. OpenCode does not say which Jev version it serves and publishes no end date or quota for it. TypeSafe's docs, homepage and blog index did not mention OpenCode as a route (2 Nov 2026, 10:49 UTC). The pool did not use or test this route. Documented (OpenCode docs, read 9 Nov 2026, 11:11 UTC, unchanged since 2 Nov 2026, 10:47 UTC; also read 7 Nov 2026, 15:33 UTC and 8 Nov 2026, 05:24 UTC; there was no check between 8 Nov, 05:24 UTC and 9 Nov 2026, 11:11 UTC; R29-S22, R28-S37, R27-S37, R26-S200, R26-S215 to R26-S217)
Details, prices as published and reported errors: third-party routes outside the six-route table. OpenCode's data terms, quoted with their dates: data privacy.
Timeline of access changes
- Early access; developers admitted from a waitlist
"Today, we are opening early access and bringing developers off the waitlist as quickly as we can." TypeSafe launch post. Documented
- Open to everyone, no waitlist
"Jev is now available to everyone. No waitlist." @typesafeai on X. Outlets dating this 21 Sep are in later time zones. Documented
- $5 new-user credit (about 120M tokens): reported, with a conflict
No primary TypeSafe source for the amount was found. AI FrontPage (22 Sep) and CryptoBriefing (21 Sep) report "$5 in credit (120 million tokens)". lmspedia reports that its own 22 Sep signup "found no credit balance anywhere in the console". The CEO's 27 Sep post implies that new-user credits existed before 27 Sep, without an amount. Reported
- API and console incident, then recovery
"We are back!" (@typesafeai, 21 Sep, 09:53 UTC). The status page shows 20 Sep "Down for 18 minutes" and 21 Sep "API issues, Down for 2 minutes". Documented
- Signups paused; existing accounts keep working
"we have to temporarily pause signups for Jev. We need to ensure quality of service for our existing signups, which will continue to function." @typesafeai on X. Documented
- Two API latency incidents
Resolved 23 Sep, 20:56 UTC and 24 Sep, 07:18 UTC (status page). A third-party page reported signups still paused on 24 Sep. Documented
- Signups reopened; free credit disabled for new users
"good news: ANYONE CAN SIGN UP … bad news: we had to temporarily disable the free credits (just for new users)". Post on X by TypeSafe's CEO (role per typesafe.ai/team). No matching @typesafeai post was found. Documented
- "Degradation in API Traffic", resolved 16:07 UTC
"Elevated latency and error rates are resolved." Status bar: "Down for 11 minutes". Documented
- "Routine operational maintenance"
Listed on the status page as ended 29 Sep, 3:32pm UTC. Documented
- "Console is unavailable."
"The console may experience issues due to regularly applied maintenance." Resolved Sep 29, 2026 at 10:05pm UTC (status page). No API incident was listed. Documented
- Published rate limits changed
TypeSafe's models page now lists 100K tokens per second and 40 requests per second (was 250,000 tokens/s and 1,200 requests/min). An Internet Archive capture of 29 Sep, 19:24:32 UTC still shows the old limits; the pool first saw the new ones on 30 Sep, 20:47 UTC. The exact time is unknown and no changelog entry was found (TypeSafe's model changelog, first seen 7 Nov 2026, has one entry, Jev 1.14 of 14 Oct 2026, and does not mention rate limits; R27-S11). A condition, not a change in who can sign up. Documented
Correction, 1 Oct 2026: this entry said "between 29 Sep, 07:07 UTC and 30 Sep, 20:47 UTC" until 1 Oct; the start is now narrowed with archive captures.
- Recheck: signups open, no new-user credit, API operational
No statement restoring the credit found on TypeSafe's homepage, docs quickstart, Hacker News or AI FrontPage; the CEO post is still online. Status page: "All services are online". Documented
- Recheck: unchanged
Signups open, no new-user credit, API operational. No new status-page event since 29 Sep, 22:05 UTC; the CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented
- Recheck: unchanged
Signups open, no new-user credit, API operational. No new status-page event since 29 Sep, 22:05 UTC; API 90-day uptime 99.826%. The CEO post is still online (its embed endpoint now redirects to
publish.x.com); no statement restoring credit on TypeSafe's homepage, blog, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented - Listed request limit raised from 40 to 80 per second
TypeSafe's models page raises the listed request limit for
jev-1.13.0from 40 to 80 requests per second; tokens per second are unchanged at 100K. The pool read 40 on 2 Oct, 05:14 UTC and first saw 80 on 3 Oct, 05:16 UTC. The Internet Archive has no capture of the page since 1 Oct and the docs changelog returns HTTP 404, so the exact time is unknown. The page says limits "can change without notice". A condition, not a change in who can sign up. DocumentedUpdate, 4 Oct 2026: the Internet Archive now has two captures of the models page from 3 Oct (06:49 and 07:23 UTC); both are later than the pool's first sight of 80, so they do not narrow the time. Update, 5 Oct 2026: three more captures from 4 Oct (02:01, 14:47 and 14:47 UTC) are also later; the docs changelog still returns HTTP 404. Update, 6 Oct 2026: the Internet Archive index could not be reached (connection error) and the docs changelog still returns HTTP 404. Update, 7 Oct 2026: the known captures (latest 4 Oct) still do not narrow the time, and the docs changelog still returns HTTP 404. Update, 8 Oct 2026: unchanged; the 4 Oct captures remain the latest known and the docs changelog still returns HTTP 404. Update, 10 Oct 2026 (no update was published on 9 Oct): unchanged; the models page was byte-identical at 05:12 and 05:16 UTC and the docs changelog still returns HTTP 404. This change was a home-page notice until 10 Oct, when its seven-day shelf life ended; the limits stay in the conditions above. Update, 11 Oct 2026: unchanged; the models page was byte-identical to the 10 Oct copy at 05:17 UTC and the docs changelog still returns HTTP 404. Update, 12 Oct 2026: unchanged; the models page was byte-identical to the 11 Oct copy at 05:12 UTC and the docs changelog still returns HTTP 404. Update, 13 Oct 2026: unchanged; the models page was byte-identical to the 12 Oct copy at 05:18 UTC and the docs changelog still returns HTTP 404. Update, 14 Oct 2026: unchanged; the models page was byte-identical to the 13 Oct copy at 16:46 UTC and the docs changelog still returns HTTP 404. Update, 16 Oct 2026: the models page no longer lists rate-limit numbers (see the 14 Oct entry on Jev 1.14 below).
- Recheck: access unchanged
Signups open, no new-user credit, API operational. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.826%, console 99.976%. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented
- Recheck: unchanged
Signups open, no new-user credit, API operational. Price ($0.042 per million input tokens) and listed limits (100K tokens and 80 requests per second) unchanged. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.826%, console 99.976%. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented
- Recheck: unchanged
Signups open, no new-user credit, API operational. Price ($0.042 per million input tokens) and listed limits (100K tokens and 80 requests per second) unchanged. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.829% (99.826% on 4 Oct), console 99.976%. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented
- Recheck: unchanged
Signups open, no new-user credit, API operational. Price ($0.042 per million input tokens), listed limits (100K tokens and 80 requests per second) and model aliases (
jev-latestandjev-previewpoint tojev-1.13.0) unchanged. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.826% (99.829% on 5 Oct; no new incident listed), console 99.976%. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented - Recheck: unchanged
Signups open, no new-user credit, API operational. Price ($0.042 per million input tokens), listed limits (100K tokens and 80 requests per second), model aliases (
jev-latestandjev-previewpoint tojev-1.13.0) and the model IDs on all six routes unchanged. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.828% (99.826% on 6 Oct; no new incident listed), console 99.976%. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented - Recheck: unchanged
Signups open, no new-user credit, API operational. Price ($0.042 per million input tokens), listed limits (100K tokens and 80 requests per second), model aliases (
jev-latestandjev-previewpoint tojev-1.13.0) and the model IDs on all six routes unchanged. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.831% (99.828% on 7 Oct; no new incident listed), console 99.976%. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented - Recheck: unchanged
Signups open, no new-user credit, API operational. No update was published on 9 Oct; the 9 Oct evidence notes recorded access unchanged. Price ($0.042 per million input tokens), listed limits (100K tokens and 80 requests per second), model aliases (
jev-latestandjev-previewpoint tojev-1.13.0) and the model IDs on all six routes unchanged. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.835% (99.831% on 8 Oct; no new incident listed), console 99.976%; the status page now also listsapi.us-west-2.typesafe.ai. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, new Enterprise page, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented - Recheck: unchanged
Signups open, no new-user credit, API operational. Price ($0.042 per million input tokens), listed limits (100K tokens and 80 requests per second), model aliases (
jev-latestandjev-previewpoint tojev-1.13.0) and the model IDs on all six routes unchanged. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.838% (99.835% on 10 Oct; no new incident listed), console 99.976%; the status page now also listsapi.us.typesafe.aiunder "API status by geography". The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, Enterprise page, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented - Recheck: unchanged
Signups open, no new-user credit, API operational. Price ($0.042 per million input tokens), listed limits (100K tokens and 80 requests per second), model aliases (
jev-latestandjev-previewpoint tojev-1.13.0) and the model IDs on all six routes unchanged. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.838% (unchanged from 11 Oct), console 99.976%;api.us.typesafe.aiandapi.us-west-2.typesafe.aistill listed. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, Enterprise page, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented - Recheck: unchanged
Signups open, no new-user credit, API operational. Price ($0.042 per million input tokens), listed limits (100K tokens and 80 requests per second), model aliases (
jev-latestandjev-previewpoint tojev-1.13.0) and the model IDs on all six routes unchanged. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.838% (unchanged from 12 Oct);api.us.typesafe.aiandapi.us-west-2.typesafe.aistill listed. TypeSafe's docs quickstart was rewritten with no access text. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, Enterprise page, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented - Recheck: unchanged
Signups open, no new-user credit, API operational. Price ($0.042 per million input tokens), listed limits (100K tokens and 80 requests per second) and model aliases (
jev-latestandjev-previewpoint tojev-1.13.0) and the model IDs on all six routes unchanged; TypeSafe's models page is byte-identical to 13 Oct. No new status-page event since 29 Sep, 22:05 UTC; 90-day uptime API 99.837% (99.838% on 13 Oct; no new incident listed); the status page now also listsapi.us-east-1.typesafe.aiandapi.us-east-2.typesafe.ai. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog, Enterprise page, docs quickstart, Hacker News or AI FrontPage. X search was not available. Documented - Jev 1.14 released as a preview; rate-limit numbers removed from the models page
TypeSafe's post "Jev: For the builders AND dreamers" releases
jev-1.14.0underjev-previewand says "jev-latest will be updated to jev-1.14.0 in a week. jev-1.13.0 will be available for a while." The models page now lists both versions at the same price and no longer gives rate-limit numbers ("Rate limits are set per organization"; until at least 14 Oct, 16:46 UTC it listed 100K tokens and 80 requests per second). Image input, a Box question type and long context are opt-in experiments. The pool first saw these changes on 16 Oct, 05:21 UTC; the docs changelog returns HTTP 404, so the exact time is unknown. A change in versions and conditions, not in who can sign up. TypeSafe blog. Documented - "Elevated Latency" on the us-east-1 API endpoint
api.us-east-1.typesafe.aiwas degraded for 45 minutes; "latency is back to normal" (status page). The mainapi.typesafe.aientry lists no event. Documented - Recheck: signups open, no new-user credit, API operational
Signup and credit unchanged; price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0). The console now shows a sign-in page (HTTP 200) instead of HTTP 403. 90-day uptime API 99.840% (99.837% on 14 Oct). The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (including the Jev 1.14 post), Enterprise page, docs quickstart, models page or AI FrontPage. X search was not available. Documented - Recheck: signups open, no new-user credit, API operational
Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0). Model aliases unchanged:jev-lateststill points tojev-1.13.0andjev-previewtojev-1.14.0; TypeSafe has published no date for the move. The models, Images, Box and quickstart pages are byte-identical to 16 Oct. No new status-page event; 90-day uptime API 99.826% (99.840% on 16 Oct). The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (no new post since 14 Oct), Enterprise page, docs quickstart, models page or AI FrontPage. X search was not available. Documented - Recheck: signups open, no new-user credit, API operational
Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0). Model aliases unchanged:jev-lateststill points tojev-1.13.0andjev-previewtojev-1.14.0; TypeSafe has published no date for the move. The models, Images, Box, legal and quickstart pages are unchanged since 16 Oct. No new status-page event; 90-day uptime API 99.826%, the same as on 18 Oct. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (no new post since 14 Oct), Enterprise page, docs quickstart, models page or AI FrontPage. X search was not available. Documented - Recheck: signups open, no new-user credit, API operational
Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0). Model aliases unchanged:jev-lateststill points tojev-1.13.0andjev-previewtojev-1.14.0; TypeSafe has published no date for the move. The quickstart, Box and legal pages are unchanged since 16 Oct; the models and Images pages differ only in links to a new errors page, after TypeSafe split its API reference into separate pages. No new status-page event; 90-day uptime API 99.826%, the same as on 18 and 19 Oct. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (no new post since 14 Oct), Enterprise page, docs quickstart, models page or AI FrontPage. X search was not available. Documented - Recheck: signups open, no new-user credit, API operational
Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0). Model aliases unchanged:jev-lateststill points tojev-1.13.0andjev-previewtojev-1.14.0, a week after TypeSafe's 14 Oct post said the move would come "in a week"; no date for it has been published. The models page and quickstart changed size since 20 Oct (the changed lines were not identified); their alias, price, limit and access text reads the same, and the Images page still says images are not ready for production. No new status-page event; 90-day uptime API 99.826%, the same as on 18, 19 and 20 Oct. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (no new post since 14 Oct), Enterprise page, docs quickstart, models page or AI FrontPage. X search was not available. Documented - Recheck: signups open, no new-user credit, API operational
Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0). Model aliases unchanged:jev-lateststill points tojev-1.13.0andjev-previewtojev-1.14.0, nine days after TypeSafe's 14 Oct post said the move would come "in a week"; no date for the move or for retiring 1.13 has been published. The models, Images and Box pages and the quickstart changed size since 21 Oct (the changed lines were not identified); their alias, price, limit, input and access text reads the same, and the Images page still says images are not ready for production. No new status-page event; the API uptime figure read as the 90-day window is 99.835% (99.826% on 18–21 Oct). The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (no new post since 14 Oct), Enterprise page, docs quickstart, models page or AI FrontPage. X search was not available. Documented jev-latestmoved to Jev 1.14 on TypeSafe's APITypeSafe's models page now lists
jev-latest→jev-1.14.0; the pool's read on 23 Oct, 05:45 UTC still showedjev-1.13.0, and it first saw the change on 24 Oct, 05:12 UTC.jev-previewalso points tojev-1.14.0("There is no preview build available right now").jev-1.13.0is still listed with its own ID and price, and no deprecation date is given. TypeSafe published no dated statement of the move (no new blog post; the docs changelog returns HTTP 404), so the exact time is unknown. A change in versions, not in who can sign up. Documented- Recheck: signups open, no new-user credit, API operational
Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0); rate-limit wording unchanged. Model aliases changed: on TypeSafe's APIjev-latestnow givesjev-1.14.0(entry above). The Images page changed only in its link form and still says images are not ready for production; the quickstart and Box pages changed size (the changed lines were not identified). No new status-page event; the API uptime figure read as the 90-day window is 99.831% (99.835% on 23 Oct). The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (no new post since 14 Oct), Enterprise page, docs quickstart, models page or AI FrontPage. X search was not available. Documented - No incident listed (from the status page's history)
The status page's own history, read on 30 Oct 2026, 05:14 UTC, listed no incident dated from 15 Oct up to that read; the newest event then was the us-east-1 latency event resolved on 14 Oct, 22:52 UTC. These days are covered by the status page's history, not by checks of ours. Documented
- Recheck: signups open, no new-user credit, API operational
The first check after 24 Oct, 05:12 UTC; there was no check between 24 and 30 Oct 2026. Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0); the per-organization rate-limit wording is unchanged. Model aliases unchanged since 24 Oct: on TypeSafe's APIjev-latestandjev-previewgivejev-1.14.0;jev-1.13.0is still listed with no deprecation date. The Images page is identical to the 24 Oct copy; the models page reworded two sentences, one of which now sends requests for higher limits to a form instead of the sales email (no price, limit, model ID or alias changed); the quickstart and Box pages changed size (not compared line by line). The API uptime figure read as the 90-day window is 99.832% (99.831% on 24 Oct). The CEO post is still online; no statement restoring credit, and no contrary signup or credit statement dated 24–30 Oct, on TypeSafe's homepage, blog (no new post since 14 Oct), Enterprise page, docs quickstart, models page, console sign-in pages or AI FrontPage. X search was not available. Documented - "System overload" on the us-east-1 API endpoint
TypeSafe's status page lists "System overload" on
api.us-east-1.typesafe.ai, "Degraded for 1 hour and 15 minutes, now operational", resolved on 30 Oct 2026 at 21:15 UTC ("System is back to normal"). The page text does not show when it started; from the stated duration it was about 20:00 UTC (an inference, not a stated time). It happened between the checks of 30 Oct, 05:14 UTC and 31 Oct, 05:11 UTC and was over before the 31 Oct check, so it is not a current notice. A service event, not a change in who can sign up. Documented - Recheck: signups open, no new-user credit, API operational
One day after the 30 Oct check. Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0); the per-organization rate-limit wording and the higher-limit request form are unchanged. Model aliases unchanged since 24 Oct: on TypeSafe's APIjev-latestandjev-previewgivejev-1.14.0;jev-1.13.0is still listed with no deprecation date. The models page is identical to the 30 Oct copy; the quickstart and Images pages changed only in formatting markup. One resolved status-page event since the 30 Oct check (entry above); the API uptime figure read as the 90-day window is unchanged at 99.832%. The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (no new post since 14 Oct), Enterprise page, docs quickstart, models page, console sign-in pages or AI FrontPage. X search was not available. Documented - No incident listed (from the status page's history)
There was no check between 31 Oct and 2 Nov 2026. The status page's own history, read on 2 Nov 2026, 10:47 UTC, lists no event dated 31 Oct, 1 Nov or 2 Nov; its newest entry is still the 30 Oct "System overload" above. Documented
- Recheck: signups open, no new-user credit, API operational
The first check after 31 Oct, 05:11 UTC. Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0); the per-organization rate-limit wording and the higher-limit request form are unchanged. Model aliases unchanged since 24 Oct: on TypeSafe's APIjev-latestandjev-previewgivejev-1.14.0;jev-1.13.0is still listed with no deprecation date. The models, quickstart and Images pages are identical to the 31 Oct copies. The API uptime figure read as the 90-day window is 99.880% (99.832% on 31 Oct). The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (no new post since 14 Oct), Enterprise page, docs quickstart, models page or AI FrontPage. The console sign-in pages returned an HTTP 403 block page and could not be read this time. X search was not available. Documented - No incident listed (from the status page's history)
There was no check between 2 Nov and 7 Nov 2026. The status page's own history, read on 7 Nov 2026, 15:29 UTC, lists no event dated 31 Oct to 7 Nov; its newest entry is still the 30 Oct "System overload" above. Documented
- Recheck: signups open, no new-user credit, API operational
The first check after 2 Nov, 10:47 UTC. Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0); the per-organization rate-limit wording and the higher-limit request form are unchanged. Model aliases unchanged since 24 Oct: on TypeSafe's APIjev-latestandjev-previewgivejev-1.14.0;jev-1.13.0is still listed with no deprecation date. Between the 2 Nov and 7 Nov reads the models page changed without a date (images listed as an input for both models; a Box question type that needs Jev 1.14; the "Language support" section removed), the quickstart now shows images and the Box primitive, and a docs changelog page appeared with one entry, Jev 1.14, dated 14 Oct 2026. The API uptime figure read as the 90-day window is 99.882% (99.880% on 2 Nov). The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (one new post, dated 3 Nov, about naming), Enterprise page, docs quickstart, models or changelog page, the console sign-in page or AI FrontPage. The console sign-in pages answered HTTP 200 again (a sign-in page; no waitlist text). X search was not available. Documented - No incident listed (from the status page's history)
There was no check between 7 Nov, 15:29 UTC and 8 Nov 2026, 05:17 UTC. The status page's own history, read on 8 Nov 2026, 05:17 UTC, lists no event dated after 30 Oct; its newest entry is still the 30 Oct "System overload" above. Documented
- Recheck: signups open, no new-user credit, API operational
The first check after 7 Nov, 15:29 UTC. Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0); the per-organization rate-limit wording and the higher-limit request form are unchanged. Model aliases unchanged since 24 Oct: on TypeSafe's APIjev-latestandjev-previewgivejev-1.14.0;jev-1.13.0is still listed with no deprecation date. The models, images, quickstart and changelog pages are identical to the 7 Nov copies; the docs index (llms.txt) added one cookbook page, "Verifying LLM answers against their source", with no access, price or model-ID content. The API uptime figure read as the 90-day window is 99.883% (99.882% on 7 Nov). The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (the same eight posts as on 7 Nov), Enterprise page, docs quickstart, models or changelog page, the console sign-in page or AI FrontPage. The console sign-in pages answered HTTP 200 (a sign-in page; no waitlist text). X search was not available. Documented - No incident listed (from the status page's history)
There was no check between 8 Nov, 05:18 UTC and 9 Nov 2026, 11:07 UTC. The status page's own history, read on 9 Nov 2026, 11:07 UTC, lists no event dated after 30 Oct; its newest entry is still the 30 Oct "System overload" above. Documented
- Recheck: signups open, no new-user credit, API operational
The first check after 8 Nov, 05:17 UTC. Signup, credit and price unchanged ($0.042 per million input tokens for
jev-1.14.0andjev-1.13.0); the per-organization rate-limit wording and the higher-limit request form are unchanged. Model aliases unchanged since 24 Oct: on TypeSafe's APIjev-latestandjev-previewgivejev-1.14.0;jev-1.13.0is still listed with no deprecation date. The models, images, quickstart, changelog and legal pages and the docs index (llms.txt) are identical to the 8 Nov copies. The API uptime figure read as the 90-day window is 99.882% (99.883% on 8 Nov). The CEO post is still online; no statement restoring credit on TypeSafe's homepage, blog (the same eight posts as on 8 Nov), Enterprise page, docs quickstart, models or changelog page, the console sign-in page or AI FrontPage. The console sign-in pages answered HTTP 200 (a sign-in page; no waitlist text). X search was not available. Documented
Post times are decoded from the X post IDs (offline arithmetic) and match the dates shown in the embeds. X posts were read through X's public embed endpoint without logging in on 28 Sep 2026, 19:41–19:50 UTC; the CEO post of 27 Sep was re-read the same way on 9 Nov 2026, 11:07 UTC. The status page, homepage and docs were rechecked on 9 Nov 2026, 11:07 UTC; the checks before were on 8 Nov 2026, 05:17 UTC, 7 Nov 2026, 15:29 UTC and 2 Nov 2026, 10:47 UTC (there was no check between 8 Nov, 05:18 UTC and 9 Nov, 11:07 UTC, nor between 7 Nov, 15:29 UTC and 8 Nov, 05:17 UTC, nor between 2 Nov and 7 Nov 2026, nor between 31 Oct and 2 Nov, nor between 24 and 30 Oct 2026); the newest status-page event is still the us-east-1 "System overload" resolved on 30 Oct, 21:15 UTC.
Is Jev down?
TypeSafe runs a status page at status.typesafe.ai; its website, docs quickstart, models page and llms.txt did not link it when checked on 30 Sep 2026, and the homepage still did not on 3 Oct. It covers api.typesafe.ai and console.typesafe.ai, and on 10 Oct also listed api.us-west-2.typesafe.ai ("TypeSafe API served from us-west-2"); on 11 Oct a new "API status by geography" section listed api.us.typesafe.ai ("TypeSafe API served from the closest US region"). On 11, 12 and 13 Oct the docs llms.txt, models page and quickstart named neither hostname; both entries were still listed on 13 Oct. On 14 Oct the status page also listed api.us-east-1.typesafe.ai ("TypeSafe API served from us-east-1") and api.us-east-2.typesafe.ai ("TypeSafe API served from us-east-2"), both at 100%; TypeSafe's docs still named only api.typesafe.ai. Documented
- API uptime
- 99.882% over the 90 days shown (9 Nov, read as before from the third of three figures the page shows without labelling their windows: 99.941%, 99.848% and 99.882%; 99.883% on 8 Nov; 99.882% on 7 Nov; 99.880% on 2 Nov; 99.832% on 30 and 31 Oct; 99.831% on 24 Oct; 99.835% on 23 Oct; 99.826% on 18, 19, 20 and 21 Oct; 99.840% on 16 Oct; 99.837% on 14 Oct; 99.838% on 11, 12 and 13 Oct; 99.835% on 10 Oct; 99.831% on 8 Oct; 99.828% on 7 Oct; 99.826% on 6 Oct; 99.829% on 5 Oct; 99.826% on 2, 3 and 4 Oct; 99.828% on 30 Sep and 1 Oct; 99.819% on 29 Sep). The figure is a rolling window: it moved on 6, 7, 8, 10, 11, 14, 18, 23, 24 and 30 Oct (no reading between 24 and 30 Oct) with no new incident listed on the main API entry, did not move between the 30 and 31 Oct readings, moved again by 2 Nov (no reading between 31 Oct and 2 Nov), by 7 Nov (no reading between 2 Nov and 7 Nov), by 8 Nov (no reading between 7 Nov, 15:29 UTC and 8 Nov, 05:17 UTC) and by 9 Nov (no reading between 8 Nov, 05:18 UTC and 9 Nov, 11:07 UTC), with no event listed in between. The us-west-2 API service showed 100% on 10 Oct, and the closest-US-region service 100% on 11 Oct; both showed 100% on 12, 13 and 14 Oct, and the new us-east-1 and us-east-2 services 100% on 14 Oct
- Console uptime
- 99.976% over the same period (12 Oct, unchanged)
- Status on 9 Nov, 11:07 UTC
- "All services are online" (last updated 11:06 UTC); no event listed after 30 Oct; last event "System overload" on the us-east-1 endpoint, degraded for 1 hour and 15 minutes, resolved 30 Oct, 21:15 UTC; the event before it, "Elevated Latency" on the same endpoint, 45 minutes, resolved 14 Oct, 22:52 UTC; last incident on the main API entry resolved 28 Sep, 16:07 UTC (as read on 30 Oct)
- Incidents
- September: API on 20, 21, 23, 24 and 28 Sep; console and maintenance on 29 Sep. October: elevated latency on the us-east-1 endpoint, 14 Oct; system overload on the us-east-1 endpoint, 30 Oct (resolved 21:15 UTC); none listed between them or after 30 Oct in the status page's history, read 30 and 31 Oct and 2, 7, 8 and 9 Nov (see timeline)
An aggregator reports that TypeSafe's incident post on X linked the status page (Reported). For gateway outages, check the gateway's own status page.
Pages that still show an old state (28 Sep)
| Site | What it still says | Current state |
|---|---|---|
| jev-ai.live | "grab $5 in free credit at console.typesafe.ai" | No free credit for new users since 27 Sep |
| jevaiplayground.com | "New signups paused" (page says checked 26 Sep) | Signups reopened 27 Sep |
| jevmodel.org | A 21 Sep "no waitlist" banner | Open, no credit |
| flaviocopes.com | "still paused as of September 24" | Signups reopened 27 Sep |
This lists outdated statements only; it is not a judgement of the sites. Resellers are covered on official vs reseller. An AI FrontPage article of 28 Sep dates Jev's launch to 21 Sep, which conflicts with TypeSafe's own 15 Sep launch post.
What was not verified
- The signup flow, whether a new account gets any credit today, account quotas and an actual bill: the console returned HTTP 403 until 14 Oct 2026, showed a sign-in page on 16, 18, 19, 20, 21, 23, 24, 30 and 31 Oct 2026, returned an HTTP 403 block page on 2 Nov 2026, and showed a sign-in page again on 7 Nov 2026, on 8 Nov 2026 and on 9 Nov 2026, 11:07 UTC (last checked); the pool does not create accounts.
- Newer posts by TypeSafe or its CEO on X: X search requires a login, so only the known posts could be re-read.
- A primary TypeSafe source for the "$5 / 120M tokens" amount.
- The rate limits that apply to a new organization: since 16 Oct TypeSafe shows them only in the developer console.
- The TypeSafe incident post that reportedly linked the status page (only an aggregator summary was seen).