Anthropic shifts programmatic Claude traffic to a separate paid API-style credit on June 15

Anthropic will separate programmatic Claude traffic from its subsidized subscription quota on June 15, routing SDK, command — line and third — party Agent SDK calls to a distinct monthly programmatic credit that is billed at full API rates. This matters because programmatic calls that once drew on subscription allowances will now be metered against a separate pool, potentially raising costs for heavy users of integrations and automation.

The new programmatic credit explicitly covers Claude Agent SDK integrations, the claude -p command — line tool, Claude Code GitHub Actions and any third — party apps built on the Agent SDK. Subscribers are scheduled to receive an activation email on June 8; the included programmatic credit will reset each billing cycle and any unused portion will expire at the cycle’s end. Anthropic says the change responds to disproportionate resource consumption from third — party integrations under a flat-rate model. Tools such as Conductor and OpenClaw produced spikes in programmatic usage that strained shared limits, and the company had previously applied targeted restrictions to address extreme cases before announcing this broader policy.

Allocated credit amounts vary by plan: Pro subscribers receive $20 per month; Max 5x users get $100 and Max 20x users $200. For Team plans the allocation is $20 per seat on Standard and $100 per seat on Premium, while Enterprise allocations differ by seat type. The programmatic credit is described as an add-on and is consumed at Anthropic’s full API rates rather than the subscription’s subsidized interactive rate.

If a subscriber exhausts the included programmatic credit they can continue making calls by enabling Usage Credits, which are billed at standard API prices and can be toggled on or off. If customers turn Usage Credits off, programmatic requests will pause until the next billing cycle when the included credit refreshes.

Anthropic developer Lydia Hallie framed the shift visually on X and cautioned "you don't pay extra," a claim that reflects the single — credit distribution but overlooks the practical effect: many heavy users of third — party apps will likely see higher costs because programmatic calls are no longer subsidized. Builders relying on Agent SDK integrations should monitor programmatic consumption, estimate API pricing for expected volumes, and decide whether to enable Usage Credits before the June 15 change.