Team and Business put one monthly allowance behind every developer. No 5-hour limit, seats from $5, and extra usage when the pool runs low.
One pool for the whole team. A quiet seat leaves its allowance for whoever needs it.
$200/mo
A shared pool for teams of up to 10.
$200 base + 0 × $5 = $200
vs Claude Team Premium −68%
$500/mo
A larger pool, and no weekly cap either.
$500 base + 0 × $5 = $500
vs Claude Team Premium −60%
Custom
For teams past the seat limits, or with procurement and security review.
Custom seats and allowance, invoiced
Tell us the team size and monthly usage.
Prices in USD. Adding seats adds people and concurrency, not allowance. Extra usage is available on both tiers.
Plus passes lock each allowance to one person: the heavy user gets blocked while the light users’ allowance expires unused. A team pool lets everyone draw from the same allowance.
Used $520 · unused $480 · blocked $180
Used $700 · unused $100 · blocked $0
Example: in the same month, the five people want $380 / $180 / $80 / $40 / $20. Plus also has a 5-hour limit that would stop the heavy user even sooner; that is not counted here.
On most teams one or two people use most of the allowance. However evenly you split it per person, someone runs short and someone has allowance left over.
Long tasks and parallel agents are not cut off by a 5-hour window. Team keeps a weekly cap of $400; Business has none.
An owner or admin buys extra usage from the console. Each $1 buys 3× its value in extra usage, usable while the team subscription is active.
Used after the monthly allowance. It doesn’t expire and stays usable while the team subscription is active. It can carry you past the weekly cap.
Pay $100: $300 of extra usage.
| Feature | 5 × Plus | Team · 5 seats |
|---|---|---|
| Price a month | $150 | $200 |
| Allowance on paper | $1,000 | $800 |
| 5-hour limit per person | $33.33 | None |
| Unused allowance | Stays with the seat | Covers teammates |
5 Plus passes add up to more paper allowance, but a quiet seat cannot lend it out. Team trades that paper for one pool and no 5-hour limit.
One console for members, keys, usage, budgets and billing.
Invite by email. Every member gets a personal key you can rotate or revoke in one click.
Slice spend by person, model, agent and project. Export CSV or pull it from the usage API.
Set a monthly budget per member and see the shared pool fill up. At 80%, we alert you by email.
Choose which models the team can call and set a default.
One subscription for the team, monthly or annual. Seats and extra usage are billed with it; the owner and admins control both.
The owner manages billing and seats. Admins manage members, keys, budgets and extra usage. Members use their own keys.
We log metadata only: model, token counts, timestamps, latency, status, request ID and key. Prompts and code are never stored or used for training. DPA on request.Security & data
Same agents, same workflow. Only the key changes.
The owner or an admin invites by email. Members sign in and use the team allowance.
Usage follows the person, not a shared secret. Revoke one key without touching the rest.
Put the base URL and your key into the agent's config. For Claude Code that is two environment variables; the Keys page has the snippet for every tool.
export ANTHROPIC_BASE_URL="https://codingpass.ai" export ANTHROPIC_AUTH_TOKEN="cp-live-••••7f3a" $ claude --model claude-opus-5-5
Tell us your team size and rough usage. We reply by email with a proposal for seats, allowance and how you pay.
One shared allowance, no 5-hour limit, every agent, and extra usage when the pool runs low.
Team includes 5 seats, Business 10. Extra seats are $5 a month. Billing questions: [email protected].