I built the claims database AI risk didn't have.
Insurers are being asked to price AI risk with no loss history to price it from. PerilAI is the missing book: real AI-liability matters, filed by the insurance line they hit, each one carrying its sources.
I designed the data model, the verification standard, the research pipeline, and the product. It is the largest thing I have built.
How a claim gets in.
Six stages, with my judgment at the two places it actually matters: what counts as an AI loss, and what is sourced well enough to publish.
A weekly crawl of court dockets, regulator actions, and legal press turns up candidate matters.
Most candidates are not losses. They get rejected with a written reason, and those reasons become the training set.
Survivors get the full write-up: what happened, what the AI did, who was sued, and under what theory.
The part only a carrier person can do: which policy responds, and where the new AI exclusions would bite.
Every record waits in a queue until I publish or reject it. Nothing reaches the database on the model's say-so.
Live to the catalog, the dashboard, and the API at the same moment, sources attached.
The dashboard
How PerilAI decides what's real.
Built with Python · FastAPI · SQLite · Claude · agentic research pipelines · a taxonomy I wrote myself