FEMA hazard mitigation grant projects

At a glance

Publisher

Federal Emergency Management Agency (FEMA)

Jurisdiction

United States (federal)

Publisher updates

Refreshed by FEMA daily

SourceFinch checks

Daily by default

Records per run

25 in the latest run

Record key

id

Acquired from

Publisher's public API: https://www.fema.gov/api/open/v4/HazardMitigationAssistanceProjects?$filter=dateApproved%20ne%20null&$orderby=dateApproved%20desc,id&$top=25

Recipe

v1.0.0, approved October 3, 2026

Verified since

October 3, 2026

Last green run

October 3, 2026

What the data contains

Projects funded through FEMA's Hazard Mitigation Assistance grant programs: the Hazard Mitigation Grant Program (HMGP), Building Resilient Infrastructure and Communities (BRIC), Flood Mitigation Assistance (FMA) and earlier programs. Data comes from the OpenFEMA Hazard Mitigation Assistance Projects dataset (version 4). Each record is one project: its identifier, program area and fiscal year, state and county, subrecipient (usually a local government, tribe, utility or public body), project type, status, project amount, federal share obligated and approval date. Each run reads the 25 most recently approved projects, so a monitor reports newly approved projects and later changes to their status and obligations. Amounts are in U.S. dollars as reported by FEMA; FEMA's data can contain entry errors, which are passed through unchanged. Projects that acquire private properties report only property counts, not owners. OpenFEMA's citation and non-endorsement statement travels with every record.

Fields and types

Every record has these fields. The key field id identifies a record across runs, so changes are reported field by field.

Sample output

The first 5 of 25 records from SourceFinch's own run on October 3, 2026, exactly as delivered.

[
  {
    "id": "3e3e1740-677b-4605-bf37-9168f0f2b528",
    "state": "Iowa",
    "county": "Madison",
    "status": "Closed",
    "program_fy": 2020,
    "program_area": "HMGP",
    "project_type": "600.1: Warning Systems (as a Component of a Planned, Adopted, and Exercised Risk Reduction Plan)",
    "subrecipient": "East Peru (corporate name for Peru)",
    "date_approved": "6023-06-01T00:00:00.000Z",
    "project_amount": 18100,
    "project_identifier": "DR-4483-0002-F",
    "federal_share_obligated": 16290
  },
  {
    "id": "1296cfbf-2f47-4438-a6b0-4e6f48c234c7",
    "state": "Illinois",
    "county": "Lake",
    "status": "Closed",
    "program_fy": 2019,
    "program_area": "HMGP",
    "project_type": "91.5: Local Multijurisdictional Multihazard Mitigation Plan - UPDATE",
    "subrecipient": "Lake County Stormwater Management Commission",
    "date_approved": "2026-08-28T00:00:00.000Z",
    "project_amount": 90000,
    "project_identifier": "DR-4461-0002-P",
    "federal_share_obligated": 67500
  },
  {
    "id": "1ed64988-506d-41e4-a174-c1d3bea9f90c",
    "state": "Oklahoma",
    "county": "Wagoner",
    "status": "Approved",
    "program_fy": 2023,
    "program_area": "HMGP",
    "project_type": "600.1: Warning Systems (as a Component of a Planned, Adopted, and Exercised Risk Reduction Plan)",
    "subrecipient": "MUSCOGEE (CREEK) NATION",
    "date_approved": "2026-08-28T00:00:00.000Z",
    "project_amount": 259498.24,
    "project_identifier": "DR-4706-0004-F",
    "federal_share_obligated": 171268.84
  },
  {
    "id": "61569c0c-1d1a-4970-89e6-27230df3d53b",
    "state": "Arkansas",
    "county": "Poinsett",
    "status": "Approved",
    "program_fy": 2024,
    "program_area": "HMGP",
    "project_type": "91.5: Local Multijurisdictional Multihazard Mitigation Plan - UPDATE",
    "subrecipient": "Poinsett (County)",
    "date_approved": "2026-08-28T00:00:00.000Z",
    "project_amount": 35000,
    "project_identifier": "DR-4788-0017-P",
    "federal_share_obligated": null
  },
  {
    "id": "6b125faf-a1fb-47b0-8552-702c94870577",
    "state": "Arkansas",
    "county": "Newton",
    "status": "Approved",
    "program_fy": 2024,
    "program_area": "HMGP",
    "project_type": "91.5: Local Multijurisdictional Multihazard Mitigation Plan - UPDATE",
    "subrecipient": "Newton (County)",
    "date_approved": "2026-08-28T00:00:00.000Z",
    "project_amount": 20000,
    "project_identifier": "DR-4788-0001-P",
    "federal_share_obligated": null
  }
]

