Skip to main content
PRYSM authenticates with a bearer API key over HTTPS. The same key works for the REST API, the SDKs, the CLI, and the MCP server.

API keys

PRYSM keys are prefixed prysm_sk_ (secret key). Create one at prysm1.com.
Your secret key grants full access to your account and is billable. Never commit it to source control, embed it in client-side code, or paste it into a browser. If a key leaks, rotate it from your dashboard immediately.

The base URL

All API requests go to:
This base URL already includes the /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 the Authorization header as a bearer token:

Environment variables

The SDKs and CLI resolve configuration from the environment, so you never have to hard-code credentials.
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

Verify your key

Confirm a key is valid and the API is reachable from the CLI:
Or with cURL:
A 200 response confirms the key is valid. A 401 means the key is missing, malformed, or revoked — check the Authorization header format.

Rate limits

Each key has a per-minute request limit tied to your plan. Exceeding it returns 429 rate_limit_exceeded with a message describing your limit. Back off and retry, or upgrade your plan for a higher ceiling.

Authentication errors

The key is missing, malformed, or revoked. Check the Authorization header is present and formatted as Bearer prysm_sk_....
You’ve exceeded your per-minute request limit. Retry after the current minute, or upgrade your plan.
Next: send your first request in the Quickstart, or browse the full API reference.