Accounts, organizations, and workspaces

Individual use rarely needs this page: the personal workspace created at sign-up is enough. Reach for organizations when you need team collaboration, per-department cost separation, or access control.

Roles and permissions are covered separately in roles and permissions.

Two kinds of account#

Account (personal | organization)
  ← balance, invoices, receipts, and negotiated discounts live here
        │
        ├── Personal account     exactly 1 workspace, fixed, no invitations
        └── Organization account multiple workspaces, members can be invited

Balance belongs to the account: one for the personal account, one for each organization. They are independent and cannot be transferred between each other, so decide the billing owner before adding credit.

Charges always follow one path:

API key → its workspace → that workspace's account → deducted from that account's balance

The personal workspace#

• Created automatically at sign-up. Each account has exactly one; it cannot be deleted, transferred, or duplicated
• Holds its own account, fully separate from any organization's
• Cannot invite others. Create an organization for collaboration
• Cannot be moved under an organization — usage history and ledgers are append-only, and moving would rewrite historical attribution

Organizations#

• Each user can create up to 5 organizations; organizations you are invited to do not count toward that limit
• Creating the next organization requires the current one to have been funded
• Each organization has an independent balance, separate from your personal account and from other organizations
• No nesting, and no sub-organizations. Internal hierarchy is expressed as multiple workspaces under one organization
• A default workspace is created automatically

Organization details include name, avatar, industry, size, and billing email, all editable in organization settings.

Closing an organization#

Only the organization owner can close an organization. On closing:

• Every workspace under it closes with it, and all API keys in them stop working immediately
• The balance must be zero; spend it down or request a refund first
• The action is not reversible
• Usage history and billing records are retained

Workspaces#

Workspaces express team, department, or project boundaries. An organization can hold up to 50 workspaces, all sharing that organization account's balance.

A workspace separates members, keys, usage, and logs — not balance.

Workspaces cannot move between organizations. Deletion is soft: call records and ledgers reference them, and a hard delete would leave data with no traceable owner.

Per-workspace rules#

An organization can set rules for a single workspace, from the organization console → workspaces → Set rules:

⚠️ Only organization admins can set these; workspace admins can only view them. That is the whole point of this layer — otherwise the team lead could simply lift the restriction.

Constraints intersect layer by layer, and lower layers cannot get around them. Once a workspace is limited to "value only", anyone creating a key in it stays within the value tier, even if they never touch the key's routing settings.

This differs fundamentally from narrowing key by key: any member can create a key, and a new key follows the layer above by default — relying on per-key configuration means one missed key defeats the whole restriction.

Workspace spend limits apply alongside member and key limits; whichever runs out first stops the call. Members can see the workspace cap and the current usage on the usage page.

Each workspace can also set its own playground default model (the model preselected for new conversations).

A personal workspace has no layer like this — only the account settings above it.

Invitations#

An invitee must accept using the email address the invitation was sent to. Users who have not signed up yet can also be invited; they join the corresponding organization and workspace automatically after registering.

⚠️ A workspace must be specified when inviting an ordinary member. Organization membership alone grants no workspace access, so without one the invitee lands in an empty console after accepting. Finance and admin invitations are exempt.

Invitations are valid for 7 days and must be resent after expiry. An organization can have at most 100 pending invitations at a time.

A member's spend limit for the target workspace can be set as part of the invitation.

Member spend limits#

Workspace admins can set spend caps per member, supporting a total cap plus daily, weekly, and monthly caps, all computed in UTC.

Member caps and key caps both apply, and the stricter one governs. Members can only tighten limits on their own keys; loosening requires a workspace admin.

Removing a member#

Once removed, the member immediately loses access to every workspace under that organization, and the API keys they created in it are disabled immediately.

Call records and billing are unaffected — they are append-only and are not rewritten when membership changes.

Common questions#

Can a personal workspace be upgraded to an organization#

No. A personal workspace cannot be transferred or moved under an organization. For team use, create a new organization and set up funding and workspaces there.

Can balance be transferred between organizations#

No. Each account's balance is independent; add credit to the target account instead.

I belong to several organizations — how do I switch#

Switch the current organization and workspace at the top of the console. Keys, usage, logs, and member lists all follow the current workspace.

What happens when a member leaves#

Remove them from the member list; the keys they created are disabled immediately. Those keys keep their original ownership record, and workspace admins can continue to view, restore, or delete them.

What if a workspace owner leaves#

The organization owner also holds workspace-level authority and can continue managing that workspace after its owner departs.

Related#

• Roles and permissions — what each role can do
• API keys — key ownership and visibility
• Billing overview — how charges are attributed to an account