Agent Identity: Why AI Agents Shouldn’t Share a Service Account

Agent Identity

Most teams authenticate AI agents the way they authenticate cron jobs: one API key, one service account, shared by everything that calls the CRM. That works on launch day. It fails the first time someone asks which agent did something, for whom, and with what authority.

This article covers what agent identity refers to, why a shared credential erases the answer, and what a workable design looks like.

Key takeaways
  • A shared service account records which credential acted, not which agent. Four agents on one credential look identical in the logs.
  • “Agent identity” spans layers: workload identity, OAuth client identity, cryptographic proof, and delegated user authority. Say which one you mean.
  • Agent identity and user identity answer different questions. Merging them gives you an agent that is the user, or one nobody can attribute.
  • Short-lived, audience-bound, scoped credentials shrink a stolen token’s window and reach. They do not stop theft or in-scope misuse.
  • Delegation keeps the agent’s identity apart from the user’s. Impersonation erases it (RFC 8693).
  • Identity complements prompt-injection defenses and sandboxing. It limits and explains damage. It does not prevent manipulation.

Quick Navigation


The Audit Log That Tells You Almost Nothing

Start with a hypothetical. This is not a real incident.

A company runs four agents: support, finance, sales and engineering. All four authenticate as agent-prod-service-account. A support ticket arrives with hidden instructions, and the support agent is talked into exporting a customer list. The security team pulls the logs:

09:14:07Z  principal=agent-prod-service-account  action=crm.contacts.export    result=allowed
09:14:09Z  principal=agent-prod-service-account  action=storage.objects.create result=allowed

The logs say which credential acted. They do not say which agent, which user’s request triggered it, or what that agent was meant to be allowed to do. Answering any of that means reconstructing intent from application logs, if they exist.

Google Cloud’s guidance notes that audit logs name the service account but not the application using it, so activity behind a shared account may not trace to the right application. The joint CISA, NSA and partner guidance (May 2026) warns that static credentials shared across agents are easy to steal, and that actions under a trusted agent identity produce logs that look legitimate.

“service-account-1 accessed the CRM” is not a finding. It is the start of an investigation with no leads.

What Agent Identity Actually Means

Agent identity is the mechanism used to distinguish one autonomous software workload from another for authentication, authorization, and auditing.

The phrase covers several things, and teams talk past each other when they don’t say which:

  1. A workload identity for the agent’s runtime: a Kubernetes ServiceAccount, cloud IAM role or SPIFFE ID. Which running workload is this?
  2. An application (client) identity, such as an OAuth client registered with an authorization server. Which application is requesting tokens?
  3. A cryptographic identity: a certificate or key the workload uses to prove it holds the identity it claims.
  4. A delegated identity representing a user: authority a person granted the agent. Strictly, this is what the agent may do for someone, not the agent’s own identity.
  5. A combination, which is what most deployments need.

Terms worth keeping apart:

TermMeaningNot the same as
Service accountA non-human principal in an IAM systemAn API key, which is a static secret
DelegationThe agent acts for a user and keeps its own identityImpersonation, where it acts as the user

OAuth defines how clients obtain tokens. It does not give an AI agent its own client registration, and no token is an agent identity by itself. Service accounts are not inherently insecure either. The trouble is sharing them, giving them long-lived keys, and over-granting.

Authentication answers “who are you?” Authorization answers “what are you allowed to do?” Auditability answers “what happened, and under whose authority?”

Agents need all three. A name in a config file proves nothing, so authentication needs proof. Behavior isn’t fixed by code, so authorization must be enforced outside the model. Actions fan out across tools and sub-agents, so the audit record must carry user, agent and authority.

Why Agent Identity Breaks the Old Backend Model

A traditional backend is deterministic where access control cares: its code fixes the calls it can make. A reviewer can read the source, list the APIs, and write a matching permission set.

An agentic workload breaks that link. The model picks tools at runtime from its context, and that context can include untrusted text: tickets, emails, web pages, tool output. The same binary and credential can make different calls depending on what it reads. That is an architectural property, not a claim about intent.

More differences compound it:

  • Asynchronous and event-driven work runs after the human leaves, or with no human at all.
  • Delegation chains form as agents hand work to sub-agents and tools, which the CISA-led guidance says operators may not see.
  • Stale decisions accumulate when permissions are checked once at startup, leaving an old “allow” an attacker can reuse.

The OpenID Foundation’s October 2025 whitepaper, Identity Management for Agentic AI, argues that enterprises should treat agents as first-class citizens in their identity systems, and lists workload differentiation and delegated authority among the open questions. NIST’s NCCoE raised related questions in a February 2026 concept paper. It proposes a possible project. It is not a standard.

