Claude Max and Team API credits: up to $500/month to build

If you already pay for Claude Max or Claude Team, you now get monthly Claude API credits at no extra cost. Anthropic started the program on October 7: $100 a month on Max 5x, $200 on Max 20x, and up to $500 pooled on Team. That is real budget for a support triage bot, an invoice parser, or a lead-scoring agent. It also expires every month. Money you do not spend is money you lose.

What actually happened

Per Anthropic's docs, the credits land in a Claude Console organization that you link to your plan. You do not need a payment method on the Console to use them.

• Amounts: Max 5x gets $100. Max 20x gets $200. Team gets $20 per Standard seat and $100 per Premium seat, pooled into one balance and capped at $500. Anthropic's example: three Standard plus two Premium seats is $260 a month.
• Covers: the Claude API, Claude Managed Agents, the Claude Agent SDK, and the playground.
• Does not cover: Claude Code, extra usage in the Claude apps, or Claude through Bedrock, Google Cloud, or Microsoft Foundry.
• Expiry: unused credits expire at the end of each billing cycle. No rollover.
• Eligibility: Free, Pro, and Enterprise are out. New subscribers wait 7 days before they can claim.
• One link only: each plan links to one Console organization, and you can't change it yourself. Pick the org you will actually build in.

When the credits run out and you have no purchased balance, API calls stop. Anthropic says usage is never charged to your Claude plan. The Claude Help Center repeats the Claude Code exclusion. It matters: the credits are for the apps you ship, not for the coding tool you use to build them.

Why it matters for your business

This is a free pilot budget. Most small businesses never start an AI automation because nobody wants to own a new monthly bill before it proves out. A Team plan with a few seats now covers a few hundred dollars of API usage every month. On Claude Haiku 5.5 at $0.10 per million input tokens, $260 runs a lot of ticket triage.

Use it or lose it, so plan the spend. No rollover means an idle month burns the credit. Pick one workflow that runs daily, like inbox sorting, order-exception alerts, or review summaries, and put it on the credits first.

Fence it off. Every API key in the linked org draws from one balance. Give each project its own workspace with a spend limit so one runaway loop does not eat the month.

Build it portable. Credits are a promotion, and promotions change. Write the agent so the model and provider sit in config. Then the credits pay for the pilot, and you are not locked in when the terms move.

Sources: Anthropic Claude Platform docs, Claude Help Center.