Workspaces
Organize API keys and usage into named containers within one account.
A workspace is a named container that groups API keys and usage inside a single account, similar to a project or an environment. Every account starts with a Default Workspace, and keyless activity rolls up to it. An account can hold up to 10 workspaces.
Workspaces are managed with a session from the dashboard.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
GET | /v1/workspaces | List workspaces |
POST | /v1/workspaces | Create a workspace |
PATCH | /v1/workspaces/:id | Rename or edit a workspace |
DELETE | /v1/workspaces/:id | Delete a workspace and revoke its keys |
A workspace looks like:
{
"id": "ws_...",
"name": "Production",
"slug": "production",
"description": "Live traffic keys",
"is_default": false,
"created_at": "2026-07-30T12:00:00.000Z"
}Slugs are lowercase alphanumeric with hyphens and must be unique within the account. The Default Workspace cannot be deleted.
Scoping keys and usage
- Create an inference key inside a workspace by passing
workspace_idwhen you create it. See authentication. - Filter usage to one workspace with
GET /v1/usage?workspace_id=<id>.
Deleting a workspace revokes the API keys that belong to it, so move or recreate any keys you still need first.