Agent Identity Is Not User Identity

Five questions are in play when an agent calls an API, and each can have a different answer:

  • Who is the human? The user whose request or consent started the work.
  • Which agent is acting? The distinct software actor.
  • What runtime executes it? The service, version and instance.
  • What resource is accessed? The API or data targeted.
  • Who authorized the action? The grant or policy that allowed it.

A shared credential typically answers at most one. Collapse them and you lose boundaries.

Borrow the user’s token and you get impersonation: the agent inherits everything the user can do, and the user’s history fills with actions they never took. Use a shared service account and the API sees neither user nor agent. Give the agent its own identity but ignore the user, and it may read data the requester was never cleared for. That is the confused deputy problem, which the CISA-led guidance gives as an example of privilege risk.

Separate identities let you limit or revoke the agent without touching the human, and tell you afterward whose authority an action rode on.

How Agent Identity Changes the Audit Trail

Here are the weak and stronger patterns:

Weak:      User → Agent → Shared Service Account → API
Stronger:  User → Delegated Authorization → Specific Agent Identity → Scoped Token → API

Don’t treat the second line as the one correct flow. Some systems use OAuth token exchange, others workload identity federation or a credential-minting gateway. The principle is what matters: the authorization decision should preserve enough identity context to answer who initiated the action, which agent executed it, and what authority was granted.

Illustrative log lines, not from a real system:

Weak:
principal=agent-prod-service-account  action=crm.contacts.export  result=allowed

Stronger:
subject=user:a.rao  actor=agent:support-triage  runtime=pod/support-triage-7f9c
audience=crm-api  scope="tickets:read tickets:update"
action=crm.contacts.export  result=denied  reason=scope_not_granted

Here the injected export may simply have been denied, because the support agent’s grant never included it. Had it succeeded, the log would still name the agent, the user and the grant. That is the gap between an incident you scope from the log and one you reconstruct from guesses.

Short-Lived Credentials and Scoped Tokens

Long-lived API keys fail predictably. They get pasted into configs, CI variables and tool definitions. Anyone holding a bearer credential can use it, and rotation is painful enough to be skipped. Google adds the audit angle: when a service account key authenticates, there is no reliable way to tell who used it.

Short-lived, scoped credentials change that:

  • Expiration shortens the window for a stolen token.
  • Scope limits the token to the operations the task needs, like tickets:read.
  • Audience limits it to a named resource server. RFC 9700, the OAuth security best current practice, treats audience-restricted tokens as a defense against stolen-token misuse. The MCP authorization specification builds on RFC 8707 resource indicators and forbids token passthrough.
  • Sender constraint (mutual TLS, DPoP) binds a token to a key, so a copy is useless alone.
  • Rotation versus revocation: rotation replaces credentials on a schedule, revocation kills one now. RFC 8693 says propagating revocation across exchanged tokens is implementation-specific, so short lifetimes are your backstop.

Platforms lean this way. AWS recommends temporary credentials via IAM roles over long-term keys. Kubernetes projected tokens are time-bound, audience-bound and kubelet-rotated.

But a ten-minute token is plenty for an automated export, a compromised agent can request fresh ones, and an injected agent uses its legitimate credentials inside its granted scope. Short-lived credentials reduce exposure. They don’t remove the compromise.

Delegation: Acting on Behalf of a User

There is a real difference between “the agent is the user” and “the agent is acting on behalf of the user.”

RFC 8693 names both. Under impersonation, the acting party holds all the user’s rights in some context and is indistinguishable from them. Under delegation, the agent keeps its own identity, the user hands over some rights, and actions are understood as the agent representing the user. In token terms the user is the subject, the agent appears in an act claim, and a may_act claim states who may act for whom. The authorization server decides by policy whether to issue such a token.

Take a finance employee who asks an expense agent for approved expense reports. The agent shouldn’t inherit everything the employee can reach, which may include payroll exports and cloud consoles. The authorization should capture:

  • Who: the employee, as subject.
  • Which agent: the expense agent, as actor.
  • Which resource: the expense API, as audience.
  • Operation and scope: read approved reports for that cost center, for this task.

Teams usually aim for the overlap of what the user may do and what the agent is meant to do. Delegation doesn’t compute that for you. Policy does.

Two caveats. RFC 8693 says only top-level claims and the current actor count in access decisions, and earlier actors in a nested act chain are informational. And support varies: Microsoft documents an on-behalf-of flow for Entra Agent ID, and Google Cloud Agent Identity supports user-delegated OAuth, but those are vendor implementations.

What a Stolen Agent Credential Can Reach

Take the shared agent-prod-service-account. These examples are illustrative.

