Skip to main content
Corvex has two key types. Both are sent as HTTP Bearer tokens.

​
Virtual keys (sk-corvex-*)

Use a virtual key on inference endpoints: /v1/chat/completions, /v1/embeddings, /v1/models, etc. 
Authorization: Bearer sk-corvex-...
The current prefix is sk-corvex-. Legacy sk-bf-* keys minted before the cutover are still accepted during migration, so existing integrations keep working — but new keys are issued with the sk-corvex- prefix. A virtual key belongs to a team, has a name, can be revoked individually, and may be subject to per-key rate limits and an allowed_models list. Virtual keys are minted via the Governance API (or your team admin’s dashboard).
Using an admin key on /v1/chat/completions or /v1/embeddings returns HTTP 401 invalid_api_key. Inference endpoints require a virtual key.

​
Admin API keys (sk-admin-*)

Use an admin key on management endpoints under /api/*: releases, catalog mutations, account management. 
Authorization: Bearer sk-admin-...
Admin keys do not work on inference endpoints. Don’t ship admin keys to client devices.

​
Where to mint keys

Mint virtual keys from the Corvex dashboard — sign in at app.corvex.ai and create a workspace-scoped key from your workspace’s API-keys section. The key value (sk-corvex-...) is shown once — copy it immediately.
The dashboard mints keys through the BFF’s self-service flow. The gateway’s governance API (/api/governance/*) is an internal surface authenticated by the X-Internal-Secret header (BFF-only, RD-703 Path C) — end users do not call it directly. The legacy HTTP Basic governance auth was removed.

​
Rate limits

Rate limits apply per virtual key, per team, and per model. If you hit a limit you’ll receive HTTP 429. The dashboard surfaces current usage; the governance API exposes programmatic counters in a follow-up ticket.

​
Going further