Troubleshooting access to Jev resources
Access troubleshooting for Jev is a short tree: credential, request shape, then capacity. Official HTTP failures TypeSafe documents are 401, 422, 429, and 529. This site cannot reset your console, raise quotas, or see your traffic. Jev is TypeSafe’s System One decision model; a failed call is usually your door or body, not a missing “access microservice.”
This page is for builders who already heard of Jev / System One and are stuck before a 200. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. We do not sell, issue, or proxy API keys. Confirm status codes on docs.typesafe.ai. Keys come only from the TypeSafe dashboard after access, at console.typesafe.ai.
Steps
- Classify the status before you edit questions. 401 is unauthorized: check
Authorization: BearerandTYPESAFE_API_KEY. Do not retry 401. Rotate the secret in the console or gateway if it leaked — see API keys. - If the status is 422, read the field error. Fix
model,state, or the question shape. Sendingjev-1.13(no.0) when the models page listsjev-1.13.0is a common first-party miss. - If the status is 429 or 529, back off. Official SDKs honor
retry-afterwhen present. Raw HTTP must implement exponential backoff itself. Details: errors and retries and rate limits. - Confirm you did not mix doors. A TypeSafe key against a Vercel AI Gateway base URL will fail in confusing ways. Gateway auth is a Gateway credential or OIDC; the model id is
typesafe-ai/jev, not a first-party alias. - If
GET /v1/modelslooks empty, treat it as auth first. The list currently shows aliases; versioned ids may still work on POST. - If the HTTP status is 200 but the answer looks like “I don’t know,” stop treating it as access. A flat distribution or Noul near 0.5 is an uncertain decision, not a missing key.
Pitfalls
- Tight-looping 401s. That burns nothing useful and can hide a copied
.env. - Treating SDK timeouts as TypeSafe outages. Your deadline is yours; fail closed on irreversible acts.
- Pasting the full response body into a public ticket. Redact keys and customer
statefirst. - Asking this site to look up waitlist status. We cannot. Ask TypeSafe.
- Quoting 250k tok/s, 1200 RPM, or $0.042/M input (output free) as if we measured them. Those are vendor claims and can change.
Symptom classes you will actually see
| You see | Class | Fix |
|---|---|---|
| 401 | Unauthorized | Check Bearer / TYPESAFE_API_KEY. Do not retry. |
| 422 | Validation | Read the field error; fix model, state, or question shape. |
| 429 / 529 | Limit / overload | Exponential backoff; honor retry-after. |
| SDK timeout | Your deadline | Fail closed on irreversible acts. |
| Gateway 4xx | That door | Confirm typesafe-ai/jev and Gateway auth. |
Marketplace 402 or customer-verification codes belong to that vendor, not to TypeSafe’s documented set. Do not invent a TypeSafe meaning for them. The Playground is useful to prove the same body works under a console login before you debug CI.
See also
FAQ
Can you look up my waitlist status?
No. Ask TypeSafe. This site does not see accounts.
Empty GET /v1/models?
Usually auth. The list currently shows aliases; versioned ids may still work on POST.
Should I paste the response body into a public ticket?
Redact keys and customer state first. A leaked bearer token is a rotate-now event.
Does a Noul of 0.5 mean I am blocked?
No. That is a 200 with an uncertain answer. Access errors are 401/422/429/529 as TypeSafe documents them.
What this page does not claim
This page does not claim we can reset consoles, raise RPM, or decode a third-party 402. It does not freeze vendor limits. It does not treat uncertain answers as outages.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai.