Claude Code spend limits: what per-member caps can and cannot do
What the seat allowance, the usage credits switch, organization, group and per-member spend limits, the spend report and the Enterprise APIs each do for a Claude Team or Enterprise bill, where each one stops, and why no limit setting is the right one.
On Claude Team and Enterprise plans the bill is per seat, and so is the ceiling. On Team and seat-based Enterprise seats, each member’s Claude Code, Claude and Cowork usage draws from that seat’s own allowance3 . On the usage-based Enterprise seat nothing is included, and every token bills at API rates4 . If you own the bill, you have one switch, three kinds of monthly spend limit, a request queue, a dashboard with an export, and on Enterprise plans two APIs. We covered what changed and when in a separate explainer . This page is about the controls themselves: what each one does, the point at which each one stops helping, and the question none of them answers.
Which plan you are on
| Plan | What a seat includes | What governs consumption past it |
|---|---|---|
| Team, Standard or Premium seat | A session window and a weekly window of included usage, sized by seat tier and belonging to the member2 | Usage credits, off until an owner enables them, at standard API rates against monthly spend limits1 |
| Seat-based Enterprise, legacy Standard or Premium seat | The same per-seat windows3 | Usage credits billed at the end of each month1 . The plan moves to the usage-based seat at the next contract renewal5 |
| Usage-based Enterprise, the single seat | Access only, with “no per-seat usage limits and no included token allowance"4 | Every token at standard API rates, under organization, group and individual spend limits4 5 |
Individual Pro and Max plans are not covered here.
The controls, one at a time
The seat allowance
What it does. On Team and seat-based Enterprise seats the allowance is the default ceiling3 : a rolling five-hour window and a weekly window, shared across Claude, Claude Code and Cowork3 , sized by seat tier. A Standard seat carries 1.25 times the Pro plan’s usage per session and a Premium seat 6.25 times2 . Weekly limits reset at a fixed time each week that is assigned to the account, and a member receives the full weekly allowance each cycle2 . On the usage-based Enterprise seat there is no allowance to reach4 .
Where it stops. The allowance is the member’s own. Usage limits on Team plans are per member, not applied to the team as a whole2 . A member who reaches the weekly wall waits for the reset or, if usage credits are on, starts spending, while the unused remainder of the seat next to them resets with everyone else’s on its own schedule2 . Usage inside the allowance is not metered in dollars3 , so the spend report has nothing to say about who is close to the wall and who never approaches it.
The usage credits switch
What it does. This is the overage switch, and it is off by default. An Owner or Primary Owner turns it on in Organization settings under Usage and sets a monthly spend limit for the organization, or leaves it unlimited1 . Once it is on, members on Standard and Premium seats continue working past their included limits at standard API rates1 . Team organizations prepay the credits; seat-based Enterprise organizations are billed at the end of each month for what was used1 . It applies to Team and seat-based Enterprise plans. On the usage-based Enterprise seat there is nothing to switch on, because every token already bills4 .
Where it stops. It is one switch for the whole organization with one number behind it. Off means every seat is a hard weekly wall. On with no organization limit means an open invoice at API rates until a narrower limit says otherwise. On with an organization limit means that when the limit is reached, a member whose request would bill to credits is stopped until an administrator raises the limit the message names3 . The switch decides between an open invoice and a hard stop, and the limits below it decide where the stop lands.
Organization, seat-tier, group and per-member spend limits
What it does. Monthly dollar limits below the organization’s. On seat-based Enterprise plans a separate limit per seat tier1 . On Enterprise plans a per-user monthly limit assigned to each group6 . On every plan an individual monthly limit per member1 . They resolve in a fixed order: an individual limit overrides the group or seat-tier limit, which overrides the organization-wide default1 6 , and a member in more than one group gets the higher or the lower group limit depending on a setting6 . On the usage-based Enterprise seat the same organization and individual limits exist, can be set to unlimited, and consumption is billed either way5 .
Where it stops. Every one of them is a ceiling on one entity’s spend past its allowance. When a member exceeds theirs, they cannot use Claude, Cowork or Claude Code again until the next billing period, or until the limit is adjusted1 . A per-member limit changes when that member stops. It has no view of the allowance another member did not use, and it cannot hand a blocked member any of it. Set low enough to protect the budget, it blocks the members who were doing the most work. Set high enough not to, it protects nothing.
The request queue
What it does. A member who reaches a limit sees a link to request usage credits, or runs a command in Claude Code that sends the request to the organization’s administrators3 , and administrators receive a daily email listing the organization’s outstanding requests1 .
Where it stops. Each request is a decision for a person, once a day, about one member’s ceiling. The queue tells an administrator who is asking. It does not tell them who is holding allowance they will not use, and answering a request moves the invoice, not the allowance.
The analytics dashboard and the spend report
What it does. Settings, then Analytics, shows cost analytics: usage limits, spend concentration, total spend and spend by model7 . On Team plans Owners and Primary Owners can see it; on Enterprise plans Owners, Primary Owners and Admins can, though Admins cannot view spend7 . The spend report export lists each person’s use of each model with requests, prompt and completion tokens, and net and gross spend, summed over a window of up to 90 days7 . Spend data refreshes daily and has a one-day delay7 .
Where it stops. On Team and seat-based Enterprise plans the report covers usage-credit spend and appears once usage credits are turned on3 ; the export only reflects spend that exceeds the seat allotment7 . A dashboard shows. It does not act. Look at the concentration rather than the average, because the members who draw on credits set the invoice and the members who never approach their allowance set the waste, and the two groups are rarely the same people. If you would rather work from the export, the Claude spend report we publish reads it in your browser and draws that distribution, including who is at or over a per-member limit you type in. Nothing is uploaded, and it needs no token or account.
The Enterprise Analytics API and the Enterprise Admin API
What it does. On Enterprise plans a Primary Owner creates an Analytics API key with the read:analytics scope8 , and the Enterprise Analytics API returns per-user usage and cost reports across Claude surfaces, including Claude Code9 . The Enterprise Admin API, in public beta for Enterprise organizations with usage credits enabled, reads each member’s effective limit and period-to-date spend and sets or clears per-member overrides10 .
Where it stops. The Analytics API is not available on the Teams plan8 , and the Admin API serves Enterprise organizations with usage credits enabled10 ; on Team plans the per-user path is the export3 . On seat-based Enterprise plans the cost and usage endpoints reflect usage credits only9 . The Admin API writes one thing, a member’s override, while seat-tier, group and organization defaults are configured in claude.ai settings10 . So the programmatic control is the same ceiling, one member at a time.
The administrator’s dilemma
Every one of those controls is a ceiling. The dilemma is that no height is correct.
| You set | What happens |
|---|---|
| Usage credits off (the default), or per-member limits low | Every seat is a hard wall. A member who hits the weekly limit waits for a reset at a fixed time assigned to the account2 , and a member past a spend limit cannot use Claude, Cowork or Claude Code until the next billing period1 . One reported case: a Team Premium seat that read 100% of its weekly limit three days after it was provisioned15 . |
| Usage credits on, limits high or unlimited | Consumption past the allowance bills at standard API rates1 . On the usage-based Enterprise seat every token bills, and an unlimited setting is still billed5 . The vendor’s own averages across enterprise deployments are around $13 per developer per active day and $150 to 250 per developer per month, with costs below $30 per active day for 90% of users3 . The other 10% are the invoice. |
| Nothing | On Team and seat-based Enterprise seats, unused allowance resets on its own schedule2 while the seat next to it is at the wall. The vendor’s consumption guide tells administrators to review individual usage reports monthly for outliers of both kinds: members consistently hitting their cap and members consuming very little11 . |
The wall itself moved this week. On Team and seat-based Enterprise seats the weekly limit in Claude Code was 50% higher from May 13, 2026 through September 13, 202612 . From September 14 the standard is 25% higher than it was before that promotion, which the vendor describes as a 17% reduction compared with the promotional level13 14 . Whatever limit you set this month sits on an allowance smaller than last week’s.
Why no limit is the right height
Each control acts on one axis: how much one entity, whether the organization, a seat tier, a group or a member, is allowed to spend past its allowance. The problem the per-seat model creates lives on a different axis: who has headroom on Thursday.
Blocking and resetting unused are not opposite failures that a well-chosen limit sits between. They happen in the same organization, in the same week, to different seats. The members on agent workflows reach the wall while the allowance on the seats around them expires at the reset. Lowering a limit moves the blocked day earlier. Raising it moves the cost onto the invoice. Leaving usage credits off makes the wall everyone’s. None of those settings moves a single hour of allowance from a member who will not use it to one who will, because a limit cannot do that. It is a distribution problem being addressed with a ceiling.
Nor is this particular to Anthropic. Each vendor’s coding tool ships a ceiling of its own, and none of them ships the route.
The route the controls do not have
What a seat-based organization needs is the thing missing from the figure above: a way for allowance that would otherwise reset unused to reach the member who ran out, before the week ends. On a usage-based plan it is the same route in dollars: a per-member limit that follows demand within a budget rather than sitting where it was set. Then the limit can stay where it protects the budget, because a member who reaches it has somewhere to go.
We are building Spillway Ops for that route. The Claude Code connection is in development, as the product page says. On Enterprise plans it uses the paths the vendor documents: the Enterprise Analytics API for per-member usage and cost9 , and the Enterprise Admin API for per-member spend-limit overrides, in public beta for organizations with usage credits enabled10 . On Team plans the per-user path the vendor documents is the spend report export3 , so the route there runs through the export and a person until that changes. Either way it reads usage metadata and sets per-member limits through the vendor’s own admin API, with no repository access, no prompt contents and no code. Unused allocation flows to the members who need it, so spend falls without anyone losing a tool. If you are choosing a limit this month, we would like to hear which one and why.
Drop your email for early access notice and product updates in between.
Sources
- Claude Help Center Manage usage credits for Team and seat-based Enterprise plans
- Claude Help Center What is the Team plan?
- Claude Code Docs Manage costs effectively
- Claude Help Center What is the Enterprise plan?
- Claude Help Center How am I billed for my Enterprise plan?
- Claude Help Center Manage groups and group spend limits on Enterprise plans
- Claude Help Center View usage analytics for Team and Enterprise plans
- Claude Code Docs Track team usage with analytics
- Claude Platform Docs Analytics APIs
- Claude Help Center Claude Enterprise Admin API reference guide
- Claude Help Center Claude Enterprise consumption guide
- Claude Help Center Claude Code May–August 2026 weekly limits promotion
- Claude Developers on X Compared to today, this works out to a 17% reduction in weekly limits on Claude Code
- BleepingComputer Anthropic is cutting Claude Code’s current weekly limits by 17%
- GitHub, anthropics/claude-code Team Premium seat weekly limit stuck at 100% after only 102M tokens (issue 41001)
Last updated September 13, 2026.