# Workspaces and API keys

Source: https://platform.lyrouter.com/ai_gateway/docs/api-keys/en
Last updated: 2026-10-19

Create an API Key in the correct Account and workspace so that model access and usage attribution share the same scope.

## Workspaces

Personal accounts use the default workspace. Team and Enterprise Owners can create spaces; members need an existing grant. Confirm organization, department or direct sharing and roles before distributing credentials.

(Screenshot: Workspaces web page, showing workspace cards, Enter buttons and the New workspace button)

Team and Enterprise Owners select **New workspace**, enter its name and description, choose the sharing scope and role, then select **Save**. Enter the new workspace before creating an API Key.

(Screenshot: New workspace form with Specified departments selected, showing department selection, subdepartments, shared role and specific member settings)

## Create a Key

Open API Keys in the workspace. With creation permission, provide a name, optional expiry and supported budgets. Token budgets use millions of Tokens. Save the one-time plaintext credential before closing the creation dialog.

(Screenshot: API Keys web page, showing the workspace key list, enabled status and Create API Key button)

(Screenshot: API Key creation confirmation, showing the one-time key warning, Copy button and saved-key checkbox)

Model access is controlled by workspace services and lower-level policies, not a second independent model list on the Key.

## Manage and rotate

Management actions follow your actual permission. Enabled means usable, not recently used. Create a replacement Key, update the application and validate it before disabling the old Key.

Monthly and cumulative usage are separate; incomplete data is not zero. Shared Keys identify their creator rather than each operator. Run the [quick start](https://platform.lyrouter.com/ai_gateway/docs/quickstart/en) and check [request logs](https://platform.lyrouter.com/ai_gateway/docs/logs/en).