On this page4 sections
Claude’s October 7 update adds monthly API credits for Max and Team subscribers. It does not, according to Anthropic’s current guidance, remove subscription access to the Agent SDK or claude -p. That distinction matters for an operations team deciding whether its scheduled agents need new credentials, a different budget, or any migration at all.
A Reddit discussion framed the change as an end to subscription use. The current help article says those subscription paths remain available. It also records that the previously announced Agent SDK usage changes were paused on June 15. Reading the October update as a completed withdrawal would send engineers toward an unnecessary migration.
The practical question is which wallet a running job is using. Subscription access consumes the plan’s allowance; eligible API calls can consume credits in a linked Console organization. The same kind of work can therefore meet a different limit without its prompt changing. Follow the authentication and launch path first, then the balance and the cost of getting a useful result.
The same command can spend from a different balance
Anthropic’s billing FAQ distinguishes self-run claude -p and Agent SDK jobs by their authentication. Signing in with a Claude plan consumes its usage limits. Running them with an API key from the linked Console organization can consume the new API credits instead. The command’s name alone does not identify its billing path.
The FAQ makes a further distinction for runs started by the Claude Code GitHub Action, an IDE extension, or the desktop app. Those count as Claude Code usage and do not become eligible for these credits simply because a run uses -p. An engineer diagnosing an unexpected charge therefore needs the launch path as well as the credential source.
For the illustrative backup-review job, a future operator should be able to tell which Console organization and authentication mode were intended. Keep that information in the job configuration and the secret itself in the existing credential store. When a charge is surprising, the useful clue is the route the job took, not a copy of its API key in a log.
Included credits are a shared resource
The Platform documentation lists $100 monthly for Max 5x and $200 for Max 20x. Team receives $20 per Standard seat and $100 per Premium seat, pooled with a $500 ceiling. Free, Pro, and Enterprise plans are not eligible for this credit program. One plan links to one Console organization, whose keys and workspaces share its balance.
Unused credits expire rather than roll over. If they run out, purchased credits or configured auto-reload can keep requests running; without another balance, API requests stop. These credits apply to the direct Claude Platform, not Bedrock, Google Cloud, Microsoft Foundry, or Claude Platform on AWS. Moving credentials between platforms would not carry the benefit with them.
A background job can lose its allowance to work it never sees. In the backup-review example, a developer’s experiment in another workspace draws from the same linked organization balance. Workspaces and spend limits can constrain exposure, but they do not reserve a slice of that shared pot for the queue. Its capacity plan needs to account for the other callers that can spend first.
A useful backup investigation costs more than its first answer
Suppose, hypothetically, that the agent gathers failed backup records, looks up the relevant runbook, and produces an evidence bundle for a responder. Acceptance requires the affected backup identifier, the failure evidence, and a cited recovery condition. A plausible paragraph that omits the condition is an unfinished task, even if the model returned normally.
Keep retrieval, retries, and verification attached to that task. This follows the task-budget principle: calculate the resources needed for a useful outcome before optimizing an individual call. It also gives the new shared credit pool a sensible unit of planning. A rejected bundle has still consumed credit. Include that spending when estimating how many usable investigations the shared balance can support.
Consider an illustrative ledger of 100 attempted investigations. Their combined estimated model cost is $72, and 60 bundles are accepted. Cost per started investigation is $0.72, while cost per accepted bundle is $1.20. Neither number includes the reviewer’s time. Both are arithmetically correct, but the first would overstate the value delivered if presented as the price of a completed investigation.
That is the attribution problem: rejected work and corrections need to remain connected to the result. If a prompt change lowers the model spending while leaving more bundles for responders to repair, the credit lasts longer without establishing that the workflow improved. Record acceptance and correction work alongside the spending so the team can see that difference.
Keep a task limit outside the retry loop
The Agent SDK exposes maxBudgetUsd in TypeScript and max_budget_usd in Python. Its agent-loop documentation describes these as estimated-spend thresholds, not exact invoice ceilings. Checks happen after responses arrive, so the response crossing a threshold still costs money, and running subagents can add spending before they stop. Subagent budget-cap enforcement requires Claude Code v2.1.217 or later.
A restarted process should not make the same investigation newly affordable. Give the backup task an allowance that follows its identifier across calls and leaves room for verification. When that allowance is exhausted, return the unresolved bundle with what is known. The next worker can then continue the task deliberately instead of unknowingly starting a fresh spending loop.
The cost-tracking documentation adds an accounting trap: normally exited resumed sessions with Claude Code v2.1.277 or later restore earlier spending into their result totals. Summing those cumulative totals double-counts work; older versions reset resumed-call totals. Independent calls have separate totals, so the aggregation rule depends on the session relationship and installed version. SDK dollar values are client estimates; reconcile them with Console billing or the Usage and Cost API.
An empty cost field is not a free investigation, any more than an empty outcome field is a successful one. ‘Credit exhausted,’ ‘task limit reached’ and ‘accepted bundle’ send the next worker in different directions. Keeping those results attached to the original backup task is what lets a restart recover the work rather than erase its spending history.
The October update gives the team another funding path; it does not, under the guidance described here, demand a blanket migration away from subscription access. Start with the actual launch and authentication path. Then account for the whole backup investigation, including its rejected attempts and checks. The credit has earned its place when the team can explain both where it went and what usable work came back.
Source context
Source links appear within this article. Read them alongside the author’s analysis and evaluate the guidance against your environment.
Report an error or outdated detail