Sharing Claude Code across a team: one key per person
As of 2026-10-07, the way to give each team member their own Claude Code key on QCode is the Enterprise Team Edition (for Codex, the enterprise edition requires contacting QCode separately): 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 enterprise edition set up, and compares it with Anthropic's own Team and Enterprise plans.
Updated 2026-10-07
Four numbers that matter
Keys: personal / enterprise
The comparison table in the enterprise guide: the personal edition gets 1 key, while the Enterprise Team Edition has no cap on sub-keys, each with its own quota.
Concurrency: personal key / enterprise account
Personal plans allow 5 concurrent requests per API key, so, by implication, people sharing one key split those 5; the enterprise page lists 35 concurrent per account and recommends 3 users per account.
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's pricing page: Team is for teams of 2 to 150; a Standard seat is $20 per seat per month billed annually or $25 billed monthly, a Premium seat $100 / $125.
Why one key per person
As of 2026-10-07, 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 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_) currently has no self-service reset, so you contact online support or email hi@qcode.cc. QCode's enterprise 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-07
QCode's dashboard guide (marked updated 2026-10-01) 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. The team card on the subscribe page reads "Flexible quota & sub-key mgmt" and points to hi@qcode.cc. The enterprise team guide (updated 2026-09-25) 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 enterprise team 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 Enterprise 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 enterprise account; the qot_ token is read-only and shown only once; the main key has no self-service reset; 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: ① whether enterprise sub-keys can be queried with the read-only qot_ token, since the docs only describe the personal console's Open API; ② whether 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; ③ the exact enterprise price, which this page leaves out: go by the Team Plan Calculator on qcode.cc/enterprise and the quote you receive; ④ how 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 has no self-service reset, so replacing it after someone leaves goes through support. One sub-key per person (Enterprise Team Edition): every key has its own quota and rate limit, the admin can set a daily quota per key, and the enterprise 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 enterprise edition, which is set up per account with 3 users per account recommended.
Against Anthropic Team / Enterprise
Anthropic sells seats. Team is for 2 to 150 people: a Standard seat is $20 per seat per month billed annually or $25 billed monthly, and a Premium seat, with 5x the usage of a Standard seat, is $100 / $125. The pricing page says Claude Code is included in all paid plans and shares the same usage limits as the rest of the plan. 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.
Five steps to give a team its keys
① Sign up: top up the amount the calculator shows in your QCode Dashboard, then email hi@qcode.cc to request the Enterprise Team Edition with your team size and the number of accounts you need; setup takes about 1 hour during working hours, and the reply contains the admin console address and credentials. ② Issue keys: the admin logs in at https://e-xxx.qcode.cc/admin and creates one sub-API key per team member or group. ③ Set limits: give each key a daily quota; sub-keys come with their own quota and rate limit. ④ Member setup: export ANTHROPIC_BASE_URL=https://e-xxx.qcode.cc/api and set ANTHROPIC_AUTH_TOKEN to the cr_ sub-key the admin handed out; for Codex CLI the base_url is https://e-xxx.qcode.cc/openai (for Codex, the enterprise edition requires contacting QCode separately, so confirm this before setup). Only the API domain differs from the personal edition; everything else is configured the same way. ⑤ Offboarding: 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.md at 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 Enterprise Team Edition; the enterprise page says its standard delivery is primarily for Anthropic Claude resources, while Codex is also supported but has to be arranged with QCode separately, case by case.
Frequently asked questions
Can a team share one Claude Code key?
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 currently has no self-service reset, so you contact online support or email hi@qcode.cc.
How do I give each member their own key?
Use the Enterprise 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 enterprise 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 enterprise 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 enterprise edition, use the admin console, which the enterprise 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 enterprise console; sub-keys can be enabled or disabled at any time. With one shared personal key it is harder: the main API key (starting with cr_) currently has no self-service reset, so you contact online support or email 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 Enterprise Team Edition, and from what team size?
Top up first, then apply by email: add the amount the Team Plan Calculator shows to your QCode Dashboard and email hi@qcode.cc with your team size and the number of accounts 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 account with no minimum purchase requirement, and the page recommends 3 users per account. For large contracts, you can contact QCode to sign a formal service agreement.
Sources
QCode's own features: the dashboard guide, the enterprise team guide, the billing page and the FAQ on docs.qcode.cc, plus the Chinese and English versions of qcode.cc/enterprise (all crawled 2026-10-07); sub-keys, daily quotas, concurrency, usage statistics, the qot_ token and the signup flow all come from these pages. Anthropic Team and Enterprise seat prices, team size, spend controls and the Claude Code usage note: Anthropic's official pricing page (anthropic.com/pricing redirects to claude.com/pricing, crawled 2026-10-07).
Give every team member their own key
Teams of 3 or more use the Enterprise 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, per-account concurrency and headcount, 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.
API Key Usage Query API
Programmatically query API key expiry and usage with a read-only token.
Checked on 2026-10-07. 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. Enterprise pricing is whatever the calculator and your quote say. For model availability, go by /models.