API keys
PRYSM keys are prefixedprysm_sk_ (secret key). Create one at
prysm1.com.
The base URL
All API requests go to:/v1 version segment — point your OpenAI client at
it and the SDK appends paths like /chat/completions automatically.
Sending the key
Pass the key in theAuthorization header as a bearer token:
Environment variables
The SDKs and CLI resolve configuration from the environment, so you never have to hard-code credentials.| Variable | Used for | Default |
|---|---|---|
PRYSM_API_KEY | Your prysm_sk_* secret key. | — |
PRYSM_BASE_URL | API base URL (override for self-hosted). | https://api.prysm1.com/v1 |
For drop-in migrations, the Python and Node SDKs also fall back to
OPENAI_API_KEY
if PRYSM_API_KEY is not set — so pointing existing code at PRYSM can be a one-line
base-URL change.Which endpoints require a key
| Endpoint | Auth required |
|---|---|
POST /v1/chat/completions | Yes |
POST /v1/route | Yes |
GET /v1/usage | Yes |
GET /v1/models | No |
POST /v1/brain/validate | No |
GET /v1/proof/{request_id} | No |
GET /health | No |
Rate limits
Each key has a per-minute request limit tied to your plan. Exceeding it returns429 rate_limit_exceeded with a message describing your limit. Back off and retry, or
upgrade your plan for a higher ceiling.
Authentication errors
401 — invalid_api_key
401 — invalid_api_key
The key is missing, malformed, or revoked. Check the
Authorization header is
present and formatted as Bearer prysm_sk_....429 — rate_limit_exceeded
429 — rate_limit_exceeded
You’ve exceeded your per-minute request limit. Retry after the current minute, or
upgrade your plan.