Agent Identity
Before: shared credentialAfter: distinct identities
Reach if the support agent’s credential is stolenCRM, email, database, internal APIs, storage, cloud resourcesOnly what the support agent was granted
Support agent canEverything the account canRead tickets; update ticket status
Support agent cannotNothing is structurally blockedAccess payroll; modify cloud infrastructure; read customer payment credentials
Finance agentSame as aboveCan read approved financial records; cannot modify engineering infrastructure
ContainmentDisable the account and every agent stopsDisable one identity; the others keep running

Why is “before” so wide? Shared accounts drift toward the union of every agent’s needs, and Google observes they keep gaining access as applications diverge.

Separate credentials don’t create least privilege on their own. Copy an overbroad role onto four identities and you have four overbroad agents. Identity gives you the unit to attach narrow grants to and the attribution to prove they held. The policy work remains. The CISA-led guidance also flags lateral movement across poorly segmented environments, so a narrow identity inside a flat network is no fix.

Agent Identity Is One Layer, Not the Whole Defense

Three controls get conflated, and they do different jobs:

None replaces the others. Identity doesn’t stop injection: a manipulated agent still acts inside its grants. A sandbox can’t tell a legitimate call from a malicious one carrying a valid credential. And identity weakens if the sandbox leaks the credential. On Google Cloud VMs, any code on the machine can by default request tokens for the attached service account from the metadata server.

That is defense in depth, which the CISA-led guidance asks for. OWASP’s agentic Top 10 lists identity and privilege abuse (ASI03) separately from goal hijacking. For tooling choices, see our review guide to ten agent frameworks.

The Agent Identity Architecture Teams Should Aim For

No single product defines this, but the shape is consistent.

Each hop should log, where supported: user, agent, session or request ID, resource, action, authorization scope, timestamp and outcome. The CISA-led guidance adds a central policy decision point on every request, a trusted registry of agents, and fresh cryptographic proof before privileged calls.

The right build depends on your stack:

PatternStrengthTradeoff
IAM role or service account per agentNative policy and logsPer deployment; doesn’t separate users or sessions
Kubernetes ServiceAccount per agentBound, expiring tokensAgents sharing one ServiceAccount share an identity
SPIFFE / SPIREAttested, short-lived, cross-platformGives authentication, not authorization; more to run
OAuth client plus token exchangeExpresses delegationNeeds authorization server support
Vendor agent-identity servicesIntegrated governanceNot portable

Microsoft’s Entra Agent ID guidance recommends a unique identity per agent instance under a blueprint that holds the credential, with a named sponsor. Disabling a blueprint blocks all its identities, which is useful and coarse. Google’s Agent Identity gives each agent a SPIFFE-based principal with certificate-bound tokens.

A Checklist for Agent Identity You Can Apply This Week

Identity

  • List every independently acting agent, including sub-agents and scheduled jobs. Does each have its own identity?
  • Pull yesterday’s logs. Can you tell agents apart by principal alone?

Credentials

  • Search repos, CI variables and configs for long-lived shared keys.
  • Swap in short-lived, audience-bound credentials where the platform allows.

Authorization

  • Compare each agent’s needs with what it can do today.
  • Evaluate user and agent permissions separately, on every request.

Delegation

  • Name the human behind one recent action.
  • Record “on behalf of” as subject plus actor, not a reused user token.

Auditability

  • Reconstruct one action: initiator, executing agent, permission used, resource touched.

Incident response

  • In staging, revoke one agent’s credential. Do the others keep working?
  • Rotate one credential alone, and time it.
  • Give each agent a named owner.

If you do only two, do the log test and the revocation test. They show quickly whether you have agent identity or a shared account with extra names.

FAQ

What is agent identity?

Agent identity is the mechanism used to distinguish one autonomous software workload from another for authentication, authorization, and auditing. In practice it combines a workload or client identity, cryptographic proof and, where relevant, delegated user authority.

Why shouldn’t AI agents share a service account?

A shared account hides which agent acted, merges every agent’s permissions, and means containing one agent disables all of them. Distinct identities restore attribution, narrow grants and per-agent revocation.

Should every AI agent have its own service account?

Not necessarily. Each independently acting agent should be attributable and hold only the authority it needs, whether through a service account, Kubernetes ServiceAccount, OAuth client, SPIFFE ID or vendor agent identity.

What is the difference between agent identity and user identity?

User identity says which human is involved. Agent identity says which software actor is acting. Delegation links them, so the agent acts for the user while keeping its own identity.

What are short-lived credentials for AI agents?

Credentials that expire quickly, often in minutes to hours, with narrow scope and audience. They shorten a stolen credential’s useful life but don’t prevent theft.

