Teams and roles
One balance, one bill, everyone in. A team shares its credits, API keys, usage, logs and API requests, and each member gets a role that decides what they can touch. Every account starts with a personal team; create more from the team switcher in the dashboard.
Roles
Five roles, checked on every request on our side (the dashboard hides what your role can't do, but the server is what says no).
| role | can |
|---|---|
| Owner | Everything, including transferring ownership and deleting the team. Each team has exactly one owner. |
| Admin | Members and invites, team settings, every member's keys, spend limits, billing view. Can't buy credits or change the plan, and can't promote anyone to owner. |
| Developer | Create and revoke their own keys, use the playground, request and follow new APIs, read usage and logs. |
| Billing | Top-ups, plans, auto top-up, invoices, billing details and spend limits. No keys. |
| Viewer | Read-only: overview, usage, logs and requests. |
Calls with a key run as the team, whoever created the key. A role only limits what a member can do in the dashboard.
Invites
- Who: owners and admins invite by email from Team → members and pick the role up front.
- How long: an invite link works for 7 days and only once. Resend it for a fresh link, or revoke it any time.
- Email must match: the person accepting must be signed in with the address you invited. A forwarded link won't let anyone else in.
- Limits: up to 20 invites a day per team. Pending invites count toward the member limit.
Teams on a paid plan can also let colleagues join on their own from a verified domain.
Switching teams
Belong to several teams? The switcher at the top of the dashboard moves you between them. Everything you see (balance, keys, logs, billing) follows the team you're in. Remote MCP sign-ins ask which team to use on the consent screen.
Member limits
| plan | members |
|---|---|
| Free | The owner plus one (2 in total) |
| Paid (any monthly plan or a past top-up) | Up to 100 |
| Enterprise | Set in your contract |
Downgrade with more members than the limit and nobody is removed: everyone stays, but new invites, accepted invites and domain joins answer 402 member_limit until you're back under it.
Transferring ownership
The owner can hand the team to any member from Team → members, confirming with their password (and a two-factor code if they use one). The new owner gets full control; the old owner stays on as an admin. Both get an email.
Leaving and removing members
- Anyone but the owner can leave a team. The owner transfers ownership first.
- Owners and admins can remove members. The member's dashboard sessions in that team end at once and they land in their personal team.
- Their keys keep working. Keys belong to the team, so production doesn't break when someone leaves. On the Keys page they're marked left so you can review them and revoke or rotate what you no longer trust.
Deleting a team
Only the owner can delete a team, and never their personal team. Type the team's name and your password to confirm. Two guard rails first:
- A plan that still renews must be canceled first.
- Purchased credits left on the team must be explicitly given up.
Deleting revokes every key and pending invite, removes all members (each gets an email), and drops the team's verified domains and sign-in connections. Orders, invoices and the activity log are kept for your records. The team's call history is de-identified straight away and deleted after 180 days.
Activity log
Who did what, and when. Team → activity lists invites, joins, role changes, transfers, key creation and revocation, billing and settings changes, with the member who did it. Owners and admins can read it. Enterprise teams can also export it or stream it to a webhook.
Billing contact
Want invoices to land in finance's inbox instead of yours? Set a billing contact email in Billing: invoices, receipts, plan emails and low-balance alerts go there too. Owners and billing members can set it. More in Billing and credits.
Next
- API keys: expiry, monthly caps and allowed endpoints per key.
- Account security: two-factor login, required 2FA and verified domains.
- Enterprise: single sign-on, SCIM and network allow-lists.