No. There is no permanently free tier for Claude Code. It is included in the Pro, Max, Team and Enterprise subscriptions, or billed per token through the API. New API accounts sometimes receive a small trial credit.

How much does Claude Code cost per month?

Through a subscription: Pro is around 20 US dollars per month, Max around 100 or 200 depending on tier, and Team and Enterprise are priced per seat. Through the API you pay per token, which for a developer using the agent daily typically lands in the tens to low hundreds of dollars per month. Check Anthropic's pricing page for current amounts.

Is Claude Pro enough for Claude Code?

For occasional use, yes. Developers who run the agent for several hours a day regularly hit Pro's usage window and are better served by Max.

Is Claude Code cheaper through the API or a subscription?

For light use the API is cheaper; for heavy daily use a Max subscription usually is. Many companies combine subscriptions for interactive work with API billing for CI and automation.

How do we control Claude Code costs across a team?

Budgets and hard caps per user and team, model policies that default to cheaper models, a forecast to month end, and a log per call. All of that is easiest to enforce in a gateway that every request passes through.

Is Claude Code free? Claude Code pricing and cost control explained

Claude Code has no price of its own. It is a tool that runs on one of Anthropic's subscriptions or on pay-per-token API billing. What you pay therefore depends on which route you choose, which model you use, and how hard the agent works. This guide explains the options, puts the numbers in context, and shows how to keep costs under control across a team. For what Claude Code is, start with the overview.

A note up front: prices change. The figures here are as of September 2026 in US dollars; Anthropic's pricing page has the current amounts and local currency.

The options at a glance

Option	Who it is for	Billing	Claude Code included
Pro	Individuals, occasional use	~20 USD/month	Yes, with a usage window
Max 5x	Developers using it daily	~100 USD/month	Yes, ~5× the Pro allowance
Max 20x	Heavy users, parallel sessions	~200 USD/month	Yes, ~20× the Pro allowance
Team	Small and mid-size teams, central admin	Per seat per month	In the premium seats
Enterprise	Large organisations, SSO, audit, contracts	Custom	Yes
API	CI, custom agents, full control	Per token	Yes, via API key

What "usage allowance" means

Pro and Max do not bill per token. They give you an allowance within rolling time windows. When it is used up, the agent pauses until the next window opens. There are additional weekly caps for very heavy users.

How far the allowance stretches depends on the model and the kind of work. Short, targeted tasks in a small repository use little. Long sessions where the agent reads large files, reruns tests and calls many tools use a lot. Rule of thumb: Pro covers a few hours a day with breaks, Max 5x a full working day, Max 20x parallel sessions or very large codebases.

API billing: what a developer spends

Through the API you pay per input and output token, with different prices per model. Sonnet-class models are considerably cheaper than Opus-class ones, and prompt caching cuts the cost of repeated inputs substantially; Claude Code uses it automatically.

From the rollouts we support, the orders of magnitude are:

Occasional use (a few tasks a week): single to low double digits in dollars per month.
Daily use (several hours): mid double digits to low triple digits.
Heavy use with Opus models and large contexts: several hundred dollars is possible.

The point that surprises finance teams: the spread between developers is wide, and a single session can cost many times the daily average. Without budget limits you find out on the monthly invoice.

Subscription or API?

Subscription when developers use the tool interactively and you want predictable per-head cost. Team and Enterprise add central administration, SSO and the commercial terms under which data is not used for training.

API when Claude Code runs in CI pipelines, automations or your own agents, when you want to choose the backend yourself (an EU region via Bedrock, Vertex AI or Microsoft Foundry), or when you operate a gateway with your own budgets.

Many companies combine the two: subscriptions for interactive use, API for automation.

Controlling cost across a team

Four measures that make the difference in practice:

Budgets and hard caps per user, team and project. Not a report after the fact, but a limit the agent cannot exceed.
Model policies. Not every task needs the most expensive model. A policy that defaults to a cheaper model and unlocks the expensive one on request often halves cost with no noticeable quality loss.
A forecast to month end per model and team, based on actual usage over the last weeks rather than a straight line.
A log per call: who, when, which model, how many tokens, which repository. Without it every cost discussion is a guess.

These four are why companies put a gateway in front of Claude Code. Walma AI Hub enforces budgets and model policy in the gateway, forecasts cost per model to month end, and logs every call, for Claude Code, Codex, Cursor and the approved MCP servers, running in the customer's own Azure tenant in an EU region. There is a cost calculator on the home page; for a concrete scenario, a walkthrough with an engineer is the fastest route.