How does delegated authorization work for AI agents?

A user grants an agent limited authority. With OAuth token exchange (RFC 8693), the token can name the user as subject and the agent as actor. Support depends on your authorization server.

Does agent identity prevent prompt injection?

No. It limits and explains what a manipulated agent can do. Pair it with injection defenses and sandboxing.

How can organizations audit AI agent actions?

Record user, agent, request, resource, action, scope, timestamp and outcome for each call, alert on identity and privilege changes, and test by reconstructing a past action.


Keep reading

AGI vs superintelligence

AGI vs Superintelligence: A New Name Isn’t a New Intelligence

Facts checked against official documents and reporting on 18 November 2026. On 29 September, the White House told federal agencies to stop writing “artificial intelligence” …
AI Coding Agent

AI Coding Agents Are Getting Expensive. Who’s Paying for the Tokens?

Pricing checked on official vendor pages on 17 November 2026. All USD. Cost scenarios are illustrative and labelled as such. On 28 October, TechCrunch published …
Model Weights

Verify Model Weights: 7 Checks Before You Download

Checked against the burner22/numbat repository and its discussions, Hugging Face and PyTorch documentation, and Moonshot AI’s announcement on 2 November 2026. On 1 November, a …
Agentic AI Statistics

30 Agentic AI Statistics for 2026: Adoption, Spending and Risk

Last updated: 15 November 2026. This page is updated monthly; each figure keeps its original publication date. Agent traffic at one healthcare booking platform rose …

Anthropic’s $518B Compute Commitment: The Obligation Behind It

Anthropic compute commitments

The number everyone repeated last week was $518 billion. The number that actually matters is 80%.

That is the share of Anthropic’s future compute and infrastructure commitments described as non-cancelable or payable regardless of usage, according to a confidential IPO prospectus reviewed by Reuters. Strip out the second number and the first is just a large purchase order from a company that needs a lot of chips. Keep it, and the commitment changes category: from a plan to spend into an obligation to pay.

Those are different things, and the difference is the whole story.

Having access to compute solves what has been the binding constraint on frontier AI development for three years. Being contractually obligated to pay for compute, on a schedule set in advance, converts a supply problem into a utilisation problem — and utilisation is something a company controls only partly, because it depends on customers showing up on the timetable the contracts assumed.

Key takeaways
  • A confidential IPO prospectus reviewed by Reuters shows Anthropic committed to at least $518 billion over roughly a decade across six infrastructure partners, with about 80% non-cancelable or payable regardless of usage.
  • The largest reported components: approximately $161.2bn in Broadcom-related equipment leases, $111.1bn with Google, $110bn with Amazon, $31.4bn with Microsoft, about $84.5bn for Nvidia-based capacity and about $20bn with AMD.
  • The commitments are not uniform. Reporting describes shortfall payments for Google and Amazon, cancellation only on uncured material breach for Microsoft, and leases cancelable only on default for Broadcom. One percentage covers four different contract types.
  • Anthropic spent $7.33 billion on compute and infrastructure in 2025 — more than half of $12.65 billion in total operating expenses — against revenue of $4.59 billion and $20.28 billion of cash and short-term investments.
  • Broadcom has reportedly agreed to lend up to $42 billion through a convertible note that could fund about a third of a five-year, $125.2 billion TPU lease, making one company supplier, lessor and lender at once.
  • Long-term commitments buy capacity certainty in a market where capacity has been the constraint. The cost of that certainty is financial rigidity if demand arrives later or smaller than contracted.
  • The exact terms remain unverifiable while the prospectus is confidential. That uncertainty is part of the story, not a gap in it.

Quick Navigation


What the $518 Billion Actually Represents

Anthropic’s compute commitments are contractual obligations to buy cloud services, computing capacity and AI infrastructure from named partners over a defined period. They are not a debt balance, not a cash payment, and not a single contract.

The reported breakdown, all from the prospectus as described by Reuters:

PartnerReported amountWhat it coversPeriod
Broadcom~$161.2bnEquipment lease obligations, largely non-cancelableIncludes a five-year TPU capacity lease of $125.2bn
Google~$111.1bnInfrastructure servicesApril 2026 – July 2033
Amazon$110bnInfrastructure servicesMay 2026 – April 2036
Nvidia-based capacity~$84.5bnCompute capacityThrough 2029
Microsoft$31.4bnInfrastructure servicesNovember 2026 – May 2033
AMD~$20bnAI computeNot reported

Those six figures sum to roughly $518 billion, which matches the headline. Note the composition: the single largest line is not a cloud contract at all but equipment leases, which behave differently from service agreements in both accounting and cancellation terms.

