Claude Max and Team API Credits: Claiming and Billing

Claude Max and Team monthly API credits go into a linked Claude Console organization. They do not increase your Claude or interactive Claude Code subscription limits. That is why an API balance can remain available while Claude Code reports a limit.

The most useful check is not “Do I have credits?” but “Which organization and billing route does this particular run use?” This guide follows the official monthly-credit FAQ, checked October 15, 2026. We did not claim credits, access a subscriber account, or run a paid request. The steps below describe the documented process, not an account test.

Who gets credits, and how much?

The Team pool is capped at $500 per month. For example, ten Standard seats and four Premium seats would produce $600 before the cap, so the monthly pool is $500. This is an arithmetic example, not a customer invoice. Discounted nonprofit and scientist Team plans are included. Free, Pro, and Enterprise are not eligible for this program.

The subscription must be active and in good standing. Mobile subscriptions can qualify, but claiming happens on the Claude website. Availability is rolling out, and the seven-day eligibility period still applies. Do not buy or upgrade a plan solely because another account already displays the button; first check the current conditions for your own account.

Link the right organization before claiming

There are two permission checks. For Max, the subscriber claims the benefit; for Team, a Primary Owner or Owner does so. On the Console side, the person linking must be an Owner, Admin, or Billing member of the destination organization.

1. Sign in on the Claude website. Open Settings → Billing for Max, or Organization settings → Billing for Team.
2. Find API credits and choose Link organization when the option becomes available.
3. Select an existing Console organization or create one through the offered flow. Confirm its name and ownership with whoever manages your application billing.
4. Review the terms and destination, then complete the link.
5. In Console, verify that the credit balance belongs to that organization. Check that the API key used by your application belongs to the same organization.

Stop before step 4 if the organization is wrong. A plan links to one Console organization, and an organization can receive this benefit from one plan. You cannot self-serve a change to the linked organization; the FAQ directs you to support. An organization used by a previous employer or a personal test project is not interchangeable with your production organization.

The FAQ says a payment card is not required just to claim. That does not mean arbitrary future API usage is free. Check purchased balances, automatic reload, invoiced billing, and workspace spending limits separately.

Identify the balance your run actually uses

The -p flag alone is not a billing switch. A terminal command you run yourself with an API key is different from a Code run launched by an IDE or GitHub Action. The FAQ explicitly preserves that distinction. Do not “fix” a limit by repeatedly rerunning a command without checking its authentication path.

These credits also do not automatically appear in an Ofox or other provider wallet. A third-party BYOK integration needs its own routing and billing verification; the official FAQ is not evidence that every such integration can or cannot pass through the benefit. Ofox publishes this explanation but does not issue the Anthropic credits.

A billing check that does not expose your key

Record four non-secret fields before investigating a discrepancy:

If you already have an authorized request, compare its time and usage with the corresponding Console organization. A successful response alone does not prove that promotional credit paid for it. Conversely, a visible credit balance does not prove that the running application uses that organization.

Do not paste keys into support messages, print environment variables into shared logs, or switch production authentication just to test the theory. If a fresh request is necessary, obtain the relevant budget authorization and use a small controlled task. This article did not perform that test.

Why the button or credits may be missing

Check the specific failure before changing settings:

• No API credits section: confirm the plan, seven-day waiting period, rollout status, and that you are using the website. A mobile purchase does not require claiming inside the mobile app.
• Cannot select or link the organization: verify both sets of roles and whether the organization is already linked to a plan.
• Credits visible, Code still limited: inspect the run’s launch source and authentication. A subscription limit is not replenished by API credit.
• API usage appears elsewhere: check the key’s organization and any gateway/provider configuration. Do not assume the most recently opened Console organization owns that key.
• Wrong organization already linked: use support; creating more keys does not move the credit allocation.

For the separate problem of actual Code rate-limit responses, use our Claude Code rate-limit troubleshooting guide. Keep that diagnosis separate from credit eligibility.

Refresh, expiration, and charges after exhaustion

Credits refresh with the subscription’s billing cycle; annual subscriptions still receive monthly allocations. Unused credit does not roll over. The organization uses the included credit before purchased credit, and keys across that organization share the pool. Workspace spend limits can help constrain individual workloads; they do not create separate monthly gifts for every key.

After the included balance is used, purchased credit or automatic reload can keep API calls running and spending money. Invoiced organizations follow their regular overage billing. With no other available credit, API usage stops until credit is available again. API spending is not simply added to the Claude subscription bill.

Canceling or moving to an ineligible plan stops future allocations; existing credit remains usable until its expiration. The FAQ also describes prorated additional credit for Max 5x → Max 20x upgrades, and a separate Team claiming process after a Max → Team change. Check those rules before assuming that a plan change preserves the same link and schedule.

Your completion check

You have resolved this task when you can name the eligible plan, the linked Console organization, the launch and authentication route, the current credit period, and the fallback billing behavior after exhaustion. “The button is visible” or “the model replied” is only one piece of that evidence.

For the price of the model itself, see Claude API pricing and our Haiku 5.5 100K cost calculation. A monthly credit is a funding source; it does not change the model’s token meter.