Organize teams under a shared billing account with separate API keys, budgets, and usage tracking.
A workspace is a shared account container for teams.
Available now in the dashboard. Go to Settings → Workspaces (/dashboard/settings/workspaces) to create workspaces, invite teammates by email, switch your active workspace, and (as owner) rename or delete one. Each workspace tracks its owner and members.
Scoping keys, budgets, and billing to the active workspace is in preview — today workspaces are an organizational + membership layer with a switcher. Every call debits the calling account's own wallet; switching workspaces never changes which wallet pays. The rest of this page describes that planned shared-billing behavior.
| Role | Capabilities |
|---|---|
| Owner | Billing, invites, all keys, budget config |
| Admin | All keys, budget config, no billing |
| Member | Own keys only, no billing |
Once available, workspaces are created from your dashboard. Every account starts as a personal workspace. You can convert it to a team workspace by inviting members.
Keys created inside a workspace inherit the workspace's DA balance and are subject to any budget caps the owner has set. A key cannot spend more than its assigned budget in the current period, regardless of the workspace's total balance.
The request format is identical whether the key belongs to a personal account or a workspace. The workspace context is resolved server-side from the key itself.
Every request is tagged with the key that made it. The workspace usage dashboard shows spend aggregated by key, model, and time. Owners and admins can export a CSV of all usage for a date range for accounting or chargeback purposes.
Each workspace can hold up to 20 API keys. Contact support if you need a higher limit.