Who it's for
Location-level flood depth and a 0–100 Flood Score for underwriting, with batch screening across a whole book in a single call.
Free, with no login: browse the 100-year layer and check individual locations, so you can test the hazard data against your own claims history before any commercial conversation. Portfolio calls, tiles, other return periods and climate scenarios are paid tiers — the free tier is a single point on the 100-year event, rate-limited, and is not a production entitlement.
The problem
Indian flood is one of the largest and least well-modeled perils on the subcontinent. Global vendor models often thin out at Indian resolution, and the terrain data underneath them is where the error concentrates.
Underwriting still frequently falls back on district-level proxies or PIN-code averages, which cannot distinguish a raised plot from the low ground across the road.
And accumulation is hard to see until it is realised — a book can be concentrated inside a single floodplain without that being visible anywhere in the portfolio system.
In practice
Each one is a real workflow — who does it, the situation, the steps, and what comes back.
A submission arrives with an address. You need a flood view fast enough that it does not slow the quote.
What you get: Depth and a hazard score at the risk location, fast enough to sit inside a quote flow.
GET /v1/point You need to know how much of the portfolio sits in one floodplain — the question that only matters before the event.
What you get: A book-level exposure view built for accumulation rather than assembled from individual lookups.
POST /v1/portfolio A treaty submission is stronger when the flood exposure is characterised independently rather than asserted.
What you get: An independent, documented characterisation of the flood exposure in the book.
POST /v1/portfolio Regulatory and internal stress testing increasingly asks what the same book looks like under a warmer climate.
What you get: A like-for-like comparison of the same book under current and future rainfall.
On request — SSP2-4.5 & SSP5-8.5 After a flood, the constraint is deciding which notified locations to inspect first.
What you get: A prioritised inspection list — with the explicit caveat that this is hazard, not observed damage.
POST /v1/portfolio How you get it
GET /v1/point POST /v1/portfolio GET /v1/tiles On request Organization and Enterprise are commercial plans — see the API page or talk to us. Return periods other than the 100-year event, and climate scenarios, are not part of the free layer.
Related reading
This is a hazard model, not a loss model — it returns depth and a hazard score, not damage, downtime or expected loss. It covers riverine and pluvial flood, not cyclone storm surge. Vulnerability curves and financial modelling remain yours.
We publish the limits next to the numbers. A risk map that hides its own weaknesses isn’t a public good.
We can run a sample of your book against the layer so you can see the fit before committing.
Also for
Flood exposure for planning, not just for response
Read more →Where to work, before the water tells you
Read more →Find out before you sign
Read more →See the flood exposure sitting inside your loan book
Read more →Know what flood risk is doing to portfolio value
Read more →Keep the plant running — and know what to disclose
Read more →Check the site before the design is fixed
Read more →