Claude Max API Credits: What $100 to $500 a Month Buys

On 7 October 2026 Anthropic started giving Claude Max 5x subscribers $100 a month in API credits, Max 20x subscribers $200, and Team plans up to $500 pooled, and unused credit disappears at the end of each billing cycle. At list prices, $200 buys roughly 667 runs of a 20K-input, 2K-output agent task on Fable 5.1, 3,333 on Sonnet 5.5, or about 66,666 on Haiku 5.5. The credits cover the API, Managed Agents and the Agent SDK. They do not cover interactive Claude Code. Below: the arithmetic per model, the exact coverage rules quoted from Anthropic, the Haiku 100K price cliff, three ways people burn the credit, and when Max 20x beats paying list price.

The change surfaced in the Haiku 5.5 launch discussion on Hacker News (1,047 points, 488 comments), and Simon Willison noted it the same day: Max 5x gets $100 a month, Max 20x gets $200, Team gets "up to $500, pooled across their users", and the credits "do not roll over".

What Anthropic actually promises

Anthropic's developer page, API credits for Max and Team plans, gives the amounts:

Team credits for all seats pool into one balance capped at $500. Anthropic's own example: three Standard seats plus two Premium seats gives $260 a month. Free, Pro and Enterprise plans are not eligible. New subscribers can claim after 7 days on an eligible plan.

Claiming takes a few clicks. In claude.ai, open Settings, then Billing, and link a Claude Console organization in the API credits section. The catch: "Each plan links to one Console organization, and each Console organization can receive credits from one plan. You can't change the linked organization yourself." Pick the org you will actually build in. Credits then show up in the Console under Promotional credits, and no payment method is required on Claude Platform.

What draws on the credits and what does not

The developer page lists the covered products: the Claude API, Claude Managed Agents, the Claude Agent SDK and the playground. Not covered: Claude Code, extra usage in the Claude apps, and Claude on Bedrock, Google Cloud or Microsoft Foundry. It also says credits "don't change your usage limits in Claude or Claude Code."

That leaves the part everyone argues about: headless Claude Code. The Help Center article splits it by how you authenticate:

• With an API key from the linked Console org: "API credits cover claude -p and the Claude Agent SDK when you run them yourself with an API key."
• Signed in with your Claude plan: claude -p and Agent SDK usage "still draw from your plan's usage limits and don't use your API credits."
• Interactive Claude Code in the terminal, IDE, desktop or web: not covered.
• The Claude Code GitHub Action, IDE extensions and the desktop app: "count as Claude Code usage, so API credits don't cover them, even with -p."

One ambiguity. A second Help Center article says the credits "cover the Claude Agent SDK, claude -p, the Claude API, and Claude Managed Agents" and that you can still run those "with your subscription limits." Read together with the first article, the rule is the credential: API key from the linked org draws credits, plan sign-in draws plan limits. Anthropic does not state that rule in one sentence on either page, so test it. Run one cheap claude -p call with the key and watch the Promotional credits balance in the Console move.

If a request is not covered and the org holds only these credits, Claude Code shows "Credit balance too low." When the balance hits zero, "API requests stop until your next monthly API credits arrive" and usage is never charged to your plan. Every API key and workspace in the linked org draws from the same balance, so give each project its own workspace with a spend limit.