Insurance

A driving record, for AI.

Motor became priceable when verified telemetry existed. AI conduct has none, so when a loss arrives the only record of what the AI did is the defendant’s own logs. Regulayer™ is that missing record: content-free, tamper-evident, and verifiable by a party adverse to everyone involved.

Bring us a book Book a live demo

Runs inside the insured’s environment. Its data does not leave it.

The problem

The AI liability line is being built without its raw material.

Every priced line began with a loss history. This one has none, so the market is pricing on model testing and on questionnaires, while exclusions are being written at the same time as the cover is being asked for.

7 of 13Lawyers’ professional-liability carriers reporting actual AI-related claims, and adding AI questions at underwriting.EPIC 16th LPL survey, 2026

May not coverStandard malpractice policies may not respond to AI-related claims at all.ABA Journal, February 2025

January 2026ISO’s generative AI exclusion for general liability. Where a carrier adopts it, AI cover becomes its own decision at renewal.ISO CG 40 48 01 26

80%+Of carrier requests to exclude AI-related damages from corporate policies, approved by state insurance commissioners.CSIS, September 2026

The stop is insuredA new cyber endorsement pays the business interruption when an insured suspends its own malfunctioning AI. A claim needs the record of when it drifted and who stopped it. The stop, proved.Beazley, AI Voluntary Shutdown, 24 September 2026

26US jurisdictions that have adopted the NAIC bulletin on insurers’ use of AI. The rules, jurisdiction by jurisdiction.NAIC adoption map, 31 August 2026

OctoberRenewal season. A firm that can hand its broker a signed conduct record instead of an assurance is a different risk on the same form.The renewal question is already on the form

The stop

The stop is now insured. Prove who pressed it.

Cover now pays when an insured suspends its own malfunctioning AI. At claim, the insurer asks when the AI drifted, who stopped it, whether they held the authority, and what ran afterwards. FailStop answers all four from one sealed record.

A named, authorized person pulls the switch. Every action stops, including the one already in flight. Tripped, it stays tripped: nothing runs again until a person re-arms it, and the AI cannot re-arm itself.

The question at claim	From the FailStop record
When did the AI drift?	The first action outside the agreed authority, sealed as it happened.
Who stopped it, and when?	The named person who pulled the switch, to the moment.
Did they hold the authority?	Who held the authority, and who withdrew it, in the same sealed record.
What ran afterwards?	Every later request held, until a named person re-armed it.

See FailStop Start a pilot

The halt and its proof are sealed together. Regulayer™ supplies the evidence; the insurer makes the determination.

The Witness, for insurers

Your book, as it happens.

A working demonstration of the carrier’s view. Open an insured, withdraw a person’s authority, check a claim against the record, and watch binds checked as they are issued. Sample insureds, sample actions.

LIVE

Insured	Sector	Actions today	Drift stops per 1,000	Named person	Record

Select an insured to open it.

0Actions checked

0Drift stops per 1,000

$0Value held by stops

noneStopping distance, last withdrawal

Named people holding authority

Named binder	Binding authority	Authority

Bind	By	Result

TodayA bordereau arrives next month. An audit samples some of it. A bind outside authority is found weeks later, if at all.

With the recordEach bind is checked against that person’s current authority as it is issued. Outside it, the bind is refused and recorded.

Sample insureds, sample actions. The record shows who allowed each action and whether their authority held; the price stays the insurer’s.

What it takes

The technology stack to write AI insurance.

From the carrier’s seat, a control becomes evidence when nine requirements are met. Here is each one, and where Regulayer™ stands today.

Supplies itWorks with it

LAYER 1The evidenceWhat the insurer prices on.

01A standard evidence schemaConsistent data across every insured.Supplies it

02Loss data and pricing modelsFrequency and severity, to set price and capacity.One signed record per action, allowed or refused: the raw material for loss data. Incident databases count incidents but not actions taken, so no rate per action exists. Every action here is counted, which gives the exposure base: rates per 1,000 actions. The models stay the insurer’s.Supplies the data

