Claude Agent SDK Billing Separation June 15 | Impact on Pro/Max Plans and How to Respond

What Changes on June 15, 2026 — The Full Picture of Billing Separation

In mid-May 2026, Anthropic announced through a scoop from The New Stack and a follow-up from VentureBeat its plan to split the usage structure of Claude Pro / Max subscriptions into two layers: one for "interactive use" and one for "agent use." The effective date is June 15, 2026 (this article is based on information as of May 21, 2026).

Until now, the monthly subscriptions — Pro at $20, Max 5x at $100, and Max 20x at $200 — operated on a flat model where all usage paths were covered under a single allowance: claude terminal interactive sessions, Claude.ai, the Agent SDK, claude -p non-interactive mode, and calls through third-party tools. Starting June 15, three of these paths — SDK, non-interactive, and third-party tool usage — will be separated into a dedicated monthly credit allowance that is consumed independently.

As indicated in Anthropic's official newsroom, the motivation behind this change is that large-scale agent usage routed through subscription allowances has grown significantly, putting pressure on the response quality experienced by individual developers using claude interactively. While Anthropic could have expanded GPU supply while maintaining the flat model, the company chose a design that asks heavy agent users to "pay a fair price through a dedicated allowance." The overall Claude pricing structure is summarized in the Complete Guide to Claude Pricing, but understand that starting June 15, the numbers on that page will incorporate the concept of a dedicated credit allowance.

Which Usage Paths Are Affected vs. Unchanged — A 5-Path Comparison Table

Whether your billing path changes after June 15 depends on where you are calling Claude from. The table below organizes the five main usage paths. Take 30 seconds to determine which category your primary usage falls into.

Cross-referencing The New Stack's explanation with Codersera's breakdown, the boundary of billing separation lies in whether a human is interacting interactively at their terminal or whether Claude is being called automatically as an agent. Interactive use continues on the existing allowance, while headless usage such as the Agent SDK or claude -p is routed to the dedicated credit allowance, consuming it separately from the monthly subscription.

There are two things to watch out for. First, classification of third-party tool usage depends on which API the tool is calling internally. VentureBeat's reporting notes that third-party agent usage, including OpenClaw-type tools that were temporarily blocked, was reinstated on the condition that it runs through the subscription but via a dedicated allowance. Claude Code interactive sessions covered in this comprehensive guide fall on the subscription side, but if you are using an IDE extension to automate PR creation, plan your cost estimates assuming that counts toward the dedicated allowance.

Second, it is common to use multiple paths simultaneously. If you interact with Claude.ai during the day and run automated reviews via the Agent SDK overnight, you will be consuming both the subscription allowance and the dedicated credit allowance every month starting June 15.

Monthly Credit Allowances for Pro / Max 5x / Max 20x with Japanese Yen Conversion

The dedicated credit allowance amounts differ by plan. According to Codersera's pricing breakdown and Anthropic Claude Platform Release Notes, the currently published allowances are as follows. Japanese yen conversions use a reference rate of 153 JPY per USD as of May 21, 2026 (subject to exchange rate fluctuations).

This means that starting June 15, if you are on Max 20x and run agent automation to its limit every month, the effective cost ceiling becomes subscription $200 + dedicated credit allowance $200 = $400 per month (approximately 61,200 JPY). Plan details are summarized in the Claude Pro guide and Claude Max guide to help you evaluate whether your current plan is sufficient.

The specific token volumes included in the dedicated allowance (e.g., how many Opus 4.7 calls, how much long-form content through Sonnet 4.6) have not been fully published as of the time of writing in the official Release Notes or the Claude Code official changelog. This is noted as unconfirmed. An official final announcement is likely to arrive just before the effective date, so be sure to check both documents again in early June.

Regarding consumption tax, since Anthropic is a US-based company, Japanese consumption tax does not apply directly. However, depending on the total annual transaction amount, reverse charge treatment may apply. Please consult your company's tax team for accounting treatment (noted as unconfirmed in this article). As for what happens after the monthly credit allowance is exhausted, currently available public information suggests either automatic switching to pay-as-you-go billing or suspension of usage, but whether this is the default behavior or user-configurable remains unconfirmed.

7-Item Practical Checklist to Complete Before June 15

Here is a step-by-step list of what you need to do before the June 15, 2026 effective date. Work through it from top to bottom. The latest technical developments around the Agent SDK are covered in the Claude Agent SDK comprehensive article, so proceed on the technical side in parallel for efficiency.

1. Identify your primary usage paths: Use the 5-path table in Section 2 of this article to categorize how you and your team primarily use Claude. Spend 30 seconds estimating the ratio of Agent SDK / claude -p / third-party tool usage.
2. Estimate usage volume over the past 30 days: Open the usage dashboard in Claude Console and convert your request count and token consumption from late April through late May into a monthly figure. For team shared contracts, aggregate across all members.
3. Estimate monthly costs after June 15: Calculate in three layers for each plan: "subscription + dedicated credit allowance + pay-as-you-go overage." Create a spreadsheet with four scenarios: Pro only, Max 5x only, Max 20x only, and Max 20x with full dedicated allowance consumed.
4. Visualize usage logs for team shared contracts: Set up monitoring to track "who is calling Claude, via which path, and how frequently." Prevent scenarios where one person running full agent automation depletes the entire team's allowance.
5. Revisit cost assumptions for freelance / contract work: If you are passing Claude usage costs as a direct cost in active client projects, update your estimates to reflect the post-June-15 billing path. Fixed-fee monthly contracts carry the highest risk of going into the red.
6. Proactively communicate with clients: If the post-June-15 billing impact affects your clients' cost expectations, provide advance notice by late May or early June. Sending an unexpected additional invoice after the effective date is certain to damage relationships.
7. Agree on escalation criteria in advance: Decide in advance with internal decision-makers what to do when the monthly credit allowance is exceeded — "immediate suspension," "continue on pay-as-you-go," or "immediately switch to a higher plan."

Enterprise contract holders will also need to revise their procurement workflows and expense reimbursement processes. Since the monthly credit allowance and pay-as-you-go charges may appear as separate line items on invoices, handle account code mapping in SAP / freee / Money Forward, etc. in advance.

Monthly Cost Estimates by User Type: Individual Developer, SME, and Enterprise

Finally, here are rough monthly cost estimates after June 15 for three typical use cases. Match your own situation to the closest case.

If you are an individual developer primarily using Claude.ai and interactive mode, your situation will not change after June 15 — you will still be running on Pro at $20. On the other hand, if you are supplementing with third-party IDE extensions or coding agents for freelance work, your setup will change to additionally consuming the dedicated credit allowance of $20. Think of it as your monthly Claude-related spending effectively doubling.

Team shared contracts face the greatest impact. A five-person team sharing Max 5x with everyone integrating agent automation into their workflows could see monthly costs jump to around 150,000 JPY. For enterprises, pay-as-you-go overages may stack on top of this, so by early June, make sure to implement both a "monthly budget cap" and a "policy for automatic suspension vs. continuation when the cap is exceeded."

Sources

• The New Stack: Anthropic Agent SDK Credits
• Codersera: Anthropic June 2026 Billing Change Claude Code
• VentureBeat: Anthropic Reinstates OpenClaw and Third-Party Agent Usage on Claude Subscriptions with a Catch
• Anthropic News
• Claude Platform Release Notes
• Claude Code Changelog