Anthropic Adds Monthly API Credits to Max and Team
Claude subscribers can fund their own apps and agents without adding a Platform payment method, but interactive Claude Code remains excluded.
Listen
AI narration
10:50
0:00 / 10:50
AI SummaryGenerated from this article
Anthropic now offers monthly API credits to Claude Max and Team subscribers, allowing them to fund applications and agents without adding a separate payment method. Max 5x subscribers receive $100 monthly while Max 20x gets $200; Team plans receive per-seat allowances up to a $500 organizational cap. The credits cover Claude Platform API usage but exclude interactive Claude Code sessions. Subscribers must link a Console organization to claim the balance, which refreshes monthly and expires if unused.
Claude Max subscribers can now claim $100 or $200 in monthly API credits, while Team subscriptions receive a shared allowance of up to $500. Anthropic says eligible subscribers do not need to add a payment method to Claude Platform to claim or spend the credits.
Announced in Anthropic’s October 7, 2026 release notes, the benefit is rolling out over several days. It gives developers already paying for Max or Team a recurring budget for building API-backed applications and agents.
The credits fund eligible Claude Platform usage, not additional chat capacity or interactive Claude Code sessions. Subscribers must claim them by linking a Claude Console organization. Paying for an eligible plan alone does not put the balance into an application’s account.
Max Gets $100 or $200, While Team Credits Are Pooled
Discounted Team plans, including Nonprofit and Scientists plans, receive the same per-seat amounts. Free, Pro, and Enterprise subscriptions are not eligible.
Team subscribers share a single organization balance. Anthropic’s example of three Standard seats and two Premium seats produces $260 per month: $60 from the Standard seats and $200 from the Premium seats. Members do not receive separate credit accounts.
Adding seats can increase the pool until it reaches the $500 ceiling, so larger teams should account for that cap when evaluating the benefit. Seat changes affect the next monthly credit calculation.
For someone already paying for Max, the allowance can offset eligible experimentation costs without a separate API credit purchase. It does not reduce the subscription’s price, and its practical value depends on using the credits before they expire. Developers who only use Claude chat or interactive Claude Code will not gain additional capacity.
Work with Zeniteq
Let’s work together
We’re open to thoughtful collaborations with teams building in AI. Explore the ways we can work together.
Claiming credits requires permissions on both the Claude subscription and the Console organization receiving them.
Before opening billing settings, check that:
Your subscription qualifies. It must be an active Max or Team plan in good standing.
You have cleared the waiting period. New subscribers can claim after seven days on an eligible plan.
You have the required subscription role. On Max, you must be the subscriber. On Team, you must be a Primary Owner or Owner.
You have the required Console role. You need Owner, Admin, or Billing access in the receiving Console organization.
You have chosen the right destination. Each plan can link to only one Console organization, and each organization can receive credits from only one plan.
Subscriptions purchased through iOS or Android are eligible, but the claim happens on claude.ai in a web browser.
Choose the organization carefully. Subscribers cannot change the linked organization themselves; changing it later requires contacting support. A Team owner should confirm which Console organization holds the team’s applications and API keys before linking.
A missing API credits section does not necessarily mean the account is ineligible. The rollout takes several days, and the seven-day requirement and role checks still apply. Anthropic advises contacting support if an account appears eligible but the offer remains unavailable.
Claim the Credits, Then Use the Linked Organization’s API Key
Open billing settings on claude.ai. Max subscribers use Settings > Billing. Team Owners or Primary Owners use Organization settings > Billing.
Find the API credits section and select “Link organization.” Choose the Console organization that should receive the balance, or create one during the flow.
Review the Supplemental Credit Terms and confirm the link.
Check the balance in Claude Console. The credits appear under Settings > Billing, in the Promotional credits section, with an amount and expiry date.
You can then create an API key in that organization and use it for eligible requests. Existing applications must use a key belonging to the linked organization to draw from its balance. A key from a different organization does not gain access simply because its owner has a Max subscription.
The allowance can fund a document-processing prototype, an application backend, or an agent built with Anthropic’s supported tools. The Console Playground is also covered, so subscribers can explore requests there before connecting an application.
Everyone with an API key in a linked Team organization draws from the same balance; linking does not assign members personal spending allowances. Anthropic recommends workspace spend limits to control usage by project or teammate, a useful precaution when several experiments run simultaneously.
Interactive Claude Code Is Excluded, With a Narrow claude -p Exception
The credits cover any available Claude model on the Claude Platform through eligible products:
The Claude API, including the Messages API and Message Batches API.
The Playground in Claude Console.
Claude Managed Agents.
The Claude Agent SDK.
They do not cover interactive Claude Code in the terminal, IDE, desktop, or web. Extra usage in Claude, Claude Code, or Claude Cowork is also excluded, and the credits do not increase those products’ subscription usage limits.
Credits cannot pay for Claude usage through Amazon Bedrock, Google Cloud Vertex AI, Microsoft Foundry, or Claude Platform on AWS. They belong to the linked Claude Console organization and cannot be used across every service that offers Claude models.
For developers using noninteractive tooling, Anthropic’s coverage guidance for claude -p says the credits cover that command and the Agent SDK when developers run them themselves with an API key from the linked Console organization. Anthropic bills that usage as Agent SDK usage.
When authenticated with the Claude subscription instead, those runs continue to draw from the plan’s usage limits and do not spend the API credits.
Runs started by the Claude Code GitHub Action, an IDE extension, or the Claude desktop app count as Claude Code usage and remain excluded, even with -p. Eligibility depends on the authentication method and how the run starts, as well as the command flag.
Credits Expire, and Existing Billing Can Still Continue
The balance refreshes each billing cycle, shortly after the subscription payment goes through. Annual subscribers receive credits monthly rather than as one annual allocation.
Unused credits expire at the end of the applicable cycle and do not roll over. Included credits are spent before purchased credits, so an organization with an existing paid balance can use the monthly allowance first.
What happens after that depends on the organization’s billing setup:
With no other credits: API requests stop until the next monthly allowance arrives.
With purchased credits: Requests continue using the purchased balance.
With auto-reload enabled: The organization can replenish its purchased balance.
With Anthropic sales invoicing: Usage beyond the included credits is billed as usual.
API usage is never charged to the Claude subscription itself. Claiming credits does not disable an organization’s existing paid billing arrangements.
Anthropic’s credit application rules specify that auto-reload watches the purchased balance, not the combined purchased and included balance. It can reload purchased credits when that balance reaches its threshold even if monthly credits remain.
For a strictly bounded experiment, check the linked organization’s purchased balance, auto-reload settings, and spend limits before starting.
A Funded API Account Still Has Usage Limits
The allowance does not remove Claude Platform’s rate and spend limits. Rate limits constrain request and token throughput, while spend limits cap monthly API costs. Credit-funded usage still counts toward the organization’s spend cap.
Organizational spend caps reset on the first of the calendar month; credits refresh on the subscription billing cycle. An organization can therefore have credits available without having remaining spend capacity.
Anthropic says linked organizations move to at least the Start tier, and organizations receiving more than $200 in monthly credits move to at least the Build tier. Beyond those provisions, claiming the allowance does not automatically raise the usage tier.
How far the balance goes depends on the model and workload. Anthropic recommends choosing an appropriate model, caching repeated context, and using the Message Batches API for work that can wait, which it describes as costing 50% less.
Existing subscribers can start by verifying eligibility, linking the organization where the application will run, and checking the expiry date and billing controls. The recurring budget supports building outside Claude’s subscription interface, but it lowers actual spending only when eligible workloads consume the credits before they expire.
