Mirza Iqbal Posted on May 30 16 days until Anthropic's Agent SDK billing splits. # claudecode # ai # llmops # enterprise What enterprise teams should do now? [2026-05-30] claude -p workflows still covered by Pro subscription [2026-06-15] claude -p workflows bill against Agent SDK credits [delta] 16 days. enterprise exposure unknown. Enter fullscreen mode Exit fullscreen mode Sixteen days from now, Anthropic flips a billing switch. Pro and Max subscriptions continue to cover interactive Claude Code sessions. Headless invocations ( claude -p , claude --print ) move to Agent SDK billing. Per-call cost, not subscription. Most enterprise teams running Claude Code in production have at least one cron, nightly batch, or pre-commit pipeline that invokes claude headlessly. Most have not run the audit. This is the article I want enterprise CTOs and Heads of Automation to read in the next 16 days. What actually breaks Five workflow patterns flip from "covered by subscription" to "billed per call" on 15 June. A nightly automation that summarizes yesterday's tickets. The cron invokes claude with a prompt. Free today. Per-call after the split. A pre-commit hook that runs claude on the staged diff. Same pattern. A scheduled report generator that runs claude across a queue of inputs. Same pattern. A CI step that asks claude to review a PR or generate a release note. Same pattern. An autonomous agent that wakes itself on a schedule via a shell wrapper. Same pattern. What these share is the claude -p or claude --print invocation. Anything that runs headless, not interactive. What does NOT break. Interactive Claude Code sessions a human opens. The Agent tool dispatching parallel subagents WITHIN an interactive session. claude agents background sessions started from an active parent session. Anything that runs under your active OAuth token in a foreground REPL. The distinction is the auth path. OAuth keeps Pro and Max coverage for interactive use. Agent SDK credits cover headless w
LIVE