Jev API keys
Official HTTP auth is:
Authorization: Bearer <API_KEY>The Python and JavaScript SDKs read TYPESAFE_API_KEY from the environment.
A missing or invalid key returns 401 Unauthorized.
Where keys come from
TypeSafe’s quick start: get the key from the dashboard after you have console access. We will not deep-link a settings path that might move; start at console.typesafe.ai.
On Vercel AI Gateway you use an AI Gateway credential (or OIDC), not a TypeSafe key, unless you point the official SDK at the Gateway base URL with that Gateway secret.
What jev.pro will not do
- Sell “Jev keys.”
- Embed a live key in examples. Use
$TYPESAFE_API_KEY. - Ask you to paste a key into this website.
Treat a key as a password. Rotate it if it leaked. This is ordinary secret hygiene, not a TypeSafe-specific protocol.
Sources
Public TypeSafe or adjacent documentation only. No private claims.