Risk that fires on receipts.
ACORD + parametric oracles.
Policies as typed objects. Triggers as signed events. No adjuster needed when the trigger is a witnessed receipt from the right oracle.
Two ways in
One scenario. One artifact.
A parametric flood policy fires on a NOAA gauge.
Homeowner policy with a parametric flood rider. Trigger: NOAA gauge X124 exceeds 12.4 ft. When the gauge crosses, the receipt IS the claim — payout fires automatically. 1.7 joules to bind. Zero to claim.
ACORD inspector + parametric simulator.
Pick a policy form. Set a trigger. Watch the payout cascade fire on a simulated oracle event.
The receipt
Every operation. Every joule. Signed.
This is what InsuranceOS returns. Not just a result — a signed JWP ReceiptPayload with the energy consumed, the standard cited, and the cryptographic signature that makes it audit-grade.
What this platform believes
Three statements. Each is the proof of the next.
Homeowner policy with a parametric flood rider. Trigger: NOAA gauge X124 exceeds 12.4 ft. When the gauge crosses, the receipt IS the claim — payout fires automatically. 1.7 joules to bind. Zero to claim.
Watch it happen →Pick a policy form. Set a trigger. Watch the payout cascade fire on a simulated oracle event.
Open the artifact →Same identity, same format, same billing unit (joules), same wire transport. InsuranceOS ships the part that handles risk.
See the receipt format →