Pull historical gridded weather data from the dClimate REST API to evaluate a parametric weather insurance payout trigger
domain: api.dclimate.net · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the relevant dataset for the insured peril (e.g., temperature, rainfall, wind) from the public dClimate data catalogue.
Call `apiv4/grid-history/<dataset_name>/<latitude>_<longitude>` to retrieve a historical time series of gridded values for the location tied to the insured risk.
For area-based rather than single-point triggers, use `apiv4/geo_temporal_query/<dataset_name>` with `output_format` set to `array` or `netcdf` to pull data across a region.
Compare the retrieved observed values against the policy's pre-agreed trigger threshold (e.g., rainfall below a set amount over a set period) to determine whether a parametric payout condition has been met.
Since the data-consumer REST API tier is free, budget separately for any paid, higher-assurance datasets or forecast products in the dClimate marketplace if the program needs them.
Known gotchas
dClimate is a decentralized, blockchain-anchored data network (Polygon/IPFS, with Chainlink-oracle-validated "skill scores"), not a conventional single-vendor SLA API — factor its provenance/governance model into any audit-trail requirement for a regulated payout decision.
The free REST API is for data consumption only; it is not itself an insurance quote/bind/claims API — actual policy issuance and payout execution (e.g., by Arbol, which is built on dClimate) is a separate system that merely consumes this data feed.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?