API Key Configuration

Create and edit keys in Dashboard > API Keys. Each key has a name, channel, Premium fallback preference, and optional expiry. Premium is the default; choose Cheap explicitly, with or without Premium fallback.

Creating keys

1. Open Dashboard > API Keys.
2. Click Create Key, enter a name, and choose Premium, Cheap, or Cheap + Premium fallback.
3. Set a future expiry if needed and copy the created key into your client.
4. Use Edit to change the name, channel, fallback preference, or expiry. Switching the catalog tab does not change the key.

Key format

All Claudexia keys follow this format:

sk_cdx_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

The sk_cdx_ prefix identifies the key as a Claudexia key.

Per-key controls

The dashboard key API accepts name, channel, fallback_premium, and expires_at. It does not configure per-key rate limits, budgets, model lists, IP filters, or IDE restrictions.

Channel modes

• Premium: channel=premium, fallback_premium=false. Omitting channel when creating a key selects Premium.
• Cheap: channel=cheap, fallback_premium=false. This key does not permit Premium fallback.
• Cheap + Premium fallback: channel=cheap, fallback_premium=true. The provider controls when fallback is used; a request served on Premium may cost more.

The auto_premium, auto_cheap and max modes, channel prices and channel errors are covered on the Premium and Cheap channels page.

Model availability

Check the catalog for the key's channel before choosing a model ID. A rejected channel or model returns an error; no retry schedule or extra capacity is guaranteed.

Expiry

expires_at must be in the future. Leave it unset when creating a key without an expiry. An existing expiry cannot be cleared through the current edit API.

Client configuration

Use the same key with the supported Anthropic or OpenAI authentication headers. Configure channel and fallback on the key, not in the inference request body.

Rotating keys

To rotate a key without downtime:

1. Create a new key with the same configuration.
2. Update your application to use the new key.
3. Verify the new key is working.
4. Delete the old key after checking the replacement.

Both keys will work simultaneously during the transition.

Deleting keys

Deleted keys stop working immediately and cannot be restored.

Deletion is permanent. Check that your clients use the replacement key before deleting the old one.