03Incident reportingThe claims signal, on time.Every refusal and every effect is recorded as it happens, so the timeline of an incident exists on the day, not after discovery.Supplies it

LAYER 2The proofWhat survives a claim.

04Audit rightsChecking the record without taking the insured’s word.An auditor checks the record without the insured’s system or ours.

05Legal admissibilityEvidence that stands up in a dispute.The path is certification under FRE 902(13) and 902(14).

06Independent certificationSomeone else carries the checking.Regulayer™ supplies the evidence. It sits beside ISO/IEC 42001 and insurer-linked audits, and gives the auditor records to test.Works with it

LAYER 3The resilienceWhat keeps the control from becoming the risk.

07Continuity if the vendor failsControl infrastructure can die.Records verify offline, with an open verifier, whether or not Regulayer™ is still there.Built in

08Accumulation riskOne shared control failing across many insureds.Runs on the insured’s own infrastructure, with no shared cloud service of ours between insureds. Each control states the release it runs, its key custody, its time source and its dependencies, so an insurer can count how many insureds share one point of failure.Designed for it

09Availability and false refusalsA control that stops too much becomes business interruption.Off the authority, an action is sent back to correct before it is stopped, so the work keeps flowing. Every period the control was unavailable is signed, with what it refused. Every refusal is linked to what followed, so refusals that proved unnecessary are counted, with the value and hours they held.

The nine requirements come from Regulayer™ market research across carrier, standards and regulator sources. Regulayer™ supplies the evidence; the insurer makes the determination.

The cover line

The authority the insured agrees is the cover.

Named person by named person: which agent may do what, up to what limit. Inside that authority, the action is covered. Outside it, the action is stopped before it takes effect, excluded, or bought as additional cover that extends the authority and the premium together. Every record shows which side of the line each action fell, at the moment it happened.

Inside the agreed authorityCovered.A named person allowed it, and their authority held at the moment it took effect.

Outside itStopped. No loss.The action never took effect, and the record proves it.

Outside it, by choiceAdditional cover.The insured extends the authority, and the cover and premium move with it.

What an underwriter prices on

AI risk, turned into rating variables.

Read from signed records, per insured and across a book. The models and the price stay the insurer’s.

Rating variable	From the record	What it prices
Agreed authority	The cover line, named person by named person	Exposure: what is insured, and what is excluded or sold as additional cover
Actions taken	Every action counted, allowed or refused	The exposure base: rates per 1,000 actions
Drift rate	Drift stops per 1,000 actions, and the trend	Frequency: a leading sign before a loss, like hard braking in motor
Stopping distance	How long after authority is withdrawn an action can still take effect, and how many did	Severity: what can still happen after the person says stop
Value held	What refused actions would have moved	Severity: what the control kept from happening
Named-person coverage	Share of actions resting on a named person, not a service account or shared login	Quality of control
Wrong refusals and availability	Refusals later proved unnecessary; signed periods the control was unavailable	Business interruption caused by the control itself
Shared-failure exposure	Release, key custody, time source and dependencies of each control	Accumulation across a book
Proof of absence	A signed proof that no other approval existed at a given moment	Renewal and claims certainty

Delegated authority

Every bind checked as it is issued, not sampled afterwards.

A coverholder, MGA or its software agent binds on the carrier’s paper under a binding authority: classes, territories, limits, expiry. Today that is checked after the fact, from bordereaux and a sample audit.

With Regulayer™, each binder, policy or certificate is checked against that named person’s current class, territory, limit and expiry as it is issued. Narrow or withdraw the authority, and the next bind outside it is refused and recorded. The carrier, its managing agent, a reinsurer or an auditor can verify every bind, not a sample.

At claim

Decided from the record, not reconstructed from memory.

Who allowed itA named person, by name.And whether their authority still held at the moment the action took effect.

