Claude API credits fund the Console key, not the Claude Code seat
Claude API credits are a monthly Console balance: $100 on Max 5x, $200 on Max 20x, Team Standard $20 or Premium $100 pooled to a $500 cap. Unused credit expires. They pay the Claude API, Playground, Managed Agents and the Agent SDK, and they do not pay interactive Claude Code. Pexon meters the linked key, because every key spends it.
Announced 7 October 2026
What each Claude API credit actually deposits
| Plan | Monthly credit | What the help article states | Caveat in the same row |
|---|---|---|---|
| Max 5x | $100 | Included on an active Max 5x plan | Claim after seven days. One Console organization. Unused credit expires. |
| Max 20x | $200 | Included on an active Max 20x plan | An upgrade from Max 5x deposits a prorated credit immediately, then $200 each cycle. The article states no proration fraction. |
| Team Standard | $20 per seat | Pooled with every other seat on the plan | The pool is capped at $500. It is calculated from the seats when the credit is granted. |
| Team Premium | $100 per seat | Same pool as Standard seats | Three Standard seats plus two Premium seats are the article's $260 example. |
| Free, Pro, Enterprise | Not eligible | The credit is limited to Max and Team | A company already on Enterprise does not receive this credit, so the announcement does not fund that API bill. |
Amounts are the monthly API credit, read from Anthropic's help article on 21 October 2026. They are not a statement of the subscription price. Discounted Nonprofit and Scientists Team plans use the same $20 and $100 seat rates.
The balance expires, and every API key spends it
Budgeting the headline credit as a private allowance is the mistake. The driver is a shared, expiring balance. Anthropic deposits the credit into one linked Claude Console organization shortly after the plan payment. On an annual plan the credit still arrives monthly.
Anything left at the end of the billing cycle expires. It does not roll over.
Monthly credit is spent before any credit the organization has purchased. Everyone with an API key in that organization draws the same balance. The credit does not change usage limits in Claude, Claude Code or Claude Cowork, so a seat can sit inside its plan limits while the API is the line that hits zero. Purchased credits or auto-reload keep requests running after the monthly credit is gone. With neither, and with no sales invoice, API requests stop until the next monthly credit. Anthropic states that this usage is never charged to the Claude plan. If Anthropic sales invoices the organization, usage beyond the credit is billed as usual.
Three Standard seats and two Premium seats deposit $260 a month, and one more Premium seat makes $360, both under the $500 cap. The help article states both totals. Read 21 October 2026.
Standard seats
3 × $20
The article's example uses three Standard seats at the published $20 rate.
Premium seats
2 × $100
The same example uses two Premium seats at the published $100 rate.
Article's sum
$260
The help article states that this seat mix receives $260 a month.
Against the cap
Under $500
The same page caps the Team pool at $500. One more Premium seat is the article's next figure, $360, still under the cap.
Input figures are the monthly credit table and the seat example on Anthropic's help article “Monthly API credits for Max and Team plans”, read 21 October 2026. The arithmetic repeats that example: three Standard seats at $20 plus two Premium seats at $100, which the article states as $260, and one further Premium seat, which it states as $360. Excluded: subscription prices, token rates, and any proration fraction. The article says an upgrade from Max 5x to Max 20x is prorated immediately and does not give the fraction.
Four ways the credit leaves another bill untouched
Unused credit expires, and every API key in the linked organization spends the same balance.
- Expiry. Unused credit expires at the end of the billing cycle. A quiet month does not fund the next one.
- One key ring. Every API key in the linked organization spends the same balance. The article's control for that is a workspace spend limit in the Console. It does not describe the limit screen.
- The plan stays a plan. Interactive Claude Code in the terminal, IDE, desktop or web does not draw the credit. Extra usage after a plan limit does not draw it either.
- A hard stop. With no purchased credits, no auto-reload and no sales invoice, API requests stop. They are not silently added to the Claude subscription.
A Console key spends the credit, and a plan login does not
An API key from the linked Console organization spends the credit. A Claude plan login does not, including on claude -p. Run claude -p or the Agent SDK with that key and the help article bills the usage as Agent SDK usage against the credit. Sign in with the Claude plan instead, and the same commands draw the plan limits and leave the credit untouched.
The June credit is not available.
Runs started by the Claude Code GitHub Action, an IDE extension or the Claude desktop app count as Claude Code, so the monthly credit does not cover them, even with -p. Interactive sessions in the terminal, IDE, desktop or web are excluded outright. So is extra usage in Claude, Claude Code or Claude Cowork, and so is Claude on Amazon Bedrock, Google Cloud Vertex AI or Microsoft Foundry. The October credit is the one claimed into a Console organization. It covers the Claude API, Claude Managed Agents and the Agent SDK on those terms. Messages API and Message Batches API usage, plus the Playground, draw it for any available Claude model on the Claude Platform.
Same balance, different surface
Which call draws the Claude API credit
| Surface | Draws the monthly credit | Caveat in the same row |
|---|---|---|
| Messages API and Batches API | Yes | Any available Claude model on the Claude Platform, inside the linked organization. |
| Console Playground | Yes | Same organization balance as the API. |
| Managed Agents, Agent SDK, claude -p on a Console key | Yes | Only when the key belongs to the linked organization. A plan login does not spend the credit. |
| Interactive Claude Code, IDE, desktop, GitHub Action | No | Still excluded when the run passes -p. Extra usage after a plan limit is excluded too. |
| Bedrock, Vertex AI, Microsoft Foundry | No | The monthly credit does not apply to Claude on these clouds. |
Coverage rules are quoted from the same help article, including its FAQ on claude -p, read 21 October 2026.
Claim path
What has to be true before the credit appears
- Plan and role. An active Max plan, claimed by the subscriber, or an active Team plan, claimed by a Primary Owner or Owner. In the Console organization: Owner, Admin or Billing.
- Seven days. New subscribers can claim once they have been on an eligible plan for seven days. The release note says the credit rolls out over a few days.
- One organization. Settings, then Billing, on Max. Organization settings, then Billing, on Team. Link organization. One plan funds one Console organization, and that organization accepts one plan.
- The link sticks. The article says you cannot change the linked organization yourself. A later change goes through support. Pick the organization the agents will actually run in.
- Where the number lives. Credits show on the Console billing page with amount and expiry date. No card is required to claim or to spend the included credit.
When a gateway is the wrong extra layer
A single Max subscriber does not need a gateway: a Max 5x credit of $100, or a Max 20x credit of $200, on one linked key is already visible on the Console billing page. The case that breaks is the Team pool: every API key spends the same expiring balance, interactive Claude Code does not, and a GitHub Action still counts as Claude Code. Enterprise plans are not eligible, so this credit is not an enterprise API budget. Where many applications already share a key, the control layer is the LLM gateway for Claude.
Where the rest of the bill is decided
- Claude cost audit — the engagement that marks which workload draws the credit and which still draws the plan
- LLM gateway for Claude — one key ring, per-application attribution, before a Team pool is shared
- Claude API cost, the token math — token math for API usage, on its own URL so it does not share this credit query
- The Claude Code bill — interactive Claude Code stays on the plan, which is why that bill is a separate page
What finance asks before anyone links an organization
Do Claude API credits pay for interactive Claude Code?
Interactive Claude Code does not draw Claude API credits. The help article excludes the terminal, the IDE, the desktop app and the web app, and it excludes extra usage after a plan limit. A GitHub Action, an IDE extension or the desktop app still counts as Claude Code when it passes -p, so the monthly credit does not pay those runs either.
How large are Claude API credits on Max and Team?
Max 5x includes $100 and Max 20x includes $200 each cycle. Team Standard seats add $20 each and Premium seats add $100 each, pooled into one balance and capped at $500. The article's example is three Standard seats plus two Premium seats, which is $260, and one further Premium seat makes the next cycle $360. Unused credit expires at the end of the billing cycle.
What happens when Claude API credits run out?
API requests stop unless purchased credits, auto-reload or a sales invoice already exist. Anthropic states that usage is never charged back to the Claude plan. If the Console organization has purchased credits or auto-reload, usage continues from those. If sales invoices the organization, usage beyond the monthly credit is billed as usual.
Which plans are excluded from Claude API credits?
Free, Pro and Enterprise plans are not eligible for this monthly credit. A new Max or Team subscriber waits seven days before the claim appears. The subscriber on Max, or a Team Owner or Primary Owner, links one Console organization, and that link cannot be changed in the product.
Does claude -p spend Claude API credits?
claude -p spends the credit only with an API key from the linked organization. Signed-in plan usage of claude -p and the Agent SDK still draws the plan limits and does not spend the credit. The June Agent SDK credit is a different offer, and the help article says that credit is not available.
Next step
Separate the monthly credit from the plan before the pool is shared
Bring the linked Console organization and the last invoice. The work is to mark which workloads draw the monthly credit, which still draw the plan, and which API key needs a spend limit before the balance is shared.