Claude API Credits From Team and Max Plans

Claude API credits are the monthly Claude Platform credits that come with Claude Max and Team plans, spent by any API key in the one Claude Console organization linked to the plan — so an Anthropic key from that organization can pay for Claude in Insulin until the credits run out or expire at the end of the billing cycle.

---

Since October 7, 2026, Claude Max and Team plans have come with monthly API credits, and anyone running an AI workspace on their own Anthropic key will ask whether the plan they already pay for can cover it. It can, through an ordinary API key. The credits are a balance in a Claude Console organization, and Anthropic’s page on API credits for Max and Team plans says you “can use them to build and run your own applications and agents.”

The surprises are in the rest of that page: every key in the organization shares the balance, it expires every billing cycle, and once it’s spent, an organization with no other credits can’t call the API until the next monthly credits arrive. This post follows the credits from the plan to an Insulin agent, then covers what happens at zero. Whether to bring your own key at all is a separate decision, covered in BYOK vs managed models for enterprise AI.

What are Claude API credits on Team and Max plans?

Claude API credits are monthly credits for the Claude API, included with Claude Max 5x, Max 20x and Team plans and delivered to one Claude Console organization linked to the plan. Anthropic’s release notes announced them on October 7, 2026, and the plans include them from that date; a new subscriber can claim after seven days on an eligible plan.

Plan	Monthly credit	How it’s counted
Max 5x	$100 USD	One subscriber’s plan
Max 20x	$200 USD	One subscriber’s plan
Team, Standard seat	$20 USD per seat	Every seat pools into one balance, capped at $500 USD
Team, Premium seat	$100 USD per seat	The same pool and the same cap

Discounted Team plans for nonprofits and scientists earn the same per-seat amounts. Free, Pro and Enterprise plans aren’t eligible.

The cap comes quickly: 25 Standard seats or five Premium seats already reach $500, so a team of 40 Standard seats gets the same pool as a team of 25. Each month’s credit counts the seats on the plan at the start of that billing month.

The credits cover the Claude API, Claude Managed Agents, the Claude Agent SDK and the playground. They don’t cover Claude Code, extra usage in the Claude apps, or Claude Platform on AWS, Amazon Bedrock, Google Cloud or Microsoft Foundry: “These credits apply only to the Claude API in the Claude Console.”

Can Claude API credits pay for Claude in Insulin?

Yes, through an Anthropic API key created in the linked Console organization. Insulin’s Anthropic connection takes an API key, and Fours’ Anthropic integration page says billing for that usage is “handled directly by Anthropic.” Because “every API key and workspace in the linked organization draws from the same balance,” Claude turns on that key spend the included credits first.

Which kind of connection holds the key decides which agents spend the credits:

• An organization-level connection is made under Settings → Integrations, where only an org ADMIN can connect or disconnect the organization’s integrations. It’s billed to the organization, and organization agents run on it.
• A personal API key is connected by a member for themselves and billed to that person. The built-in Insulin assistant and that member’s personal agents run on it, and per Model Selection they “never reach the organization’s keys.”

That split matters more than it looks. A Team plan’s credits fit an organization-level connection, but there they pay only for organization agents, because the built-in Insulin assistant runs on each member’s own keys. A member’s personal key spends the pool only if it, too, was created in the linked organization. A Max plan is one person’s subscription, so its credits fit a personal key.

Two things never touch the credits: a key from any other Console organization, and Claude reached through another provider’s key, such as Claude Sonnet 5 on DigitalOcean GradientAI, which that provider bills.

One condition comes with the link. The program terms say credits can’t be transferred or sold, and “may only be used by the holder of the Anthropic account to which the Credits are associated,” per Anthropic’s supplemental credit terms. Keep the key with the organization that holds the credits, for its own work, and ask counsel to read the terms if any other party’s work would run on it.

How do the credits reach an Insulin agent?

