Access the OpenFEMA API at the base path https://www.fema.gov/api/open without authentication; identify the FimaNfipClaims dataset endpoint in the OpenFEMA data catalog
Issue a GET request with query parameters to filter by fields such as yearOfLoss, floodZone, occupancyType, and state; use the $top and $skip parameters for pagination since the dataset contains over two million records
Request only required fields using the $select parameter to reduce payload size, focusing on fields like buildingDamageAmount, contentsLossAmount, causeOfDamage, and totalBuildingInsuranceCoverage
Aggregate the results by flood zone, year, and occupancy type to compute average loss ratios, frequency distributions, and geographic concentration
Cross-reference aggregated loss data with NFHL flood zone shapefiles to validate that your book of business has appropriate premium loadings relative to historical NFIP experience
Known gotchas
The dataset is redacted for privacy—precise addresses and coordinates are not included; geographic analysis is limited to census tract or zip-code level granularity
Fields such as buildingDamageAmount have been added in recent dataset versions and may be null for older claim records; handle nulls explicitly before computing averages
OpenFEMA imposes rate limits; large bulk downloads should use the bulk data files (CSV/JSON exports available on the dataset page) rather than paginating through millions of API calls
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp