Skip to main content
Create a key in the dashboard, store it on your server, and send it as a bearer token with Gateway requests.

Key types

  • Gateway API keys call model, provider, and generation endpoints available to your workspace.
  • Management API keys call administration APIs. See Management API Keys.
Rotate a key by updating your application to use its replacement before invalidating the old credential. See the key rotation endpoint. Keys follow the format phaseo_v1_sk_<kid>_<secret>. Treat them like passwords and avoid storing them in client-side code or public repositories.
You can call :free models without depositing credits. Paid models require available wallet balance.

Header format

Include the key in the Authorization header on every request:
Most HTTP clients let you set this once on the client. For example, with fetch:

Key handling checklist


Common authentication errors

  • 401 Unauthorized: the key is missing, invalid, or belongs to a disabled workspace.
  • 403 Forbidden: the key exists but cannot access the requested provider or model.
  • 429 Too Many Requests: the key or workspace exceeded a limit. See Rate limits.
  • 5xx errors: retry with exponential backoff and contact support if the issue persists.
Last modified on September 6, 2026