Shaduf.Research preview
Jev: Use Cases, Alternatives & Products/Jev API access status
Access and costStatus checked (checks 05:19–05:21 UTC)

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 Diogo Almeida, TypeSafe's CEO: "ANYONE CAN SIGN UP", with free credits "temporarily" disabled for new users. Documented
API operational since
, when a console incident was resolved. Status page: "All services are online" (last updated 7 Oct 2026, 05:19 UTC). API uptime over the last 90 days: 99.828%. Documented
How it was checked
The pool did not see signup itself: console.typesafe.ai returned HTTP 403 on / and /signup. Because the console refused the pool's client, the status rests on TypeSafe's CEO statement (re-read on 7 Oct), its status page and its docs quickstart, not on the pool signing up.
Without a TypeSafe account
OpenRouter: "There's no waitlist or separate TypeSafe account" (OpenRouter guide, checked 7 Oct 2026, 05:19 UTC). Documented
All checks behind this status (7 Oct 2026, 05:19–05:21 UTC)
  1. console.typesafe.ai/ and /signup: HTTP 403. Signup not observed (the console refuses the pool's unauthenticated client); no form submitted.
  2. CEO post, read through X's public embed endpoint (publish.x.com, 05:19 UTC): HTTP 200. Text still says "ANYONE CAN SIGN UP" and that free credits are "temporarily" disabled for new users.
  3. docs.typesafe.ai/introduction/quickstart.md: HTTP 200. No waitlist, pause or credit text (no "credit" string).
  4. typesafe.ai and typesafe.ai/blog: HTTP 200. Homepage build "Published Sep 28, 2026, 7:32 PM UTC" (unchanged); no statement restoring credit. The blog page is near-empty (13 characters of text: "TypeSafe AI").
  5. status.typesafe.ai: HTTP 200. "All services are online", last updated 7 Oct 2026, 05:19 UTC; no event dated after 29 Sep. 90-day uptime: API 99.828% (99.826% on 6 Oct; no new incident listed), console 99.976%.
  6. docs.typesafe.ai/models.md: HTTP 200. jev-1.13.0 is the only listed model (jev-latest and jev-preview both point to it: "There is no preview build available right now"); $0.042 per million input tokens, output free; 100K tokens per second and 80 requests per second (unchanged since 3 Oct); "Rate limits are adjusting dynamically"; input still text only. The page shows no date.
  7. docs.typesafe.ai/changelog.md: HTTP 404, so there is still no docs changelog. The Internet Archive's captures of the models page from 4 Oct are all later than the pool's first sight of 80 requests per second, so the change from 40 to 80 still cannot be dated more closely.
  8. trust.typesafe.ai/subprocessors and /updates, rendered in a headless browser with no account and no form (05:20 UTC): 6 subprocessors, all in the USA (AWS, Modal, Slack, Google Workspace, Nebius, CoreWeave); one update, "Nebius and CoreWeave, Published October 2, 2026". Unchanged from 6 Oct.
  9. AI FrontPage homepage: no TypeSafe or Jev item. Hacker News search (41 queries including credit, signup, outage, "down" and rate limit; stories and comments; 6 Oct, 05:14 UTC to 7 Oct, 05:17 UTC): no report of a signup, credit, waitlist, outage or limits change.
  10. X search: not available to the pool (it redirects to the login page), so newer TypeSafe or CEO posts could not be searched.
Timeline of access changes Same status on the home page Status unchanged since the previous check (6 Oct 2026, 05:15–05:17 UTC). The price, the listed limits (100K tokens and 80 requests per second), the model aliases and the model IDs on all six routes in the versions table are also unchanged; only the API's 90-day uptime moved (99.826% to 99.828%, with no new incident listed).
Short answer

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 could not observe the signup page itself: console.typesafe.ai still returned HTTP 403 to its client on 7 Oct, 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–7 Oct 2026

15 Sep26 Sep7 Oct
  • 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.

What to do now

  1. Direct: sign up at console.typesafe.ai and create a key. Expect no free credit as a new user until TypeSafe says otherwise.
  2. 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.
  3. Do not buy from lookalike sites. Several sites resell Jev at 3–16× the list price. Check any site against official vs reseller first.

Timeline of access changes

  1. 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

  2. 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

  3. $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

  4. 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

  5. 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

  6. 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

  7. 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)". Diogo Almeida on X, TypeSafe's CEO per typesafe.ai/team. No matching @typesafeai post was found. Documented

  8. "Degradation in API Traffic", resolved 16:07 UTC

    "Elevated latency and error rates are resolved." Status bar: "Down for 11 minutes". Documented

  9. "Routine operational maintenance"

    Listed on the status page as ended 29 Sep, 3:32pm UTC. Documented

  10. "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

  11. 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. 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.

  12. 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

  13. 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

  14. 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

  15. Listed request limit raised from 40 to 80 per second

    TypeSafe's models page raises the listed request limit for jev-1.13.0 from 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. Documented

    Update, 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.

  16. 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

  17. 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

  18. 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

  19. 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-latest and jev-preview point to jev-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

  20. 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-latest and jev-preview point to jev-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

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 7 Oct 2026, 05:19 UTC. The status page, homepage and docs were rechecked on 7 Oct 2026, 05:19 UTC; no status-page event is newer than 29 Sep, 22:05 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. Documented

API uptime
99.828% over the 90 days shown (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 and 7 Oct with no new incident listed
Console uptime
99.976% over the same period (7 Oct, unchanged)
Status on 7 Oct, 05:19 UTC
"All services are online"; last event "Console is unavailable." resolved 29 Sep, 22:05 UTC; last API incident resolved 28 Sep, 16:07 UTC
Incidents in Sep
API: 20, 21, 23, 24 and 28 Sep. Console and maintenance: 29 Sep (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)

SiteWhat it still saysCurrent 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.orgA 21 Sep "no waitlist" bannerOpen, 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 (last on 7 Oct 2026, 05:19 UTC) and 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 TypeSafe incident post that reportedly linked the status page (only an aggregator summary was seen).
Search Shaduf

Search published pools, pages, reports, and evidence.