Three distinctions matter before anyone compares this to a balance sheet.

  1. Commitment is not cash. A ten-year obligation is paid over ten years. Spread evenly — which it will not be, since these ramp — $518 billion is roughly $50 billion a year, against the $7.33 billion Anthropic actually spent on compute and infrastructure in 2025.
  2. Commitment is not debt. It does not sit on the balance sheet as borrowing, though lease obligations are capitalised under current accounting. It is a future purchase obligation, disclosed in the commitments note rather than counted as leverage.
  3. The period is long and the ramp is steep. Contracts running to 2033, 2036 and beyond assume a company much larger than today’s. Reuters reported an annualised revenue run rate above $65 billion by the end of July and earlier reporting put Anthropic’s own 2028 revenue projection at roughly $190–200 billion. Those projections are the company’s, not forecasts anyone has validated.

The useful comparison is not $518 billion against $4.59 billion of 2025 revenue — that ratio is dramatic and tells you almost nothing. It is annual contracted spend against annual revenue in each future year, which is where the question of whether the commitments are comfortable or binding actually gets settled.

The Obligation Hidden Inside the Headline

The 80% figure is a summary statistic covering several different contractual mechanisms, and the mechanisms matter more than the average.

From the reporting:

  • Google and Amazon: Anthropic must pay the difference if its actual spending falls short of the minimum commitment. This is a shortfall provision — you can buy less, but you pay the same.
  • Microsoft: the agreement is described as non-cancelable through May 2033 absent an uncured material breach.
  • Broadcom: the equipment leases are largely non-cancelable except after default, and certain payment or performance defaults could make a substantial portion of the lease obligations immediately payable.
  • The Nvidia-based capacity arrangement: described as giving Anthropic more room to retreat than the others.

So “80% non-cancelable” bundles a minimum-volume commitment, a breach-only termination clause, a lease default provision and at least one more flexible arrangement under a single number.

That distinction has a practical consequence. A shortfall provision caps your downside at the committed spend — you lose the optionality, not more. A lease acceleration clause is different in kind: default can pull future payments forward into the present, which turns a long-dated obligation into an immediate one at exactly the moment a company would least be able to meet it.

The prospectus itself flags this. Reporting describes a warning that certain defaults could accelerate a substantial portion of lease obligations while also restricting Anthropic’s ability to draw on the $42 billion Broadcom facility to cover them. A financing facility that becomes unavailable precisely when it is needed is a standard credit structure and a real risk factor.

What cannot be verified: the actual contract language, the ramp schedules, the definitions of “minimum commitment”, any price-adjustment or technology-refresh provisions, and whether the agreements contain renegotiation mechanisms that reporting has not described. The prospectus remains confidential. Anyone asserting precision about these terms is working from the same journalism everyone else is.

Take-or-Pay Changes the Utilisation Equation

Take-or-pay means the buyer pays for a contracted quantity whether or not it takes delivery. The structure comes from energy and shipping, where suppliers build expensive dedicated capacity and need revenue certainty to justify it. It is appearing in AI infrastructure for exactly the same reason: someone has to fund the data centre before the demand shows up.

For the buyer, take-or-pay converts a variable cost into a fixed one. That is the entire economic consequence, and it cuts both ways.

Anthropic compute commitments

Here is what it does to the unit economics. The following is a hypothetical illustration, not a description of any Anthropic contract or price.

Suppose a company commits to $10 billion of compute capacity for a year under a take-or-pay arrangement.

ScenarioCapacity usedCost incurredEffective cost per unit used
Demand as planned100%$10bn1.0x
Demand arrives late70%$10bn1.43x
Demand disappoints50%$10bn2.0x
Usage-based contract, same shortfall50%$5bn1.0x

Under a usage-based contract, a demand shortfall is a revenue problem. Under take-or-pay, the same shortfall is a revenue problem and a margin problem, because the denominator shrinks while the numerator does not.

This is why utilisation stops being an engineering concern and becomes a financial one. When capacity is elastic, running accelerators at 60% is an optimisation question — you are leaving efficiency on the table. When capacity is committed and paid for regardless, 60% utilisation means 40% of a contracted dollar produced nothing, and that gap flows directly into gross margin. We worked through the mechanics of where idle capacity comes from in our analysis of accelerator utilisation, and every source of idle time in that piece becomes more expensive under this contract structure.

The pressure this creates is directional and predictable. A company with committed capacity has strong incentives to fill it: push inference volume, expand enterprise contracts, launch workloads that consume compute, price aggressively to drive usage. None of those are irrational responses. They are what the contract structure rewards.

The honest caveat: none of this establishes that Anthropic is underutilising anything. Its reported run-rate growth suggests demand has been the easier half of the equation so far. The point is structural — take-or-pay raises the cost of being wrong about timing, for anyone who signs it.

