Skip to main content
Use this reference when you need to send authenticated requests or decide how to store and rotate keys. Phaseo Gateway uses bearer tokens. Every API request must include a valid key from your workspace.

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.
  • Rotated keys can be created at any time, then swapped into your app before the old key is removed.
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 July 26, 2026