On this page4 sections
Imagine opening the bill for a backup-review agent that ran exactly the job it ran yesterday. Same prompt, same schedule, different allowance paying for it. The first place to look is how the job was launched and signed in. Claude’s October 7 update added monthly API credits for Max and Team subscribers; it did not, under the guidance discussed here, end subscription sign-in for the Agent SDK or claude -p.
That distinction was easy to lose in a Reddit discussion describing the change as the end of subscription use. Anthropic’s current help article says those paths remain available and records that the previously announced Agent SDK usage changes were paused on June 15. A team reading only the discussion could spend its afternoon migrating a job that did not need to move.
The practical answer is smaller than a migration: trace the job to its balance. Claude-plan sign-in uses the plan’s limits. Eligible API calls use the linked Console organization’s balance. Changing that route can change what pays for the work without changing a word of the prompt.
Start where the backup job starts
For a self-run claude -p command or Agent SDK job, Anthropic’s billing FAQ draws the line at authentication. Sign in with a Claude plan, and the job consumes that plan’s usage limits. Give it an API key from the linked Console organization, and eligible calls can consume the new API credits. Seeing claude -p in a script tells you what runs, not which balance it uses.
Now put that command inside the Claude Code GitHub Action, an IDE extension or the desktop app. The FAQ treats those launch contexts as Claude Code usage; adding -p does not make them eligible for these credits. To explain an unexpected charge, you need both pieces: what started the job and how it authenticated.
For our hypothetical backup reviewer, put the intended Console organization and sign-in mode in its configuration. Leave the actual secret in the credential store. The person investigating the bill needs to recognize the route, not find an API key printed in a log.

The credits arrive in a shared balance
As of November 2, 2026, the Platform documentation lists monthly credits of $100 for Max and $200 for Ultra. Team contributes $20 per Standard seat and $100 per Premium seat, pooled up to $500. Free, Pro and Enterprise plans are not eligible for this program. One plan links to one Console organization, and that organization’s keys and workspaces draw on the same balance.
Unused credits expire rather than rolling into next month. Once they are gone, purchased credits or configured auto-reload can keep requests running. Organizations invoiced through Anthropic sales continue with further use billed as usual; otherwise, without another credit balance, API requests stop. The benefit applies to the direct Claude Platform, not Bedrock, Google Cloud, Microsoft Foundry or Claude Platform on AWS. Moving a credential to another platform does not take the credits along.
That shared balance matters when the backup reviewer waits in a queue. Another workspace can spend it first. Workspaces and spending limits can constrain consumption, but they do not set aside a private portion for this job. Planning the night’s work therefore means counting the other callers too.
Count the investigation that someone can use
Suppose the backup agent gathers failure records, consults the relevant runbook and hands a bundle to a responder. In this teaching example, a usable bundle needs three things: the affected backup identifier, the failure evidence and a cited condition for recovery. If the agent writes a polished paragraph but leaves out that condition, the responder still has work to do. A normal model response has not finished the investigation.
The lookups, retries and verification belong on the same task’s bill. That is the task-budget principle in practice: work out what a useful result requires before optimizing one call. A rejected bundle still spends credit. Leaving rejected attempts out of the estimate makes the shared balance look as though it can buy more completed investigations than it really can.
Here is an illustrative ledger: 100 investigations started, $72 in combined estimated model cost, 60 bundles accepted. Dividing by starts gives $0.72. Dividing by accepted bundles gives $1.20. Both calculations are right, and neither includes the reviewer’s time. But only the second describes the model cost per accepted investigation in this example.
Perhaps a cheaper prompt leaves more bundles for responders to repair. That is the attribution problem: the API bill improves while the work moves to someone else’s desk. Keep rejected attempts and correction work connected to the eventual result, so a longer-lasting credit balance does not hide a longer afternoon for the responder.
A restart should remember what the task has spent
The Agent SDK offers maxBudgetUsd in TypeScript and max_budget_usd in Python. As the agent-loop documentation explains, these are thresholds for estimated spending, not exact invoice ceilings. The check happens after a response arrives, so the response that crosses the threshold still costs money. Subagents already running can add spending before they stop, too. Enforcing their budget caps requires Claude Code v2.1.217 or later.
If the backup worker restarts halfway through an investigation, it should pick up the remaining allowance, not receive a new one. Carry the task identifier and budget across calls, with enough room left to verify the bundle. When that allowance is used, hand back the unresolved bundle and what is known. The next person can then choose whether continuing is worth the cost.
There is a wrinkle when adding up the receipts. The cost-tracking documentation says that, with Claude Code v2.1.277 or later, normally exited sessions restore earlier spending when resumed: their result totals are cumulative. Adding each of those totals together counts earlier work again. Older versions reset resumed-call totals, while independent calls have separate totals. Check the installed version and whether calls belong to one resumed session before choosing the arithmetic. SDK dollar amounts are client estimates; reconcile them with Console billing or the Usage and Cost API.
An absent cost value leaves a question mark, not a free investigation. Keep that uncertainty with the task, alongside the difference between “credit exhausted,” “task limit reached” and “accepted bundle.” They describe different endings, and a restart should not erase which one happened.
When the backup reviewer runs tomorrow, the useful record is quite ordinary: where it started, how it signed in, what the whole investigation spent and whether the responder received a usable bundle. The October update adds a way to fund that work, not a blanket requirement to abandon subscription access. Following the job all the way to the responder explains both the charge and what the team got for it.
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