Claude Max API credits vs usage credits for Claude Code
Max, Ultra and Team include monthly Claude Platform credits, but they do not pay for interactive Claude Code. Usage credits do. Here is what each covers.
The monthly API credits that come with Max, Ultra and Team do not pay for interactive Claude Code. They are Claude Platform credits for the Claude API, the Agent SDK and similar developer work, and they do not change your plan's usage limits. Usage credits are a separate pay-as-you-go balance that lets you keep using Claude and Claude Code after you hit a plan limit. If you want to keep working past a limit in the terminal, you need usage credits.
The short version
| Monthly API credits | Usage credits | |
|---|---|---|
| What they are | Claude Platform credits included with the plan | A pay-as-you-go balance you buy |
| Who gets them | Max, Ultra, Team, once claimed | Pro, Max, Ultra; on Team, set up by the owners |
| Pay for interactive Claude Code | No | Yes, past plan limits |
| Pay for the Claude API and Agent SDK | Yes, with a key from the linked organization | No |
| Where the balance lives | The Console organization you link | Settings > Usage on claude.ai |
| Expiry | Unused credits expire at the end of each billing cycle | Purchases from December 7, 2026 generally expire after 12 months |
The table summarises two Anthropic pages: monthly API credits and managing usage credits. Details below are as of November 2026.
Monthly API credits
Anthropic added these for Max and Team on October 7, 2026 (release notes), and the help article now covers Max, Ultra and Team. The amounts, per month:
- Max: $100
- Ultra: $200
- Team: $20 per Standard seat and $100 per Premium seat, pooled into one balance capped at $500 per team
Free, Pro and Enterprise plans are not eligible.
Claiming them
Nothing lands anywhere until you claim it. You link one Claude Console organization: in Settings > Billing as the Max or Ultra subscriber, or in Organization settings > Billing as a Team Owner or Primary Owner. You also need the Owner, Admin or Billing role in that Console organization, and new subscribers can claim after seven days on an eligible plan. You can link only one organization, and you cannot change it yourself afterwards.
What they cover
The Claude API (the Messages and Message Batches APIs), the Playground in the Claude Console, Claude Managed Agents and the Claude Agent SDK. For claude -p, they apply only when you run it with an API key from the linked Console organization.
What they do not cover
The same page says the credits do not apply to "Interactive Claude Code in the terminal, IDE, desktop, or web", "Extra usage in Claude, Claude Code, or Claude Cowork" (extra usage is the old name for usage credits), or Claude on Amazon Bedrock, Google Cloud Vertex AI or Microsoft Foundry. They are also "Separate from your plan limits": they "don't change your usage limits in Claude, Claude Code, or Claude Cowork."
This is the most common mix-up, so it is worth saying directly: a Max plan with $100 of monthly API credits does not mean $100 of Claude Code on top of your limits.
How they behave
- They refresh each billing cycle, monthly even on annual plans, and do not roll over.
- They are spent before any credits the organization bought.
- Everyone with an API key in the linked organization draws from the same balance.
- When they run out and the organization has no other credits, "API requests stop until your next monthly credits arrive." Usage is never charged to your Claude plan.
Usage credits
Usage credits let Pro, Max and Ultra subscribers keep using Claude after reaching any five-hour, weekly or Fable limit. They bill at standard API rates, separately from your subscription. You enable them in Settings > Usage, set a monthly spend limit, buy credits and optionally turn on auto-reload; in Claude Code, /usage-credits takes you there. On Team, owners enable them for the organization. Usage credits "don't affect the reset timing" of your limits. The setup, the "Now using credits" switch and the expiry rules are in usage credits on Claude plans.
Which one applies
- An interactive session in the terminal, IDE or desktop app at a limit: usage credits, or wait, or upgrade. The monthly API credits are never used here.
- A program that calls the Claude API directly, or the Agent SDK, with an API key from the linked organization: the monthly API credits.
claude -por the Agent SDK signed in with your plan and no key: these "still draw from your plan's usage limits and don't use your API credits."claude -pwith an API key from the linked organization: the monthly API credits can cover it.- Runs started by the Claude Code GitHub Action, an IDE extension or the Claude desktop app: these count as Claude Code usage, so the API credits do not cover them, "even with -p".
Cases 3 and 4 are the ones to watch, because the same command bills very differently depending on the credential. When an API key is set in your environment, Claude Code uses it in -p mode: "the key is always used when present" (authentication docs). If that key belongs to a Console organization you did not link, it bills that organization's own credits as ordinary API usage. See why Claude Code bills your API key instead of your plan and what claude -p does to subscription limits.
Anthropic said in June 2026 that a planned change to bill Agent SDK and claude -p usage separately had been paused, and its October 7 update repeats that "Nothing changes for your plan" for signed-in use (Agent SDK with your plan). That could change again, so check the page if you depend on it.
Does Pro get anything similar
No. Pro is not eligible for monthly API credits, and Anthropic says Pro "does not include API usage through the Claude Console" (Pro plan). Pro subscribers can still enable usage credits.
Why the confusion happens
Three things share the word "credits": the monthly Claude Platform credits above, usage credits for going past plan limits, and credits you buy in the Console for API use. The first and third end up in the same place: the monthly credits land in your linked Console organization's balance next to anything you bought there, and are spent first. A message like "Credit balance is too low" belongs to that Console balance; on a subscription, Anthropic ties it to an API key routing your requests to the Console. See Fix "Credit balance is too low".
A quick rule: if you claimed it by linking a Console organization and it refreshes each billing cycle, it is the monthly API credit. If you turned it on and bought it in Settings > Usage on claude.ai, it is a usage credit. If you bought it in the Console, it is ordinary API credit.
Planning around it
If your work is mostly interactive Claude Code, the monthly API credits are not a reason to pick a plan. They matter if you also build with the API or the Agent SDK. Anthropic does not publish token or message counts behind any plan, only multipliers, so neither credit type lets you compute a precise amount of Claude Code time.
Watching what your plan has left
Headroom is a free Mac menu bar app that shows session and weekly use for each Claude Code account signed in on your Mac, so you can see when the plan allowance, not any credit balance, is running low. It does not show usage credit spend, monthly API credits or Console billing, and it never sends a prompt. It is independent, not made or endorsed by Anthropic. Get it at headroom.everydaymactools.com.