Sharing Claude Code across a team: one key per person
As of 2026-11-05, a team can share one Claude Code API key on QCode, but everyone then draws on the same limit and concurrency (a personal-plan key allows 5 concurrent requests, 10 on Ultimate); to control quota and usage per person, use the Team Edition with one sub-key per member, each with its own quota. Anthropic's Claude Team is billed per seat, and its help center states that Claude Code is included with every Team plan seat. As of 2026-10-27, a team shares Claude Code on QCode with one key per person through the Team Edition (Codex is also available, set up per team after a quick review of your needs; contact sales): an admin creates a sub-API key for each member or group in a dedicated console, each key has its own quota and rate limit, and any key can be enabled or disabled at any time. The personal console manages one main key per plan and has no self-service sub-key screen. This page covers issuing keys, setting limits, checking usage, offboarding and getting the Team Edition set up, and compares it with Anthropic's Claude Team and Enterprise plans.
Updated 2026-11-07
Want to sell it yourself? Validate the full flow with one key first — white-label and reseller come after.
- Billed per token — live rates on /models
- Pay by card (Visa / Mastercard), Apple Pay, Google Pay or crypto
- Self-service: top up and activate instantly
Four numbers that matter
Keys: personal / Team Edition
The comparison table in the Team Edition Guide: the personal edition gets 1 key, while the Team Edition has no cap on sub-keys, each with its own quota.
Concurrency: personal key / Team Edition unit
Personal plans allow 5 concurrent requests per API key (10 on Ultimate), so, by implication, people sharing one key split that key's concurrency; the Team Edition page lists 35 concurrent requests per unit and recommends 3–5 people per unit.
Personal daily-limit reset (Beijing time)
On personal plans the daily cost limit resets at midnight Beijing time; once it is spent the API pauses and resumes automatically the next day. With a shared key, you can assume the whole team shares that one limit.
Anthropic Team plan size
Anthropic Help Center (updated 2026-10-16) and the pricing page: Team is for 2 to 150 seats; a Standard seat is $20 per seat per month billed annually or $25 billed monthly, a Premium seat $100 / $125. The Claude Code article updated 2026-10-27 says every Team seat includes Claude Code, and usage limits are per person and cannot be shared.
Why one key per person
As of 2026-10-27, a team can share one Claude Code key; if you want to control quota and usage per person, you may want one key per person. Three points in the docs bear on this: personal plans allow 5 concurrent requests per API key (10 on Ultimate) and have a single daily cost limit; the console's usage statistics cover the current active key; and the main API key (starting with cr_) can be reset in the console yourself: on the Key card, open the ⋯ menu next to the API Key line and reset the API key; the old key stops working within 1 minute, and quota, usage and expiry stay the same.
Each key can be reset at most once every 3 days, a small service fee applies per reset (the amount is shown in the console), and some keys still need online support or hi@qcode.cc. QCode's Team Edition page puts it this way: dedicated domains and sub-keys give each developer an independent quota, so usage and cost break down per person.
Where things stand on 2026-10-27
As of 2026-10-27, both QCode's dashboard guide and Team Edition Guide are marked as updated on 2026-10-22 (when last checked they showed 2026-10-01 and 2026-09-25). The dashboard guide states that the personal console manages one main key per plan and has no self-service sub-key screen; sub-keys belong to the team products, and a read-only qot_ token can query key expiry and daily usage programmatically.
The Team Edition Guide splits the admin's job into three steps: create a sub-API key for each team member or group, set a daily quota per key, and hand the keys out. Resellers have a separate Partner Dashboard that can issue sub-keys, with its own rsk_ access token.
Timeline
QCode's Team Edition Guide is marked as updated on this date; the current version says the admin creates a sub-API key for each member or group; every key has its own quota and rate limit and can be enabled or disabled at any time.
QCode's dashboard guide is marked as updated on this date; the current version describes: one main key per plan in the personal console and no self-service sub-key screen; a read-only qot_ token queries key expiry and daily usage programmatically.
This page is checked against the official pages: on Anthropic's pricing page Team covers 2 to 150 people, and Enterprise is US$20 per seat per month billed annually, with usage charged at API rates on top.
Confirmed vs not in the docs
Confirmed (verbatim in the official pages)
Everything below can be checked word for word in QCode's docs, on qcode.cc/enterprise and on Anthropic's pricing page: one main key per plan in the personal console with no self-service sub-key screen; the Team Edition is designed for development teams of 3 or more, with a dedicated e-xxx.qcode.cc domain and an /admin console; each sub-API key has its own quota and rate limit and can be enabled or disabled at any time, and the admin can set a daily quota per key; 5 concurrent requests per personal key, 35 per Team Edition unit; the qot_ token is read-only and shown only once; the main key can be reset in the console yourself (the old key stops within 1 minute, at most once every 3 days); Anthropic Team covers 2 to 150 people at $20 / $25 (Standard) and $100 / $125 (Premium), and Enterprise is US$20 per seat per month billed annually plus usage at API rates, with admins setting user and org spend limits.
Not in the docs, not inferred here
Four things are not in the primary sources, so don't plan around them
- 1whether Team Edition sub-keys can be queried with the read-only qot_ token, since the docs only describe the personal console's Open API
- 2whether a sub-key can carry a monthly cap on top of its daily quota, since the steps and examples in the docs only use daily quotas, and custom quota limits are raised as a special requirement when you enquire
- 3the exact Team Edition price, which this page leaves out: go by the Team Edition Cost Calculator on qcode.cc/enterprise and the quote you receive
- 4how fine-grained Anthropic's user and org spend controls are, since the pricing page only marks Team and Enterprise as having them.
One shared key, one key each, or Anthropic Team?
One shared key vs one sub-key per person
One shared personal key: the 5 concurrent requests and the daily cost limit belong to that one key; once the limit is spent the API pauses and resumes the next day, which you can expect to affect everyone sharing it at once. The console's usage statistics cover the current active key, so if you want usage per person, you can move to one key each.
The main key can be reset in the console yourself (at most once every 3 days, for a small fee), so you can replace it after someone leaves, but everyone sharing it has to switch to the new key. One sub-key per person (Team Edition): every key has its own quota and rate limit, the admin can set a daily quota per key, and the Team Edition page says usage and cost break down per person; when someone leaves, you can disable that one key in the console. The price is moving to the Team Edition, which is set up per unit, with 3–5 people per unit recommended.
Against Anthropic Team / Enterprise
Anthropic sells seats. As of 2026-10-27, Team is still 2 to 150 seats: a Standard seat is $20 per seat per month billed annually or $25 billed monthly, and a Premium seat with 5x the usage of Standard is $100 / $125. The prices are unchanged from the previous check. The pricing page still says Claude Code is included in all paid plans and shares the same usage limits as the rest of the plan; the Claude Code article updated 2026-10-27 adds that every Team seat includes Claude Code and that Premium seats simply offer more usage for heavier workloads.
The “What is the Team plan?” article updated 2026-10-16 says: “Usage limits can't be transferred or shared between team members. Each seat is for one named individual.” The credits article updated 2026-10-19 says Team plans also include monthly Claude API credits: $20 per Standard seat and $100 per Premium seat, pooled into one balance capped at $500; they are available after 7 days on the plan once an Owner or Primary Owner links a Claude Console organization, and they cannot be used for interactive Claude Code or extra usage in Claude, Claude Code or Claude Cowork.
Enterprise is US$20 per seat per month billed annually with usage at API rates on top, and admins set user and org spend limits. QCode bills per token, with per-model prices on /models. For the Claude Team plan itself, see /en/claude-team-plan-2026.
Five steps to give a team its keys
- 1Sign up: top up the amount the calculator shows in your QCode Dashboard, then email hi@qcode.cc to request the Team Edition with your team size and the number of units you need; setup takes about 1 hour during working hours, and the reply contains the admin console address and credentials.
- 2Issue keys: the admin logs in at
https://e-xxx.qcode.cc/adminand creates one sub-API key per team member or group. - 3Set limits: give each key a daily quota; sub-keys come with their own quota and rate limit.
- 4Member setup: export
ANTHROPIC_BASE_URL=https://e-xxx.qcode.cc/apiand setANTHROPIC_AUTH_TOKENto the cr_ sub-key the admin handed out; for Codex CLI the base_url ishttps://e-xxx.qcode.cc/openai(Codex is set up per team after a quick review of your needs, so confirm it with sales before setup). Only the API domain differs from the personal edition; everything else is configured the same way. - 5Offboarding: sub-keys can be enabled or disabled at any time, so when someone leaves, you can disable their key in the console. Keep team conventions in a
CLAUDE.mdat the project root and commit it to Git, but never commit API keys to the repository.
On QCode
QCode bills per token; per-model prices are on /models. Personal plans: one key starting with cr_ drives both Claude Code and Codex on the same plan quota. The console's usage statistics show the daily cost limit, a Monthly Usage Overview (Total Tokens / Total Requests / Total Cost, counted from the day the key was created), and today's input, output and cache tokens per model.
For programmatic checks, generate a read-only token starting with qot_ at /dashboard/openapi-token and call https://qcode.cc/api/v1/openapi/keys for key expiry and usage. qot_ is a personal token and is not interchangeable with the reseller rsk_ token. Teams of 3 or more that want a key per person use the Team Edition; the Team Edition page says Claude resources are covered by a mature standard flow and provisioned through the regular Team Edition, while Codex is also available and set up per team after a quick review of your needs (contact sales).
Want to try it for a few days first? Pay-as-you-go Packs start at $4 for a one-time quota you use within 7 days; if you already have a Personal Plan, buy a booster pack when you need more quota.
Frequently asked questions
Can a team share one Claude Code API key?
Yes, but a shared key means the whole team shares one limit and one concurrency allowance; to control quota and usage per person, use the Team Edition, where each person gets a sub-key with its own quota. Yes; if you want to control quota and usage per person, consider one sub-key per person. A personal key has 5 concurrent requests and one daily cost limit (reset at midnight Beijing time; once spent, the API pauses and resumes the next day), so you can assume everyone sharing it draws on the same allowance; the console's usage statistics cover the current active key; and when someone leaves and you want a new key, the main API key can be reset in the console yourself: the old key stops working within 1 minute, and quota, usage and expiry stay the same; each key can be reset at most once every 3 days, and some keys still need online support or hi@qcode.cc.
How do I give each member their own key?
Use the Team Edition. The admin logs in to the dedicated console at e-xxx.qcode.cc/admin, creates a sub-API key for each team member or group and hands them out; there is no cap on the number of sub-keys, and each has its own quota. The personal console manages one main key per plan and has no self-service sub-key screen.
Can I set a spend limit per key?
On the Team Edition, yes: the admin sets a daily quota for each key, and every key has its own quota and rate limit. Personal plans have a single daily cost limit tied to that one key; if you need other quota limits, you can raise them as a special requirement when you enquire about the Team Edition.
How do I see usage for each key?
On personal plans, use the console's usage statistics (daily cost limit, Monthly Usage Overview, today's tokens per model) or the Open API with a read-only qot_ token: one endpoint returns expiry and usage for all your active keys, the other an account-level usage summary. The token is shown only once and only a hash is stored. On the Team Edition, use the admin console, which the Team Edition page describes as real-time monitoring of the entire team's API usage, with usage and cost broken down per person. The /cost command in Claude Code is only an estimate; the Dashboard is what counts.
How do I take a key back when someone leaves?
With one sub-key per person, you can disable that person's key in the Team Edition console; sub-keys can be enabled or disabled at any time. With one shared personal key, the main API key (starting with cr_) can be reset in the console yourself: the old key stops working within 1 minute, and quota, usage and expiry stay the same; each key can be reset at most once every 3 days, and some keys still need online support or hi@qcode.cc. A qot_ token, by contrast, can be reset or revoked by yourself in the console, and the old token stops working immediately.
How do I get the Team Edition, and from what team size?
Top up first, then apply by email: add the amount the Team Edition Cost Calculator shows to your QCode Dashboard and email hi@qcode.cc with your team size and the number of units you need; setup takes about 1 hour during working hours. The edition is designed for development teams of 3 or more, is set up per unit with no minimum purchase requirement, and the page recommends 3–5 people per unit. For large contracts, you can contact QCode to sign a formal service agreement.
Sources
QCode's own features: the dashboard guide and Team Edition Guide on docs.qcode.cc (both marked updated 2026-10-22), the billing page and the FAQ, plus the Chinese and English versions of qcode.cc/enterprise (fetched again 2026-10-27); sub-keys, daily quotas, concurrency, usage statistics, the qot_ token and the signup flow all come from these pages. Anthropic: Help Center articles “What is the Team plan?” (updated 2026-10-16), “Use Claude Code with your Team or Enterprise plan” (updated 2026-10-27), “Purchase and manage seats on Team plans” (updated 2026-10-16) and “Monthly API credits for Max and Team plans” (updated 2026-10-19), plus claude.com/pricing/team (fetched 2026-10-27); seat prices, team size, Claude Code and monthly API credits all come from these pages.
Give every team member their own key
Teams of 3 or more use the Team Edition to issue one sub-key per person with a daily quota per key; billed per token, with per-model prices on /models.
Related reading
Buying an AI coding API for a team
Pooled versus daily-cap quota, concurrency and headcount per unit, and sub-key attribution.
enforced_spend_limit_reached: spend-cap 429
A 429 with no retry-after is the org monthly spend cap, not RPM throttling.
Share magpie with a team: gateway keys, LAN sharing and sync (2026-11)
magpie for a team or several computers: a gateway key per person with a limit and model list, Remote magpie from another computer, Docker, and backup, restore and sync.
Crypto payment guide
Nine coins, 56 networks, zero platform fee for AI coding API credits.
Checked on 2026-10-27. Anthropic's Team prices, seats, Claude Code and monthly API credits follow the Help Center articles updated 2026-10-16, 2026-10-27 and 2026-10-19; QCode features follow docs.qcode.cc and qcode.cc/enterprise, and Anthropic's plans and prices follow its official pricing page; both can change without notice. Team Edition pricing is whatever the calculator and your quote say. For model availability, go by /models.