Claude Enterprise pricing: what a seat costs and what it buys

What a Claude Enterprise seat costs

The number most people are looking for is on the pricing page and easy to miss, because it sits under a heading that describes a formula rather than a price: Seat price + usage at API rates, then $20/seat, then the sentence "Usage cost scales with model and task". Checked on claude.com/pricing in August 2026.

Anthropic also states directly that Claude Code is included with the single Enterprise seat on new and self-serve plans. Older Enterprise contracts are different: there, Claude Code rides on either a Chat + Claude Code seat with usage-based billing or a Premium seat with seat-based billing, so an organization that signed before this simplification should check which seat types its contract actually carries before assuming parity.

What Enterprise adds over Team

Team already covers the things a growing company notices first: central billing, SSO, domain capture, admin controls for connectors, enterprise deployment of the desktop app, and no model training on your content. Enterprise is the layer your security review asks for after that.

Two of those rows carry more weight than the rest for an engineering org. SCIM is the one that turns offboarding from a checklist item into an automatic consequence of the identity provider, which is the difference between a control you claim to have and one that survives a bad week. Managed policy settings is the row that lets you push a Claude Code configuration to every developer machine and have it win over anything they put in their own settings file.

The usage half of the bill

On Enterprise there is no per-seat usage cap to hit. Anthropic’s own guidance for usage-based Enterprise plans is explicit: no per-seat caps, billing follows API consumption. So the seat line is trivially predictable and the usage line is the entire budgeting problem.

Sonnet 5 at $2 and $10 per million is the permanent standard rate; the increase that was once scheduled for September 2026 was cancelled and will not happen. The two rows above it are where an Enterprise bill actually moves: Claude Opus 5 is 2.5x Sonnet and Claude Fable 5 is five times it, so a default that reaches for either is the largest single line on the usage half. Batch processing is half price, and cache reads are a tenth of input, which matters enormously for a coding agent because a Claude Code turn re-sends a large, mostly unchanged context every time.

What that comes to for a real team

Anthropic publishes an outside number worth anchoring on. Across enterprise deployments Claude Code averages roughly $13 per developer per active day and $150 to $250 per developer per month, staying under $30 per active day for 90 percent of users. Put that against the seat lines and the shape of the decision appears.

The corollary is that on Enterprise, spend limits are not a nice-to-have. Set them at the organization level before the first developer signs in, then relax them per group. A cap you can raise in an afternoon costs less than the month where someone leaves an agent team running against a large repo. Agent teams use roughly seven times the tokens of a standard session.

What is still sales-gated

Being candid about the gaps is more useful than filling them with a guess. As of August 2026, here is what Anthropic does and does not publish.

Third-party pricing roundups circulate seat numbers for sales-assisted Enterprise contracts. Treat them the way you would treat a competitor’s reported salary bands: they are a directional prior for a negotiation, not a fact you can put in a budget. Anthropic does not publish those numbers, so nobody outside your own procurement conversation knows what you will pay.

Which plan you actually want

1. Under about ten engineers, and no compliance pressure: Team Standard seats, annual. You get central billing, SSO, offboarding, and a spend report, and the allowance covers ordinary use.
2. Ten to a hundred, agents used daily: a mix of Team Standard and Team Premium seats. Premium is 5x a standard seat, and you can mix seat types in one workspace, so provision by measured usage rather than by title.
3. You need SCIM, audit logs, or a data retention commitment: Enterprise, and budget the usage line properly. This is a controls purchase, and the controls are the thing you are buying.
4. Your heaviest engineers exhaust a Premium seat: Enterprise, or leave those individuals on personal Max 20x, which is still the best allowance per dollar Anthropic sells and has no team equivalent. Naming that trade explicitly is better than absorbing it.
5. You are API-first already: the Claude Console with workspace spend limits gives you metered billing without a seat purchase, at the cost of the claude.ai features that need a subscription login.

Seeing the spend once you are on it

Every plan shape gives you a different answer to "who spent what", and mixed organizations get mixed reporting, because each developer is metered by whichever method they authenticated with.

The Enterprise Analytics API is Enterprise-only and is not available on Teams. A Primary Owner mints the key with the read:analytics scope, and it returns per-user engagement, usage, and cost across Claude surfaces including Claude Code. OpenTelemetry export works on every setup and is the only route that streams per-user token and cost metrics into your own stack in near real time.

Questions people ask

Keep reading

Continue through AI spend and governance with ChatGPT Enterprise pricing: what OpenAI publishes, and what it will not.