Claude Max included API credits: what the allowance covers

TL;DR

• Eligible Max 5x plans include $100 per month in Claude Platform API credits.
• Eligible Max 20x plans include $200 per month; Team credits are pooled based on seats.
• A subscriber may need to claim the credits in Claude settings and link one Claude Console organization.
• The credits cover API and selected platform surfaces. They do not increase interactive Claude or Claude Code limits.
• Credits expire at the end of the billing cycle and do not roll over. Eligibility and personal balance still need an account check.

The useful detail in Anthropic's monthly API credit policy is the boundary. The allowance is a separate Claude Platform budget. It is not extra interactive Claude Code capacity hiding inside a Max subscription.

The official Help Center article, checked for the October 7, 2026 rollout, says eligible Max 5x plans include $100 per month and eligible Max 20x plans include $200 per month. Team plans receive pooled credits based on their seats. Anthropic says availability rolls out over a few days, so a plan description alone does not prove that a particular account can claim the benefit.

What the credits cover

The credits apply to the Claude API, Claude Console Playground, Claude Managed Agents and the Claude Agent SDK. A builder can use that budget for an app or an agent that calls the platform through those surfaces.

They do not cover interactive Claude, extra usage in Claude or Claude Code, Claude Cowork, or Claude through Bedrock, Vertex AI or Microsoft Foundry. That distinction matters when you plan a workflow. An API experiment can use the included budget while a long interactive coding session still consumes its own plan limits.

Treat the two pools as separate ledgers. If a task is running in Claude Code, do not assume moving it to the API is a free continuation. Prepare a bounded API task with its own credentials, data boundary, acceptance check and stop condition.

The claim path has a few gates

The plan must be active and in good standing. A new subscriber may claim after seven days on an eligible plan. The claim links one Claude Console organization through Claude billing settings, and the credits go to that organization.

That creates an ownership question for teams. Before an API call, record which Console organization receives the allowance and who can inspect its billing view. A team member's interactive plan and a shared API organization are related, but they are not the same source of truth.

The credits refresh each billing cycle. Unused credits expire at the cycle end. They do not roll over. The practical action is to check the claim and expiry date, then choose a small experiment that can finish before the window closes. Do not build a forecast from an unverified balance or from a weekly Claude Code reset.

A useful experiment uses a receipt

I spend around $600 a month across AI subscriptions. In my private Meter work, I want allowances, reset dates and local activity to remain visible without turning a personal estimate into a provider invoice. The same discipline applies to an API-credit experiment.

Write down the experiment before spending the credit:

1. State the question the API call must answer.
2. Define the input data and the fields the model may change.
3. Set a request and token ceiling.
4. Save the response, model identifier, date and source account.
5. Run a deterministic check or human review against the result.

If the experiment fails, keep the failed attempt and its reason. A zero-cost result can still waste time, and a successful response without a check can still be wrong. A separate route also needs a handoff record if the work returns to Claude Code or moves to another provider.

What the allowance does not prove

An eligible plan does not prove a personal credit balance. A visible claim button does not prove that the credits have been used. A provider announcement does not prove a saving on a particular workload. Label a provider-reported balance with its source, currency, coverage and observation date. Label a list-price estimate as an estimate. Keep owner-entered records separate.

This level of bookkeeping is not busywork. It is how a builder can compare API experiments with subscription work without inventing a bill or hiding an expired allowance.

Sources and related reading

The source event is my October 8 LinkedIn post. The post was edited in place; it does not claim personal eligibility, a remaining balance or savings.

• What one resolved SWE-bench task really costs
• How to measure AI subscriptions across accounts and machines
• Claude vs Codex: choosing a personal workflow
• SASID service companion: Claude Max included API credits

For a task-side view of checks and source status, open the Agent receipt example. Use it to plan what evidence an API experiment should leave behind.