Evidence behind every value

• Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash 035b90a7416c3a38a55778b0dda7f4414e36f5cd26d84a0db2281633b4f8382c.
• Every value records where it came from in that response: a JSON Pointer into the retained capture.
• Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is 8265cf682d761eecc931227815afc7bc1d218e3a4b49c18199a0a789bc5c77af, timestamped October 3, 2026.
• The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
• Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch: sourcefinch verify-bundle run.wacz.

Terms posture and usage rights

OpenFEMA offers FEMA's public data through an API without a key. Its terms require citing the dataset and the access date, stating that the product uses the OpenFEMA API but is not endorsed by FEMA, not modifying the data while presenting it as FEMA's, not using FEMA or DHS logos, not attempting to re-identify individuals, and using the data for statistical research or as a reporting record rather than for decisions about individuals' rights or benefits.

Federal Emergency Management Agency (FEMA), OpenFEMA Dataset: Hazard Mitigation Assistance Projects - v4. This product uses the FEMA OpenFEMA API, but is not endorsed by FEMA. The Federal Government or FEMA cannot vouch for the data or analyses derived from these data after the data have been retrieved from the Agency's website(s).

Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.

Reliability

Runs, last 30 days

1

Green

100%

Failed

0

Median run time

0.8 s

Latest run

success, October 3, 2026

Measured on runs of this recipe version across SourceFinch, anonymized. This recipe is newly Verified; the numbers fill in as it runs daily.

Use it

Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).

{
  "name": "FEMA hazard mitigation grant projects",
  "url": "https://www.fema.gov/api/open/v4/HazardMitigationAssistanceProjects?$filter=dateApproved%20ne%20null&$orderby=dateApproved%20desc,id&$top=25",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "HazardMitigationAssistanceProjects[*]",
    "fields": {
      "id": "id",
      "state": "state",
      "county": "county",
      "status": "status",
      "program_fy": "programFy",
      "program_area": "programArea",
      "project_type": "projectType",
      "subrecipient": "subrecipient",
      "date_approved": "dateApproved",
      "project_amount": "projectAmount",
      "project_identifier": "projectIdentifier",
      "federal_share_obligated": "federalShareObligated"
    },
    "required": [
      "id",
      "project_identifier",
      "state",
      "date_approved"
    ]
  },
  "key_field": "id",
  "schedule": "daily",
  "rights": true
}

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/openfema-hazard-mitigation-projects -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

sourcefinch login
sourcefinch catalog get openfema-hazard-mitigation-projects --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

import { SourceFinch } from "@tsg/sourcefinch";

const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("openfema-hazard-mitigation-projects");
const source = await sf.sources.create({
  name: entry.name.slice(0, 100),
  url: entry.acquisition_path.endpoint,
  recipe: entry.recipe.definition,
  key_field: entry.recipe.key_field,
  schedule: entry.recipe.schedule,
  rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor FEMA hazard mitigation grant projects: get_catalog_source openfema-hazard-mitigation-projects,
then create_source with its create_source_args (dry run first), then run_source."

Pricing

Each check is one run, whatever the number of records, and failed runs are free. On its default daily schedule this source uses about 30 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.

Related sources

• FEMA disaster declarations · Federal Emergency Management Agency (FEMA)