Definition

Exposures

Foundation Model Liability

The exposure faced by developers of base AI models (OpenAI, Anthropic, Google) and by enterprises that build downstream applications on those models.

Foundation model liability is the legal exposure that attaches to the developers of large general-purpose AI models (OpenAI, Anthropic, Google DeepMind, Meta, Mistral, and similar firms) and, derivatively, to the enterprises that build downstream applications on those models. The liability runs in two directions. Direct claims target the developer for the model's training (copyright infringement claims like Bartz v. Anthropic and Thomson Reuters v. ROSS) and for the model's outputs in deployed contexts the developer controls. Downstream claims target the deployer that put the model into production, with potential indemnification from the developer under enterprise contracts.

The model developer's exposure is concentrated in training-data copyright, model output safety, and regulatory action under emerging frameworks like the EU AI Act. The largest financial events to date have been training-data settlements: Anthropic's $1.5 billion Bartz settlement in 2025 is the bellwether, and similar matters are pending against several other major developers. The developer's insurance program typically includes Directors and Officers, professional liability, IP-specific coverage, and increasingly bespoke wordings for AI-specific exposures that traditional carriers were not built to write.

The deployer's exposure depends on what the deployer did with the model. A SaaS company that exposed a foundation model directly to end users with minimal scaffolding inherits substantial exposure for the model's outputs. An enterprise that fine-tuned a model and embedded it in a regulated workflow takes on additional exposure proportional to the regulatory environment. Vendor indemnifications (Microsoft Copilot Copyright Commitment, Google Cloud Generative AI Indemnification, OpenAI's enterprise indemnity, Anthropic's commercial Claude indemnity for API and Claude for Work or Enterprise customers) cover narrow slices of the deployer's exposure, primarily IP infringement on the specific vendor's service.

Generative AI Liability insurance for deployers fills the gap that contracts and older insurance forms leave open. The policy responds to the deployer's third-party liability across hallucination, IP infringement and personal injury, unauthorized data disclosure, regulatory defense, and narrow bodily injury and property damage agreements. It coordinates with the foundation model vendor's indemnification (and with the deployer's own Cyber and Tech E&O) through an Other Insurance clause rather than replacing those layers.

Also known as

Foundation Model Developer Liability, Base Model Liability, Large Language Model Liability

Frequently asked

Who bears liability when a deployer's product harms a user through OpenAI's API?

Primarily the deployer, with potential contribution from OpenAI under the deployer's vendor contract. The user's claim runs against the deployer because the deployer is the party with whom the user has the contractual or product relationship. OpenAI's enterprise indemnification covers a defined set of IP claims for paid customers using the API within terms; it does not cover hallucination harm, defamation, unauthorized actions, or regulatory matters. The deployer's own insurance program (Cyber, Tech E&O, and a standalone Generative AI Liability policy where placed) is where the exposure ultimately lands.

What insurance do foundation model developers themselves carry?

Foundation model developers typically carry Directors and Officers, professional liability (often substantially uplifted for AI-specific exposure), IP insurance for training-data claims, Cyber, and bespoke AI wordings written by specialty carriers willing to underwrite the class. Program limits are large (D&O towers in the hundreds of millions are normal for venture-funded developers) and coverage terms are heavily negotiated. The market for AI-specific coverage at the developer level is thinner than at the deployer level and a smaller number of carriers underwrite it.

Related terms

Continue reading

General information, not legal or insurance advice.