How to set spending limits in Anthropic and Claude Code.

01Where Anthropic's spending limits live.

TakeawayFind out which way each team reaches Claude, because each way has its own limits page.

02Usage tier spend caps.

Every Claude API organisation sits on a usage tier, and each paid tier carries a monthly spend cap, the most the organisation can spend on the API in a calendar month.

At the tier cap, API usage pauses until 00:00 UTC on the first day of the next month. Requests return HTTP 429 with the error type rate_limit_error and the code enforced_spend_limit_reached. The response carries no retry-after header, so retries, including the SDK's automatic ones, keep failing until access resumes. To lift the cap sooner, use Request tier increase on the Rate limits page in the Console.

03How to set an organisation spend limit in the Claude Console.

1. In the Claude Console, go to the Billing page, at platform.claude.com/settings/billing.
2. In the Spend limits section, click Adjust limit, or Set limit if none is set yet.
3. Enter the new value. It cannot exceed your tier's cap.

When usage reaches a limit you set, requests return HTTP 400 with the error type invalid_request_error and a message that begins "You have reached your specified API usage limits" and says when access resumes. Raise or remove the limit to restore access sooner.

04How to set a workspace spend limit.

1. Go to the Workspaces page in the Claude Console, at platform.claude.com/settings/workspaces.
2. Select the workspace.
3. In the panel that opens, click Spend limits.
4. Under Monthly limit, click Change limit and enter the amount.
5. Under Email notification, click Add notification to get an email when the workspace's spend reaches an amount you choose.

A workspace limit can be lower than the organisation's and never higher. Left unset, it matches the organisation's limit, and the organisation limit always applies, even when the workspace limits add up to more. Only organisation admins can create workspaces, and the default workspace takes no spend limit at all, so move production keys into workspaces that can be capped. The message at a workspace limit reads "You have reached your specified workspace API usage limits".

TakeawaySet the organisation limit in Billing and a monthly limit on every workspace that runs production work.

05How to limit Claude Code costs.

Anthropic puts the average Claude Code cost across enterprise deployments at around $13 per developer per active day, or $150 to $250 per developer per month, with 90 percent of users below $30 per active day. How you cap it depends on how developers sign in.

With a Claude Console account.

The first time a member signs in to Claude Code with a Console account, Anthropic creates a Claude Code workspace and adds each member who signs in after them. Claude Code mints a key for each user there, and nobody can create keys in it by hand. Set a spend limit on this workspace, the same way as any other, to cap total Claude Code spend. Anthropic's workspaces documentation says it is the only workspace that supports per-user monthly spend limits. The Console's Claude Code dashboard shows spend for each member.

Admins can also cap Claude Code's share of the organisation's rate limits on the Rate limits page, which protects other production work. Leave the workspace in place: archiving it turns off Claude Code sign-in through Console billing for the whole organisation.

On Claude Team or Enterprise.

Each member's Claude Code use draws from their seat's allowance, shared with Claude chat and Cowork, which resets on a rolling five-hour window and a weekly window. The seat allowance is the default ceiling. To let members continue past it, turn on usage credits and set spend limits for the organisation, groups or members in the claude.ai admin settings. A developer who sees "You've hit your individual spend limit" or "org's monthly spend limit" has reached a limit an admin set, which an admin raises under Organization settings, then Usage. Members without billing access can run /usage-credits in Claude Code to send their admins a request.

On Amazon Bedrock, Google Cloud or Microsoft Foundry.

Claude Code is billed per token to your cloud account, and its spend controls live in your cloud provider's billing console. Anthropic's analytics do not see this usage. For spend by developer, Anthropic points to OpenTelemetry export, or to a self-hosted Claude apps gateway, which adds per-user spend limits on these clouds.

For a single scripted run.

In print mode, claude -p --max-budget-usd stops the run once its estimated spend reaches the amount you pass, counting subagents. The check uses Claude Code's own estimate, which can differ from the bill, and spend can pass the cap, so Anthropic advises leaving headroom.

TakeawayThe way a developer signs in decides where their Claude Code spend is capped, so check every sign-in method your teams use.

06How to set limits on Claude Team and Enterprise.

1. Sign in as an Owner or Primary Owner and go to Organization settings, then Usage.
2. Click Enable next to Usage credits. Team plans pre-purchase credits and can set auto-reload. Seat-based Enterprise plans are billed monthly for what was used.
3. Set the organisation-wide limit. In the Usage and spend limits section, click Adjust limit, enter an amount and click Set spend limit.
4. On seat-based Enterprise, set a limit for each seat tier. Under Spend limits, open the By group tab, click the menu beside Standard seats or Premium seats and choose Edit limit.
5. Set limits for individual members. In Spend limits by user, click the menu beside the member, choose Edit limit, enter an amount and click Set limit.

The organisation limit is the ceiling for total credit spend, whatever the seat and member limits say, and changes take effect immediately. On Enterprise, a member without a limit of their own inherits the limit of their group, their seat tier or the organisation, and a per-user limit set for them applies instead. A group limit is a default for each member, counted against that member's own spend. The MTD Spend column shows each member's spend so far this month.

When a member reaches their monthly limit, their credits pause until the end of the month. When the organisation or a seat tier passes its limit, Claude, Cowork and Claude Code stop until the next billing period or until the limits change. The limit is checked before each request and the cost counted after it, so one request can take spend slightly over.

On seat-based Enterprise, members who reach their included limit see a Request usage credits link. Owners, Primary Owners and custom roles whose Billing permission is set to Can manage review requests under Organization settings, then Usage, then Review requests, and click Increase limit to approve one. Admins get a daily email listing the requests still open. Claude Enterprise organisations can also set member limits and work the request queue through the Spend Limits API.

TakeawaySet the organisation limit first, then seat tiers and members, and decide who approves requests before the first one arrives.

07Where Anthropic's limits stop.

• Claude only. Spend on OpenAI, Google or a coding tool sits outside every Anthropic limit.
• Separate places to set them. Console limits, claude.ai admin limits and cloud budgets are set apart, and each developer is metered by whichever way they signed in.
• Workspaces, with agents inside them. Apart from per-user limits in the Claude Code workspace, API limits stop at the workspace, so agents sharing a workspace share its month.
• No request route on the API. Requests and approvals exist on Team and Enterprise. On the Console, an admin raises the limit, with no reason or expiry on record.
• A slightly late stop. A single request can take spend past a limit before the next one is blocked.

Our comparison of AI spending limits shows how Anthropic's controls sit beside OpenAI, Google, Azure, AWS, Cursor and GitHub Copilot, and how to set one budget above them all.

TakeawayUse Anthropic's limits as a backstop on every workspace and member, and keep the company's AI budget in one place above them.