Teams

30Teams

An organisation groups accounts so a team can see who spent what. Create one from the dashboard's Team pane, invite people by link, and the usage view shows 30 days of per-member spend, requests and tokens, read from the same rows billing uses. One organisation per account. Credits are per member by default, each person topping up and spending their own balance; the owner can switch the organisation to a shared balance from the Team pane, after which every member's requests spend from the owner's credits.

• Roles. The creator is the owner; everyone else is admin or member. Owner and admins invite and remove people and see everyone's spend; a plain member sees the roster but only their own numbers. Only the owner changes roles, and the owner cannot leave or be removed.
• Invites. An invite is a link, not an email: the token is shown once at creation, only its hash is stored, and it expires after 7 days or on first use. Joining while already in an organisation answers 409.

# Session-authenticated (dashboard login), not API-key:
POST   /v1/orgs                        { "name": "Acme" }
GET    /v1/orgs/mine                   # org, members + 30d spend, invites
POST   /v1/orgs/:id/invites            { "email": "...", "role": "member" }
DELETE /v1/orgs/:id/invites/:inviteId  # revoke an unused invite
POST   /v1/orgs/join                   { "token": "..." }
PATCH  /v1/orgs/:id/members/:userId    { "role": "admin" }   # owner only
DELETE /v1/orgs/:id/members/:userId    # remove someone, or yourself to leave
GET    /v1/orgs/:id/usage              # 30 days, per member