AI Hallucination

An AI hallucination is when an AI system states something false as if it were true, with no basis in its source data or training. The output sounds fluent, confident, and well-formed, and that is exactly what makes it dangerous. The model isn't flagging a guess; it's presenting fiction in the same voice it uses for fact.

In Depth

Hallucination isn't a bug in the ordinary sense. Generative models are built to produce the most plausible next piece of text, not the most true one. Most of the time plausible and true line up. When they don't, say the model has a gap in its knowledge, an ambiguous prompt, or a retrieval step that returned nothing useful, it fills the gap with something that reads correctly rather than admitting it doesn't know.

That's why hallucinations are so hard to catch in production. There's no error code, no stack trace, no dropped request. The agent returns a clean, confident answer, and unless someone knows the ground truth, nothing looks wrong. The failure is invisible until a customer acts on the bad output, and by then it's already caused harm.

The exposure scales with two things: how much the agent operates without a human checking its work, and how high the stakes of its domain are. A chatbot suggesting a recipe can hallucinate all day. A support agent quoting policy, a legal assistant citing case law, or a clinical tool summarizing a chart cannot. There, a single confident fabrication is a direct line to a claim.

What It Looks Like

In 2024, a Canadian tribunal held Air Canada liable for a refund its support chatbot had invented, a bereavement-fare policy that did not exist. The airline argued the bot was a separate entity responsible for its own statements. The tribunal disagreed: the company was responsible for everything on its website, including what its AI said. The customer got the refund, and the case became the reference point for "your agent's words are your words."

Now picture the same pattern in healthcare. An AI scribe summarizing a patient visit adds a symptom the patient never reported, or drops a medication the doctor did prescribe. The note goes into the record. The next clinician treats the patient based on it. This is no refund dispute. It's a path to a malpractice claim, with your agent in the chain of causation.

Why It Matters For AI Vendors

Hallucination is the most common AI failure and the most quotable one. It shows up in headlines, in courtrooms, and in your enterprise customer's security questionnaire. When a hallucination causes financial or physical harm, the resulting claim usually lands as misrepresentation, negligence, or professional liability. And here's the trap: the Tech E&O policy most AI vendors carry now excludes exactly this. The AI carve-outs added through 2025–2026 were written to keep "the AI said something false" claims out of traditional coverage.

So a vendor can be fully insured on paper and completely uncovered for its single most likely failure mode.

Common Questions

No. A bug is code doing something other than what it was written to do. A hallucination is the model doing exactly what it was designed to do, producing fluent output, and being confidently wrong. You can't patch it away; you manage it with retrieval grounding, guardrails, human review, and testing.
Not with today's models. You can drive the rate down with grounding and constraints, and you can catch more of them with red-teaming and human-in-the-loop review, but residual risk remains, which is the case for insuring it rather than assuming it away.
Increasingly, no. Check your Tech E&O and CGL forms for AI or "generative AI" exclusions added in 2025–2026. If they're there, a hallucination-driven claim likely falls in the gap Ollive's AI Liability Insurance is built to fill.
← PreviousAI Governance Maturity Next →AI Incident Response

See where your AI agents stand.

Get an Agent Trust Score, map your liability exposure, and find out what it takes to make your AI agents insurable.