Why Compute Certainty Can Be Worth Paying For

It would be easy to write this as a cautionary tale. That reading ignores why a competent management team signs these contracts, and the reasons are good ones.

For the past three years, the binding constraint on frontier AI has been access to compute, not demand for it. Accelerators have been allocated rather than sold. Memory has been contracted years ahead. Data-centre power has become a multi-year procurement problem. In that environment, a company without secured capacity does not get to choose how fast it grows.

What a long-term commitment buys:

  • Capacity that exists. Suppliers build against contracted demand. An uncommitted buyer competes for whatever is left.
  • Price certainty in a rising market. If compute costs rise, a fixed contract becomes an asset. The hedge runs both directions.
  • Planning horizon. Model development schedules depend on knowing what hardware will be available and when.
  • Priority on new generations. Being a large committed customer affects allocation when the next accelerator ships short.
  • Scale economics. Volume commitments buy better unit pricing than spot purchasing.

There is also a competitive dimension. If frontier capability tracks compute, then capacity secured is capability secured, and capacity your competitor cannot buy is capability they cannot build. Commitments of this size take supply off the market.

The trade-off is clean enough to state in one sentence: Anthropic has exchanged financial flexibility for compute certainty. Whether that was a good trade depends entirely on which constraint turns out to bind — and that will not be clear for years.

The Partners Behind the Anthropic Compute Commitments

The prospectus, as reported, identifies Amazon, Google and Microsoft as simultaneously investors, customers, cloud providers, distributors and competitors. That is not a conflict the company is hiding; it is one it is disclosing as a risk.

Each role pulls differently. As an investor, a partner benefits from Anthropic’s success. As a supplier, it benefits from Anthropic’s spending. As a distributor, it takes a margin on Anthropic’s models. As a competitor, it builds models that compete with them. The same counterparty occupies all four positions at once.

The Broadcom structure is the sharpest version. Reuters reported on October 1 that Broadcom agreed to lend Anthropic up to $42 billion through a convertible note that could fund roughly a third of the five-year, $125.2 billion TPU compute lease, with Broadcom permitted to designate a financing partner and the debt convertible into Anthropic equity. Anthropic is expected to become the largest customer in Broadcom’s chip design business next year.

So one company supplies the hardware, leases it, lends the money to pay for the lease, and may end up holding equity. The prospectus reportedly flags potential conflicts of interest directly, warning that Broadcom’s decisions on pricing and hardware could affect Anthropic’s ability to procure enough computing infrastructure.

Broadcom’s own public filings describe a structure of this shape without naming a customer. Its 10-Q for the quarter ended August 2, 2026 discloses an “AI XPV platform” launched in June 2026 with an initial $35 billion tranche led by a financial partner, enabling deployment of more than a gigawatt of compute infrastructure for a customer, with Broadcom providing a backstop on that customer’s five-year lease obligations and maximum potential liability of roughly $29 billion. Broadcom does not identify the customer, and no public source establishes that these are the same arrangement.

The economic observation, offered as analysis: vendor financing linked to future demand for the vendor’s own product is not new — it is how equipment vendors have supported large customers for decades, and Nvidia has done versions of it recently. What is different here is the concentration. The same relationship carries supply risk, credit risk and equity exposure, and a stress event in one leg propagates to the others. Rothschild’s Robert Leitao put the market’s version of this concern plainly, questioning whether the revenue base can keep pace with the scale of financing that has been arranged.

Leases, Depreciation and the Technology Risk in a Long Contract

Three concepts get conflated whenever AI infrastructure costs come up, and they are related but not interchangeable.

ConceptWhat it isWhere it shows up
Contractual commitmentA promise to buy capacity or services in future periodsCommitments note; lease liabilities on the balance sheet
DepreciationAllocation of an owned asset’s cost across its useful lifeOperating expenses, for hardware you own
Operating expenseCash cost of running the business in a periodIncome statement

For a company leasing capacity rather than buying accelerators, depreciation largely sits with whoever owns the hardware — but the economics do not disappear. They arrive embedded in the lease rate, because the lessor priced in the asset’s expected useful life when setting it.

That is where the technology risk lives. A five-year lease on a specific accelerator generation assumes that generation stays economically competitive for five years. Hardware improves on a roughly annual cadence now, and what ends an accelerator’s economic life is usually not failure but the arrival of something that does more per watt and holds more memory — the pattern we examined in our piece on AI accelerator depreciation.

Follow that through. If performance per dollar improves sharply in 2029, a lease signed in 2027 at 2027 rates becomes expensive relative to what the market then offers. The capacity still works. It is simply worth less than it costs, and the contract does not care.

