Teams & enterprise

One account for your whole team’s Claude usage.

Give each person or project its own key, with its own quota, allowed models and IP allowlist. Every request shows what it cost and which key spent it.

A key per person

Create as many keys as you need under one account, named by member or project, or in bulk. When someone leaves or a project ends, disable that one key and nobody else is affected.

Limits on every key

Set a quota, an expiry date, allowed models and an IP allowlist for each key under “API Keys” in the console. When a key’s quota runs out it stops working instead of drawing on the rest of your balance.

Usage you can trace

Usage logs in the console record each request’s model, tokens and cost. Filter by key name to see what each person or project spent. Every entry is charged at our price and shows the list price and your discount, see Billing.

Someone who looks after your account

Every account has an account manager for top-ups and reconciliation.

Get started in three steps

  1. Create one account

    Have the person who owns the budget sign up and keep it. This account holds the balance and manages every key.

  2. Top up through your account manager

    Contact your account manager from the “Account manager” card on the dashboard and top up for the team. See How to top up.

  3. Hand out keys

    Create a key for each member or project under “API Keys”, set its quota and models, then share the setup steps. For a shared Claude Code setup, see the team chapter of the guide (in Chinese).