In five steps: claim, link one Console organization, create a key there, connect it in Insulin, and let the balance run. The first two happen once and are hard to undo; the last is where the surprises are.

Step	What happens	Who does it	What to get right
1. Claim	On claude.ai, Settings > Billing on Max or Organization settings > Billing on Team, then the API credits section	Max: the subscriber. Team: the Primary Owner or an Owner. Either way, also an Owner, Admin or Billing member of the Console organization	New subscribers wait seven days on an eligible plan
2. Link one organization	Credits arrive there each billing cycle, under the Console’s Promotional credits with an amount and an expiry date	The same person, in the same step	One plan, one organization: “You can’t change the linked organization yourself.” Changing it takes Anthropic support
3. Create an API key in it	The key draws on the shared balance, like every other key and workspace there	A Console member allowed to create keys	Only keys from this organization spend the credits
4. Connect it in Insulin	Organization level: organization agents. Personal: the built-in assistant and that member’s own agents	An org ADMIN for the organization; any member for themselves	A non-empty AI Model Policy allow-list must include Anthropic
5. Spend it	Included credits first, then purchased ones. With no credits left, Anthropic stops serving the key	Nobody: it’s automatic	Insulin fails over to your next connected provider, then to Fours-hosted models, unless your AI Model Policy rules them out

Three notes on the path:

• Link the organization you mean to keep. Anthropic says to “link the organization you plan to build in.” If the key later has to come from another organization, Insulin can’t edit an Anthropic key in place: delete the connection and create a new one.
• The pool has no lanes. Developers’ scripts, Managed Agents sessions and Insulin all draw on one balance. If a project needs a ceiling, Anthropic’s answer is to “give it its own workspace and set that workspace’s spend limit.” How AI API spend limits work when you bring your own key covers that cap beside Insulin’s own.
• The allow-list can block the key. When the AI Model Policy’s Allowed AI integrations list has rows, AI features may use only those, so an Anthropic connection left off it serves nothing. How the AI model allowlist decides which vendors see your prompts covers each row.

What happens when the Claude credits run out?

It depends on what else the linked organization holds: purchased credits keep Claude running, an invoiced account keeps billing, and an organization with nothing left has its requests stopped until the next monthly credits arrive. Only the last case reaches your Insulin agents, as a failed model call.

If the linked organization…	Anthropic	Your Insulin agents
Also holds purchased credits	Requests continue on purchased credits; auto-reload, if it’s on, refills the purchased balance	Keep running on Claude, now on credits you paid for
Is invoiced through Anthropic sales	”Usage beyond the API credits is billed as usual”	Keep running on Claude, on your invoice
Has no credits left	Requests stop until the next monthly credits, returning “Your credit balance is too low to access the Anthropic API…”; nothing is charged to your Claude plan	Each turn fails over to another model

Check auto-reload before relying on the first row: it’s “based only on your purchased balance” and reloads “even if included credits remain,” so it can charge your card while included credits are left.

In Insulin, a failed call doesn’t end the turn. Model Selection says that “if a model call fails — a provider outage, a usage limit, or a rejected key — the turn retries on your next connected provider,” with the Fours-hosted models as “the fallback the turn degrades to.” So when the credits run out, an organization agent keeps answering on your next provider’s key, or on a hosted model billed to your Insulin balance. Which hosted models serve Insulin chat covers that pool.

Whether a turn should fall back that far is an org ADMIN’s call, on Settings → Organization → AI Model Policy. The platform-key switch is on by default. Turned off, it makes the organization bring-your-own-key only, where “every AI call must then use one of your own connected keys,” so a turn whose Claude key has run dry goes to your next key or stops, never to a hosted model. A non-empty allow-list without the hosted-model row removes the hosted pool the same way.

You’ll see it in three places, and not in a fourth:

