Workspaces
A workspace is the unit of ownership on the platform. It owns:
- API keys — every key belongs to exactly one workspace.
- The wallet — usage from those keys is billed to that workspace.
- Usage history and invoices.
- Members and their roles.
Everything you do is in the context of one workspace. If you belong to several, the app has an active workspace, shown in the sidebar and switched from the workspace menu.
There is only one kind of workspace
Section titled “There is only one kind of workspace”There is no separate “personal” and “team” distinction. A workspace you created for yourself and one shared with twenty colleagues are the same object — the difference is only how many members it has. A workspace you use alone can be shared later without migrating anything.
Creating and switching
Section titled “Creating and switching”Create one from the workspace menu, or at Create workspace. The number of workspaces a single user may own is capped; if you hit the limit you can request an increase from within the app.
Switching workspaces changes everything workspace-scoped at once — usage, billing, members and keys. Note the URL does not contain the workspace, so a link you copy resolves against whichever workspace the recipient has active. When sharing a link with a colleague, say which workspace you mean.
Settings
Section titled “Settings”| Page | Purpose |
|---|---|
| Workspace | Name, business details, billing email, appearance |
| Team members | Members, roles and invitations |
| API keys | Create and revoke keys |
| Billing | Wallet, top-ups, payment method |
| Invoices | Invoice history and PDFs |
| Usage | Consumption and cost |
Which of these you can see depends on your role — see Team members and roles.
Choosing how many to use
Section titled “Choosing how many to use”One workspace per billing relationship is the usual answer, since the wallet and invoices are per-workspace.
Use separate workspaces when you need hard separation — distinct invoices, or a guarantee that one team’s spend cannot exhaust another’s balance. Use one workspace with separate API keys when you only need attribution, since usage can be broken down per key without splitting the wallet.