Skip to main content
NewsArticle AI Industry News

Anthropic splits Claude Agent SDK and claude -p into separate monthly credits, ending the shared-limit era for programmatic agents

Starting June 15, 2026, Claude Agent SDK usage, claude -p, Claude Code GitHub Actions, and third-party Agent SDK apps move out of normal Claude subscription limits and into separate monthly credits. Pro gets $20, Max 5x $100, Max 20x $200, with usage billed at API-style rates after the credit.

Anthropic splits Claude Agent SDK and claude -p into separate monthly credits, ending the shared-limit era for programmatic agents

Anthropic has drawn a hard line between interactive Claude use and programmatic agent use.

Starting June 15, 2026, usage through the Claude Agent SDK, the claude -p non-interactive command, Claude Code GitHub Actions, and third-party apps built on the Agent SDK no longer draws from normal Claude subscription limits. Eligible paid users instead receive a separate monthly Agent SDK credit that is consumed first, then standard API-rate extra usage if the user has enabled it.

The official support article lists the monthly credits:

PlanAgent SDK monthly credit
Pro$20
Max 5x$100
Max 20x$200
Team Standard seats$20
Team Premium seats$100
Enterprise usage-based$20
Enterprise seat-based Premium seats$200

Seat-based Enterprise Standard users are not eligible for the credit, according to Anthropic. API-key users also do not receive the credit; pay-as-you-go billing continues as before.

What the credit covers

The new bucket applies to:

  • Claude Agent SDK usage in a user’s own Python or TypeScript projects.
  • claude -p in Claude Code non-interactive mode.
  • Claude Code GitHub Actions.
  • Third-party apps that authenticate with a Claude subscription through the Agent SDK.

It does not apply to normal Claude conversations, Claude Cowork, or interactive Claude Code in a terminal or IDE.

Credits are per-user, cannot be pooled across a team, do not roll over, and require a one-time claim. If extra usage is disabled and the monthly credit runs out, Agent SDK requests stop until the credit refreshes.

Why this matters

This is one of the clearest signs yet that flat-rate AI subscriptions are colliding with agent economics.

Human chat sessions are bursty. Programmatic agents are not. They can run in CI, execute repeatedly, call tools, miss cache paths, reprocess context, and burn far more inference than a human typing into a chat window. Anthropic’s old model let some users route heavy external automation through subscription credentials that were priced for human-in-the-loop use.

Anthropic is not removing third-party agent support. In fact, the change restores a more official path for tools such as OpenClaw, Conductor-style harnesses, and custom Agent SDK scripts. But the subsidy is capped. After the included credit, serious automation moves toward API economics.

The user reaction is understandably split. Light users get a clearer legal path to experiment. Heavy users lose the ability to treat a $20-$200 subscription as a broad compute pool for unattended workflows.

Buyer take

For Claude buyers, the practical read is:

  • Interactive Claude Code is still the subscription story. If a human is in the terminal or IDE working with Claude Code, Anthropic says those normal subscription limits continue.
  • Automation now needs a budget. CI runs, claude -p, custom scripts, and third-party agent apps should be treated like cloud spend.
  • Production agents should use API keys. Anthropic explicitly positions the monthly Agent SDK credit as individual experimentation and automation, not pooled production infrastructure.

For OpenClaw users, this is a mixed win. The route is less gray than the April restriction period, but the economics are much less magical. OpenClaw remains free and self-hosted; the model bill is now harder to hide inside a subscription.

For teams, this should trigger a small governance cleanup: identify where claude -p, Claude Code GitHub Actions, Agent SDK scripts, and third-party agent tools are being used; assign cost owners; and decide whether those jobs belong on subscription credits or normal API billing.

What is still unclear

Anthropic has not published a granular calculator that maps typical claude -p jobs to how fast each monthly credit burns. That makes the June 15 change hard to price for teams running real agent workflows.

The other open question is competitive response. OpenAI just put Codex into the ChatGPT mobile app and continues to bundle substantial Codex access into ChatGPT tiers. If OpenAI keeps more agentic work inside flat-rate subscriptions while Anthropic meters programmatic use more aggressively, buyer behavior may shift. If OpenAI follows the same economic path later, this Anthropic move will look less like a one-company backlash and more like the beginning of agent pricing normalizing across the market.

Sources

Primary and corroborating references used for this news item.

5 cited sources
  1. Claude Help Center: Use the Claude Agent SDK with your Claude plan
  2. The Register: Anthropic tosses agents into the API billing pool
  3. VentureBeat: Anthropic reinstates OpenClaw and third-party agent usage on Claude subscriptions
  4. InfoWorld: Anthropic puts Claude agents on a meter across its subscriptions
  5. Techmeme: Anthropic unveils Claude Agent SDK credits for paid plans

Read next

Share LinkedIn
Spotted an error or want to share your experience with Anthropic splits Claude Agent SDK and claude -p into separate monthly credits, ending the shared-limit era for programmatic agents?

Every tool page is re-verified on a recurring cycle, and corrections land faster when readers flag them directly. If you spot a stale fact, a missing capability, or have used Anthropic splits Claude Agent SDK and claude -p into separate monthly credits, ending the shared-limit era for programmatic agents and want to share what worked or didn't, the editorial desk reviews every message sent through this form.

Email editorial@aipedia.wiki