Skip to main content
Research Preview — APIs may change. GitHub

Parametric insurance

You’re building crop insurance. When a qualifying weather event occurs within a certain distance of insured farmland, the policy pays out — without a manual claims process or an adjuster visit — once the spatial condition is verified.
Astral verifies the distance computation between the inputs you supply. It does not establish that a qualifying weather event actually occurred, or that the weather-station coordinates are truthful — those come from outside the system (an oracle, a data feed, a registered location). The signed result is one trustworthy link in the chain, not the whole chain. Design the event-reporting and location inputs with the same care, and be explicit with policyholders about what is verified and what is trusted. This is a Research Preview, not a production insurance product.

How it works

  1. The insurance contract stores a farmland location UID and references to weather station locations
  2. When a weather event is reported, the system computes the distance from the event to the insured farmland
  3. If the distance is below the policy threshold, the payout triggers automatically
  4. The signed result provides auditable proof that the spatial condition was met

The flow

Register locations

Both the insured farmland and weather station locations are registered as onchain location records.

Compute distance when an event occurs

When a qualifying weather event is reported at the station, compute the distance to the insured farmland.

Resolver contract

The insurance resolver decodes a numeric signed result and checks whether the distance is below the policy threshold.

Why this matters

Traditional crop insurance requires:
  • Filing a claim
  • Waiting for an adjuster
  • Disputing coverage decisions
Parametric insurance reduces much of that. The spatial condition is defined upfront, the distance computation is independently verifiable, and the payout can be automated against it. The signed result is auditable proof that the spatial condition was computed correctly on the given inputs — the remaining trust (that the event occurred, that the station data is honest) sits with whatever feeds those inputs.

Variations

  • Flood insurance — use intersects to check if a flood polygon overlaps insured property
  • Wildfire proximity — use distance from fire perimeter to insured structures
  • Hurricane path — use within to check if insured property falls within the projected storm path

Next: Geofence compliance

Prove an asset stayed within an approved boundary