County climate risk data API, bulk files and workbooks

County climate risk data API and bulk delivery are available for scope discussions with ESG teams, consultants and portfolio analysts. Request county hazard evidence, decade climate context or El Niño history in a format your workflow can use. The API is planned; coverage, fields, licensing and delivery must be agreed first.

Which delivery format fits your work?

Who is this for?

ESG and CSR reporting teams, disclosure and sustainability consultants, real-estate and lender risk teams, analysts and newsrooms can request a scope. AI agents and research assistants must keep credentials server-side. County data supports physical climate risk screening for ESG reporting; it does not establish framework compliance.

Which request shapes are proposed?

These request shapes describe the proposed interface.

Bulk scope can include county source fields, reviewed county fields, climate measures, El Niño winters, a field manifest and release metadata. Source-tier coverage is not the same as reviewed coverage. Portfolio matching is a batch file job to discuss first; no location-upload endpoint is offered here.

How are fields and releases documented?

Agree on a field registry that lists labels, units, geographic levels, agencies, releases and observation windows. Preserve Not Applicable, No Rating and Insufficient Data. Missing values remain missing. Keep release identifiers with exports and distinguish source release dates from observation periods.

Agency sources: FEMA, NOAA, NASA, US Census Bureau and Copernicus/ECMWF.

What would a sample response contain?

This example shows Harris County fields in the proposed response format. Climate delta is recent minus baseline. Historical claims and county measures do not predict property damage.

{
  "fips": "48201",
  "name": "Harris",
  "state": "TX",
  "hazards": {
    "riverine_flood": "Very High",
    "hurricane": "Very High",
    "heat_wave": "Very High"
  },
  "climate_periods": {
    "baseline": [
      1991,
      2000
    ],
    "recent": [
      2016,
      2025
    ]
  },
  "climate_decades": {
    "hot_days": {
      "baseline": 38.6,
      "recent": 63.9,
      "delta": 25.3
    },
    "definition": {
      "threshold": 35,
      "threshold_unit": "°C",
      "unit": "days/year",
      "label": "Hot days · ≥35°C (95°F)"
    }
  },
  "el_nino": {
    "winter": "1997–98",
    "oni_peak": 2.4,
    "rain_pct_of_normal": 157.607,
    "heavy_rain_days": 8,
    "nfip_claims": 536,
    "nfip_rank": 2
  },
  "el_nino_units": {
    "oni_peak": "°C",
    "rain_mm": "mm",
    "rain_pct_of_normal": "%",
    "temp_c": "°C",
    "temp_departure_c": "°C",
    "temp_departure_f": "°F",
    "heavy_rain_days": "days/winter",
    "nfip_claims": "claims",
    "nfip_paid_usd": "USD",
    "nfip_rank": "rank (1 = most claims; ties share rank)",
    "slope_c_per_decade": "°C/decade",
    "slope_f_per_decade": "°F/decade"
  }
}

How are access and metering agreed?

Scoped on request. Geography, fields, request volume, release version, support and refresh terms determine the written scope. No public quota or subscription plan is promised.

How do I request licensed access?

1. Describe your use, county list, state or national geography and preferred format.
2. Confirm coverage, definitions and license fit.
3. Approve the written scope and payment terms.
4. Receive the agreed delivery after payment.

Approved customers receive an individual API key after the use, geography, fields, request volume and license are agreed and paid.

Confirm availability and timing in the written scope. Internal-use rights and attribution need written agreement. Redistribution is custom-scoped. Request licensed delivery rather than scraping public pages.

Can research agents use this data?

The site publishes JSON-LD. Stable JSON shapes, release metadata, an agent-readable access summary and an MCP-style schema can be discussed in your scope. Include authentication and service availability in the agreed scope.

Discuss your scope ↗