Claude Code Using API Credits? Switch to Your Subscription

Verified against Anthropic documentation · July 29, 2026

Claude Code using API credits instead of your Pro or Max subscription usually means the terminal is on a different account or billing route. A Claude paid plan can include Claude Code, but Anthropic Console API billing remains a separate pay-as-you-go system. If Claude Code is connected to Console, you accepted an API-credit option, or an API credential is forcing a different route, terminal activity can consume paid API credits.

The fastest safe fix is to run /status, note the active account and billing method, then use /logout and sign back in with the same Claude.ai account that owns your Pro or Max subscription. When the setup screen asks, choose the Claude App subscription option—not Anthropic Console. Do not delete an API key until you know whether another application depends on it.

Claude Code subscription vs API billing at a glance

Billing route	What pays for usage	Where to check it
Claude App with Pro or Max	Your plan’s included Claude allowance; Claude and Claude Code share the relevant limits	Claude Settings → Usage and `/status` in Claude Code
Anthropic Console	Prepaid API usage credits at standard API rates	Console → Billing and Usage
API credits after a plan limit	Paid credits you explicitly choose to use after included usage is exhausted	The prompt in Claude Code, then Console billing controls
Bedrock, Vertex AI, or a gateway	Your cloud provider or organization’s configured route	Managed settings, environment variables, and the provider’s billing console

These systems can use the same Claude models while charging different balances. A Pro or Max receipt does not automatically turn every API-key request into included subscription usage.

1. Check the current account before changing anything

Start Claude Code and enter:

/status

Use the result to answer three questions:

Is Claude Code signed in with the same email or sign-in method as the paid Claude account?
Does it identify a Claude subscription, a Console account, or an organization-controlled provider?
Are you actually seeing API charges, or only a warning that your included plan limit is nearly exhausted?

Anthropic recommends /status for monitoring the remaining Pro or Max allocation. If the active identity is unfamiliar, do not purchase more credits yet. An account mismatch is more likely than a missing subscription.

2. Switch from Console billing to your Pro or Max plan

Anthropic’s current help instructions say that a user already signed in through Anthropic Console pay-as-you-go can switch to a subscription by running /login. A clean reauthentication is safer when the current route is unclear:

Run /logout inside Claude Code.
Run claude update in your terminal.
Close and restart the terminal so the updated client and environment are loaded.
Start Claude Code again.
Choose the Claude App option for Pro or Max.
Sign in with the same credentials used for the active subscription.
Run /status again and verify the route before starting a large task.

If the paid plan is attached to a Google or Apple sign-in, use that same sign-in method. Two accounts can show the same display name while having different subscriptions and billing histories.

3. Understand the API-credit prompt

Pro and Max have usage limits. Claude chat and Claude Code activity share the relevant subscription allowance, so a long coding session can exhaust capacity even when you sent few messages in the web app.

When included usage is exhausted, Claude Code may offer a way to continue with API credits. Anthropic states that moving to API-credit usage requires the user’s choice. If you want to remain strictly within the subscription budget:

decline the API-credit option;
wait for the displayed usage period to reset;
use /status to monitor remaining capacity;
consider Max only if repeated limits cost more time than the higher recurring price is worth.

Accepting paid overflow does not mean the subscription disappeared. It means the included allowance is unavailable and you chose a separate metered route. Our guide to the Claude five-hour limit, reset times, and credits explains how to distinguish a normal limit from a billing problem.

4. Check Console auto-reload before another charge

Anthropic Console can automatically buy more API credits when the balance falls below a threshold. Auto-reload is managed in Console, not in Claude Code.

If API credit consumption was unintended:

Open the Anthropic Console account shown by Claude Code.
Review Billing and Usage for the dates and organization involved.
Check whether auto-reload is enabled.
Lower the reload amount, set a tighter limit, or disable auto-reload if it is not needed.
Return to Claude Code and authenticate only with the intended Pro or Max account.