This is the structural reason long compute contracts carry risk that long property leases do not. A building is still a building in year seven. An accelerator generation may be two or three generations behind by then, and the memory capacity that made it viable for a given model size may no longer fit the models being served.

The counterweight, in fairness: the TPU capacity in question reportedly starts coming online in 2027 and the lease runs five years from there, which is roughly in line with how hyperscalers depreciate their own fleets. These are not exotic terms. They are standard terms applied at an unusual scale, and the scale is what makes the technology-refresh assumption consequential.

What Could Make the Anthropic Compute Commitments Work

The bull case is not complicated, and it is mostly about one variable arriving on schedule.

If enterprise AI demand grows as projected, contracted capacity gets consumed, and the commitments look like foresight rather than exposure. Reuters reported an annualised revenue run rate above $65 billion by the end of July, against $4.59 billion for full-year 2025. A company growing at that rate does not have a utilisation problem; it has a capacity problem, which is what the contracts solve.

Several things reinforce that outcome:

  • Compute stays scarce. If accelerators, memory and power remain constrained, fixed-price contracts signed earlier look cheap later.
  • Agentic and reasoning workloads consume more per task. Demand per customer rises without needing more customers.
  • Enterprise contracts lengthen. Multi-year customer commitments on the revenue side offset multi-year obligations on the cost side, which is the natural hedge.
  • Scale lowers unit cost. Large committed volumes buy better pricing than anyone purchasing on demand.

The cleanest version of the bull case: the commitments convert an unpredictable supply risk into a predictable cost, in a business where supply has been the thing that limited growth.

What Could Make Them Expensive

The bear case does not require AI demand to collapse. It only requires the economics of compute to move faster than the contracts.

  • Efficiency improves faster than demand grows. Better quantisation, more efficient architectures and cheaper serving reduce compute per unit of output. The same revenue then needs less capacity, and contracted capacity goes unused.
  • Performance per dollar jumps. A new accelerator generation that is substantially more efficient makes older contracted capacity expensive relative to what is available, exactly as described above.
  • Price competition compresses margins. If model API prices keep falling — and they have fallen steeply — revenue per unit of compute falls with them, while the cost per unit is fixed by contract.
  • Demand arrives late rather than never. This is the underrated scenario. Contracts ramp on a schedule. If adoption lands two years behind the schedule, the capacity is paid for during the gap.
  • Customer concentration bites. Reporting indicates two customers supplied nearly a quarter of 2025 revenue. Concentrated revenue against distributed fixed obligations is an asymmetry worth noting.
  • Capital markets tighten. Much of this structure assumes continued access to financing, including the Broadcom facility. The prospectus reportedly warns that certain defaults could both accelerate lease obligations and restrict access to that facility.

None of these is a prediction. They are the variables that would determine whether a commitment of this size reads as strategic or as overextended, and they are the ones worth tracking.

The Valuation Connection

A valuation above $2 trillion — against a self-estimated $965 billion in May — is a statement about future cash flows. Those cash flows depend on revenue growth, gross margin, capital intensity and how much compute each dollar of revenue requires.

What the $518 billion does is make one of those variables visible. Infrastructure spending is normally a forecast assumption that investors argue about. Here, a large portion of it is contracted, dated and disclosed. The spending is no longer a question mark; what remains uncertain is the revenue that has to arrive alongside it.

This is not an argument that the valuation is right or wrong, and this article offers no view on that. The structural observation is narrower: when costs are contractually fixed and revenues are not, the equity absorbs the variance. That is true of any capital-intensive business, and it is unusual to see it at this scale in a company five years old.

The 2025 figures give a sense of the starting point. Revenue of $4.59 billion, operating loss of $8.06 billion, compute and infrastructure spending of $7.33 billion within $12.65 billion of total operating expenses, and $20.28 billion of cash and short-term investments at year end. The headline $42 billion net loss is mostly a non-cash charge of roughly $34 billion tied to the rising estimated value of convertible financing instruments — a number that grows precisely because the company’s valuation grew, and which tells you nothing about operations.

A Note on Governance

Briefly, because it is a separate question from the economics.

Reporting describes a newly created “Founder LLC” comprising Anthropic’s seven co-founders, holding a single Class F share carrying 50.1% of voting power on certain matters including some director elections. The founders direct that share by majority vote. The structure is not permanent: a founder who leaves, dies, sells below a threshold or is removed for cause drops out, and the super-voting class begins to sunset once few enough founders remain.

That is the factual position. Dual-class structures are common in technology listings, and whether this one is appropriate is a judgement for investors rather than for this article. The relevant connection to the rest of the piece is simply that financial scale and governance structure are independent: the commitments would have the same economics under any voting arrangement.

