Claude Enterprise pricing: seats plus usage

Claude Enterprise is a seat fee plus usage: $20 a seat a month, billed annually, 20 seats at least, and every token on top at API rates. That is the whole public price. The usage line is the part Anthropic cannot print for you, and the part you can measure before you sign: what a merged pull request costs at list price on the machines your developers already use.

What Anthropic publishes about Claude Enterprise pricing

From claude.com/pricing and the Enterprise page, read on 29 October 2026:

• The seat. "US$20/seat/month, billed annually, 20 seat minimum." Annual commitment required; prices exclude tax; "price and plans are subject to change at Anthropic's discretion."
• Usage. "Usage is billed as you go at API rates, based on what your team uses." The pricing page adds that "usage cost scales with model and task" and prints no rate of its own: the rate is the API price list.
• What a seat covers. Claude in the apps, Claude Code and Cowork, "all three are included in every Enterprise plan". The help centre: "Claude Code is included with the single Enterprise seat on new and self-serve plans", in the terminal and in the IDE alike.
• One seat type. Usage-based plans have one seat, assigned to one named person. Standard, Premium, Chat, Chat + Claude Code are legacy seat types "no longer available for new Enterprise contracts"; an organization on them moves to the single seat at its next renewal.
• No per-seat allowance. On the usage-based plan "there are no per-seat usage limits — usage is based on consumption and billed at API rates." The ceiling is the spend limit an admin sets at the organization, group or individual level, and the consumption guide is blunt about the default: "No limit anywhere = no limit."
• Two ways to buy. Self-serve by card or ACH, or sales-assisted with invoice billing. AWS Marketplace, consultation, trials, tiered incentives on committed spend are listed for the sales-assisted plan only.
• No monthly API credits. The Team plan's pooled API credits stop at Team: "Free, Pro, and Enterprise plans aren't eligible."

Claude Enterprise on AWS Marketplace

The listing Claude Enterprise, sold by Anthropic, is the one place the plan has a public contract price:

$4,800

"20 Claude Enterprise Seats for One Year"

$0.01

a unit of usage, "based on Anthropic API rates"

The seat comes to $20 a month, the same as buying direct; an added seat is billed at $0.65753424 a day for the rest of the term, which is $20 a month over a year. Spend "draws down directly from your EDP or PPA commitment"; any other price is a private offer. A seat there "is one employee's access to the Claude Enterprise apps, including Claude Chat, Claude Code, and Claude Cowork."

The price has moved once already. The launch post of 15 July 2025 listed Claude Enterprise at "$40 per user per month, 25 seat minimum". Read the listing on the day you buy.

What is "contact sales" and not public

Three things you will be asked to call about. Each was looked for on the pages above on 29 October 2026 and is not there:

• A discount on usage. The pricing page names "tiered incentives on committed spend" for the sales-assisted plan and gives no tier, no threshold and no rate. Until you hold a quote, the usage line is the API price list.
• A per-user budget. Claude Code's cost docs say the Enterprise consumption guide "gives per-user dollar starting points for budgeting". The guide, read the same day, does not: it tells admins to "define consumption tiers based on role type before rollout" and to "start conservatively", and its only dollar figures are a worked example of what a skill is worth.
• Trial, invoice and support terms. "Trials", "consultation" and "customer success support at certain spend thresholds" are listed for the sales-assisted plan with no length, threshold or scope.

One thing Anthropic's two sources say differently. The Claude Code cost page says that "on Teams and Enterprise plans, usage draws from each member's seat allowance" and that "usage inside the seat allowance isn't metered in dollars"; the help centre calls that the legacy seat-based plan, and says the current seat has no allowance at all. If your contract predates the single seat, ask which model you are on before you size anything.

Claude Team vs Enterprise vs the API

• Team fits 2 to 150 people who want one bill and no usage line: the seat allowance is the ceiling, and usage credits past it are a switch an Owner turns on and caps. Who should pick it: a team whose heaviest user would still rather wait for a reset than be metered. Which seat runs Claude Code, and where its limit sits: Claude Team plan.
• Enterprise adds SCIM, audit logs, the Compliance API, data retention controls and spend limits per organization, group and person, from 20 seats. Who should pick it: a company that needs those controls, or one whose coding use would blow through Team's allowances every week.
• The API, Bedrock or Vertex has no seat at all; the cap is a Console workspace limit or your cloud budget, and on Bedrock Anthropic's dashboards do not see the use. Who should pick it: a team already on keys or on a cloud commitment that wants no second contract.

Claude Enterprise cost per user: size it from cost per merged pull request

The usage line is the one no page can give you, and the one you can measure. Usage-based Enterprise bills at API rates; so does an API key. Price the work your developers already do at API list rates, by the unit you ship, and you have the figure before the first invoice.

On my machine, Caprock priced every Claude Code session at API list rates and joined it to the pull request it produced. Thirty days to 28 October 2026, read from that database the same day:

$5,699 / 722

= $7.89 a merged pull request, dspv/caprock

$589 / 194

= $3.04 a merged pull request, cybrixcc/caprock-web

The same thirty days came to $7,409 at list price, every project included. That is what a usage-metered plan would have billed for me at list rates, before any discount: one developer's reading, not a typical one. Anthropic's own average across enterprise deployments is about $13 per developer per active day and $150–250 a month, with 90% of users under $30 a day.

The sizing, in three steps:

• Count merged pull requests a month, per repository. GitHub has that figure already.
• Measure what one costs at list rates on a few developers' machines, per repository, for a month. Repositories differ: the two above are 2.6× apart, and a long test suite or a large context is the usual reason.
• Multiply, then add the seats. 20 seats × $20 is $400 a month; my usage line was $7,409. For a developer who works in Claude Code all day, the seat is the small line.

What that figure is not:

• Not a bill. List rates, before any committed-spend incentive, and an estimate, as Claude Code's own /usage is. Claude Code can show contracted rates through the modelPricing managed setting; Caprock shows list.
• Not Bedrock's price. Caprock records a Bedrock session and prices it at Anthropic's first-party list, not at Bedrock's own Claude prices. The difference is a known gap, kept open in the risk register until a team asks for it.
• Not the whole pool. Chat and Cowork draw from the same consumption pool as Claude Code. Caprock prices coding sessions on the machine; a chat in the browser is not on it.

Anthropic billing across a team: where the figures come from

Caprock for Teams keeps the ledger across seats, API keys and Bedrock: every coding agent on every machine, each session priced the same way at list price, summed per repository, pull request and release, on a server you run. That is the usage line by work unit, whichever route paid for it, and the figure to put beside the quote.

Buying Caprock has its own Enterprise row and an AWS Marketplace private offer, the route an Enterprise buyer already knows.

For one developer's plan, Claude Code pricing has every plan and the API rates. What Anthropic's own Enterprise dashboard shows, and what none of the vendor surfaces answer: Claude Code analytics. Allocating the usage line by repository, reporting it beside the invoice and capping the loop, in the FinOps Foundation's words: FinOps for coding agents.