• The reply. A turn that switched models ends with an italic note naming both. Insulin writes hit its usage limit for a quota and was unavailable for other errors, so don’t read a Claude model that was unavailable as an Anthropic outage before checking the credit balance.
• The Console. Promotional credits, under Settings > Billing, shows the amount and its expiry date.
• The Usage panel. On Insulin’s Settings → Billing, group the period by Provider to see turns move from Anthropic to the hosted models.
• Not the integration card. API-key connections such as Anthropic’s never show Insulin’s Connection expired alert, because they can’t be checked without using the key.

Each new turn starts from the agent’s usual model, so Claude returns with no change in Insulin once the organization has credits again.

Who pays for what when Claude runs on the credits?

Two balances, two bills: the credits pay Anthropic for the Claude tokens, and your Insulin balance pays Fours’ flat platform fee on the same tokens. On your own key, the provider bills the tokens under your own contract, and Fours charges “a flat fee per unit.” Insulin’s pricing sets it at $0.10 per million tokens, input and output, the same whichever model you run.

The two balances run out independently:

• The Claude credits pay only Anthropic, so they never cover the platform fee, a hosted-model turn after failover, or sandboxes and storage.
• Your Insulin balance, or your invoice on monthly billing, pays all of those. On pay as you go, AI features pause when the balance reaches zero, and “a zero balance still pauses BYOK requests, because the per-unit fee is still owed,” so a workspace can stop with Claude credits left. Monthly billing is never stopped for a balance.

A Team pool can carry the token bill, then, but someone still owns the Insulin balance, and the decision to let a fallback spend it.

Frequently asked questions

Which Claude plans include monthly API credits?

Max 5x ($100 a month), Max 20x ($200) and Team, including discounted Team plans, at $20 per Standard seat and $100 per Premium seat, pooled and capped at $500. Free, Pro and Enterprise plans aren’t eligible, and new subscribers can claim after seven days.

Can Claude API credits pay for Claude in Insulin?

Yes, through an Anthropic API key created in the Console organization linked to your plan, since every key there draws on the credits. An organization-level connection serves organization agents; the built-in Insulin assistant and personal agents run on each member’s own key.

Do Claude API credits cover Claude Code?

No. Anthropic lists Claude Code and extra usage in the Claude apps as not covered, along with Claude Platform on AWS, Amazon Bedrock, Google Cloud and Microsoft Foundry. The credits pay for the Claude API, Claude Managed Agents, the Claude Agent SDK and the playground.

Do unused Claude API credits roll over?

No. Unused credits expire at the end of each billing cycle, or monthly on annual plans. Included credits are spent before any you’ve purchased, and every API key and workspace in the linked organization draws on the same balance.

What happens to an Insulin agent when the credits run out?

With no other credits in the linked organization, Anthropic stops serving the key. Insulin retries the turn on your next connected provider, then on Fours-hosted models billed to your Insulin balance, unless your AI Model Policy rules them out. A fallback reply’s note names both models.

Do Claude API credits cover Insulin’s platform fee?

No. The credits pay Anthropic for Claude tokens. Fours charges a flat platform fee per token on your own keys, drawn from your Insulin balance, and on pay as you go a zero Insulin balance pauses AI requests even while Claude credits remain.

Takeaways

• The credits work through an ordinary API key. Any key in the linked Console organization spends them, including the one you connect to Insulin.
• Choose the organization and the connection deliberately. A plan links to one organization you can’t change yourself, and an organization-level key pays for organization agents, not the built-in assistant.
• The pool is shared and monthly. Up to $500 on Team, drawn by every key in the organization and gone at the end of each billing cycle.
• Decide what happens at zero. Insulin falls back to your next provider, then to Fours-hosted models, unless your AI Model Policy says otherwise, and Fours’ platform fee comes from your Insulin balance throughout.

Claude credits change who pays for the tokens, not how Insulin runs or meters a turn. To see what a turn on your own key costs next to a hosted one, read Insulin’s usage-based pricing.