What AI Infrastructure Buyers Should Take From This

Most organisations will never sign a contract with nine zeros. The structural lessons scale down anyway.

  • Know which of your compute spend is committed. Reserved instances, savings plans, minimum commitments and capacity reservations all behave like small take-or-pay contracts. The percentage of your bill that is committed is the percentage where utilisation becomes a margin issue.
  • Model the shortfall, not just the spend. The question is not what the commitment costs. It is what it costs if you use 60% of it.
  • Match contract duration to demand visibility. A three-year commitment against six months of demand visibility is a bet, however good the discount.
  • Price the flexibility you are selling. Vendors discount committed volume because certainty is worth something to them. Work out what it is worth to you before trading it away.
  • Watch counterparty concentration. If the same vendor supplies, finances and distributes, your exposure to them is larger than any single contract suggests.
  • Treat utilisation as a financial metric. Once capacity is committed, the operations team’s efficiency work shows up in gross margin. That changes who should be in the room when it is discussed.

The question this story leaves open is a genuine one. Does committing $518 billion remove Anthropic’s biggest risk — not being able to get compute — or substitute a different one, being obligated to pay for compute whether or not demand arrives on schedule? The answer is that it does both, and which dominates depends on variables that will take years to resolve: utilisation, revenue growth, contract terms nobody outside has seen, compute prices, model efficiency and how quickly hardware generations turn over.

Anyone offering a confident verdict today is working from the same confidential document nobody has read.

FAQ

What are Anthropic’s compute commitments?

Contractual obligations to purchase cloud services, computing capacity and AI infrastructure from named partners over fixed periods. According to a confidential IPO prospectus reviewed by Reuters, they total at least $518 billion over roughly a decade across six partners.

What is the $518 billion figure?

The sum of Anthropic’s disclosed infrastructure commitments: approximately $161.2bn in Broadcom-related equipment leases, $111.1bn with Google, $110bn with Amazon, about $84.5bn for Nvidia-based capacity, $31.4bn with Microsoft and about $20bn with AMD. It is a multi-year obligation, not a current debt or a cash payment.

What does take-or-pay mean here?

That the buyer pays for contracted capacity whether or not it is used. Reuters reported that about 80% of Anthropic’s commitments are non-cancelable or payable regardless of usage, though the specific mechanisms differ by counterparty.

What happens if Anthropic does not use the contracted compute?

Based on the reported terms, it would still owe the money in most cases — through shortfall payments to Google and Amazon, or through lease obligations to Broadcom. The exact provisions cannot be verified while the prospectus stays confidential.

Why would a company commit so much compute?

Because compute availability, not demand, has been the binding constraint on frontier AI development. Long-term commitments secure capacity, lock in pricing, support planning and give priority on new hardware generations — at the cost of financial flexibility.

Who provides Anthropic’s compute?

Six partners per the reported prospectus: Broadcom, Google, Amazon, a provider of Nvidia-based capacity, Microsoft and AMD. Amazon, Google and Microsoft are described as simultaneously investors, customers, cloud providers, distributors and competitors.

What is the Broadcom financing arrangement?

Reuters reported that Broadcom agreed to lend Anthropic up to $42 billion via a convertible note that could fund roughly a third of a five-year, $125.2 billion TPU compute lease. Broadcom may designate a financing partner, and the debt could convert into Anthropic equity.

How do compute commitments affect AI company economics?

They convert a variable cost into a fixed one. That reduces supply risk and increases operating leverage: if capacity is fully used, unit economics improve with scale; if it is not, the unused portion still has to be paid for and effective cost per unit rises.


Keep reading

AGI vs superintelligence

AGI vs Superintelligence: A New Name Isn’t a New Intelligence

Facts checked against official documents and reporting on 18 November 2026. On 29 September, the White House told federal agencies to stop writing “artificial intelligence” …
AI Coding Agent

AI Coding Agents Are Getting Expensive. Who’s Paying for the Tokens?

Pricing checked on official vendor pages on 17 November 2026. All USD. Cost scenarios are illustrative and labelled as such. On 28 October, TechCrunch published …
Model Weights

Verify Model Weights: 7 Checks Before You Download

Checked against the burner22/numbat repository and its discussions, Hugging Face and PyTorch documentation, and Moonshot AI’s announcement on 2 November 2026. On 1 November, a …
Agentic AI Statistics

30 Agentic AI Statistics for 2026: Adoption, Spending and Risk

Last updated: 15 November 2026. This page is updated monthly; each figure keeps its original publication date. Agent traffic at one healthcare booking platform rose …