Member and system keys - AIHubMix

Enterprise workspaces offer two types of model API credentials. Choose the type based on who or what will use it.

Choose a key type

Type	Ownership and use	Who manages it
Member key	Belongs to an active workspace member; useful for individual development and member-attributed requests	The member manages their own keys; administrators manage them within organization permissions
System key	Belongs to the workspace; useful for persistent applications and services, with an optional maintenance contact	Organization administrators

A system key’s maintenance contact is not its owner. The key does not automatically stop when that contact leaves the organization.

Create and store a key

Confirm the organization and workspace, then open API keys.
Create a key, give it a recognizable name, and choose its type, limit, and expiration.
Configure model mapping, fallback, or other advanced options as needed.
Copy the full key after creation and store it in a secret manager or environment variable.

The full credential is shown only once, when created. The list shows a masked value afterward and cannot reveal the original key.

Limits and expiration

Key limits can be daily, weekly, monthly, or lifetime. An unlimited key still follows workspace hard limits and the account balance. See budgets and limits. An enterprise key’s expiration is read-only after creation. Create a replacement if you need a longer lifetime. An expired key cannot be re-enabled.

Replace or disable a key

Create a replacement with the required permissions and limits.
Update the applications using it and verify requests with the new key.
Disable or delete the old key.

Disabling temporarily stops use; deletion requires confirmation. Resolve member keys before their owner leaves, is suspended, or is removed. Historical requests retain their original attribution. Related: API key management · Model mapping and fallback · Members and permissions Last updated: 2026-10-13

⌘I