Proof of absenceNo other approval existed.A signed proof that no other approval was in force at that moment, checkable by a party holding nothing else.

StoppedNo loss.A refused action never took effect, and the record proves it.

Agent to agentSettlement with both authorities checked.Where a claimant’s agent and an insurer’s agent settle, each side’s named authority is checked at acceptance, and both hold one record.

The carrier’s view

Read the whole book, live.

With the insured’s agreement, the carrier reads the records at any time through the Witness: drift, stops, withdrawals and trends across its book, sliced by insured, sector, class, named person and period. The carrier builds nothing.

A carrier can make the control a condition of affirmative AI cover, or price better terms when it runs, the way telematics works in motor.

Two ways in

Start with the proof. Add the control.

The barrier to AI cover, as CSIS puts it, is that carriers cannot see “whether claimed risk controls actually exist.” The Witness shows them. Both run on the same sealed record. The insured holds the control. The carrier holds a read-only view, with the insured’s agreement, the way a driver agrees to a telematics box.

The Witness · the proof

See what the AI did, live.

The insured runs Regulayer™, which seals every AI action as it happens. The carrier reads the book through the Witness: actions, drift, stops and trends, by insured, class and named person.

Nothing in the insured’s operation changes.
Every record verifies offline, by anyone.
The first step for a carrier and a book.

Regulayer™ Control · the control

Outside the agreed authority, stopped.

The insured sets the authority, named person by named person. An action outside it is stopped before it takes effect, and the record shows it. This is what makes the cover line hold.

A condition of affirmative AI cover, or better terms.
Drift is stopped before it takes effect.
The basis for every rating variable above.

	The insured	The carrier
Holds	The authority and the control, inside its own environment	A read-only view through the Witness
Agrees to	Share the sealed record with its carrier	Read it, and price on it
Sees	Its own actions and content	The conduct record, content-free

Start a pilot Estimate a book

Estimate a book

What drift could cost, and what the record would show.

Enter your own figures for one insured, or a whole book. The arithmetic runs in your browser and nothing is sent.

Drifted actions a year: 0
Exposure a year, if they take effect: $0
Held by Regulayer™ Control: $0held before it took effect: every drifted action outside the agreed authority is stopped, and sealed as a rating variable an underwriter can read.
Records a year for the underwriter: 0one sealed record per action, allowed or stopped

Your figures. The models and the price stay the insurer’s.

The precedent

Cyber went through this first.

Early cyber policies took the insured’s word on controls, and the word turned out to be worth very little at claim. The market moved to evidence of controls as a condition of cover, and priced accordingly. AI has arrived at the same point without the equivalent evidence existing yet.

In Johnson v. Dunn the firm had an AI policy in place and its lawyers were sanctioned anyway. The policy was not the failure. The failure was that nothing existed to show whether it had been followed on the day.

Two sides of one market

For the carrier using AI, and the carrier covering it.

Insurers deploying AIControl before consequence.Claims, underwriting and service agents act only under the authority a named person set. Off it, the action is sent back or held, and a signed record shows who authorized what.

Insurers underwriting AI riskConduct you can price.A sealed, content-free record of how AI is actually used, which an outsider can verify without trusting the insured.

What a carrier gets.

Self-evaluating coverage conditions.A condition written against attested operating state, checkable by both sides, with neither party seeing the other’s content. Replaces a questionnaire answered once at bind.

The ask

Bring us a book, and we will show you the record behind it.

We are looking for underwriters and claims specialists in professional lines, cyber and technology E&O to answer one question: which fields of a conduct record would actually move an underwriting or a claims decision.

Nothing here asks you to trust us. Every artifact verifies offline, with no contact with us at all.

Start a pilot Write to hello@regulayer.com AI rules for insurers The full insurers brief

Regulayer™ supplies the evidence. The insurer reads the record and makes the determination. Any change to a sealed record fails verification.