Changing auto-reload prevents new automatic purchases; it does not convert earlier API usage into subscription usage. Anthropic says purchased API credits are normally non-refundable and expire one year after purchase, so verify the account and settings before funding a balance.

5. Look for API credentials and organization routing

Claude Code can also be configured with an Anthropic API key, an authentication token, Amazon Bedrock, Google Vertex AI, or an LLM gateway. These are legitimate setups, especially for teams, but they do not use a personal Pro or Max allowance.

Common places to review include:

the current terminal session;
shell startup files;
project-level Claude settings;
user-level Claude settings;
organization-managed settings;
development containers, CI jobs, and editor integrations.

Relevant configuration names can include ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, ANTHROPIC_BASE_URL, or provider-specific Bedrock and Vertex settings. Anthropic documents that API credentials can take precedence in gateway configurations. A project or company policy can also override a personal setting.

Do not paste an API key into a support ticket, forum post, screenshot, or AI chat. If a key was exposed, revoke it in Console and create a replacement for the applications that still require API access.

6. Remove a conflicting credential carefully

If you own the computer and confirm that an old credential is forcing API billing, remove it from the place where it is defined, restart the terminal, and sign in again. The exact method depends on the operating system and shell, so there is no single safe command for every user.

Before removing anything:

record only the variable name and location, never the secret value;
check whether scripts, editors, or local applications use the key;
ask the organization administrator if the setting is managed;
make a reversible backup of the configuration file;
restart the terminal after the change and verify with /status.

If the setting comes from a company-managed policy, a personal logout may not change the route. Contact the administrator responsible for Claude Code access and cost controls.

How to tell whether the fix worked

Use a small test rather than immediately opening a large repository:

Run /status and confirm the intended Claude App account.
Open a small folder with no sensitive files.
Ask one short question about a local text file.
Check Claude Settings → Usage for subscription activity.
Check Console Usage and confirm there is no new API charge from the test.

Usage dashboards may not update at exactly the same second, so allow time for normal reporting delay. The important signal is that the active authentication route is correct and new activity appears in the expected account.

Subscription usage, Claude usage credits, and Console credits are not identical

The names are easy to confuse:

Included Pro or Max usage is part of the recurring Claude subscription.
Paid overflow offered in Claude Code lets you continue after included usage and is billed at API rates when you accept it.
Anthropic Console credits fund API, Workbench, and eligible Claude Code activity through the developer account.

For a broader explanation of overflow, spending limits, and automatic reloads, read Claude usage credits for Pro and Max. If you are deciding whether a larger recurring allowance is better, compare Claude Pro, Max 5x, and Max 20x.

Frequently asked questions

Does Claude Pro include Claude Code?

Yes. Anthropic says Pro and Max subscribers can authenticate Claude Code with their Claude.ai account and use a unified subscription. The applicable limits are shared with Claude.

Why does Console still ask me to buy credits?

Console is the separate developer/API product. A Claude subscription does not include general API calls made through Console credentials.

Can Claude Code switch to API credits automatically?

Anthropic says transitions to API-credit usage require explicit user consent. However, an existing Console login, API key, managed setting, or cloud-provider configuration may mean the session was already using a metered route from the start.

Will logging out cancel my subscription?

No. /logout signs Claude Code out on that device. It does not cancel the Pro or Max plan.

Should I delete every Anthropic API key?

No. API keys may power other tools. First identify the credential actually used by Claude Code, then remove, rotate, or scope it only when you understand the impact.

What if the correct subscription option does not appear?

Run /logout, update Claude Code, restart the terminal, and try again. Verify that the paid plan is active on the same Claude account. If an organization manages the installation, ask its administrator which authentication route is enforced.

Official sources

HiseHub is independent and is not affiliated with Anthropic. Authentication options, limits, and billing behavior can change; the account, usage, and checkout screens shown by Anthropic control.

Regional price check: Compare current Claude Pro App Store prices by country, with local currency, estimated USD values, and official Apple source links.

Claude Code Using API Credits Instead of Your Subscription? Fixes