Skip to main content
Provider credentials are upstream API keys that airmux uses after an inference request has been authenticated and routed. They are separate from inference keys and management keys.

Credential scopes

Add a credential

The webapp exposes credentials at instance, organization, and workspace settings. The CLI creates organization or workspace credentials:
Add --organization-wide to share the credential across the selected organization. Without it, the credential belongs to the selected workspace.
Values are never returned. Lists show metadata, the last four characters, current version, enabled state, and observed health.

Rotate, enable, disable, or delete

Selection and health

Within the selected scope, lower priority values are tried first. Credential status is advisory and reflects the latest ingested request event: unknown, live, invalid, or rate_limited. Request-time selection also uses an in-memory cooldown after a rate limit. Use a credential_access rule to allow only selected scopes.

Secret stores

The default managed deployment uses a file-backed store. Standalone mode uses environment variables and can resolve only one value per provider, making it appropriate for local or single-tenant use. Both planes must point at the same store when deployed separately.
Vaults support is coming.If you need a distributed vault for now, use insecure_database kind.