US Disaster Declarations & FEMA Money Monitor (MCP)
Pricing
Pay per event
US Disaster Declarations & FEMA Money Monitor (MCP)
OpenFEMA official feed: disaster declarations (DR/EM/FM) with state, county & assistance programs, plus public-assistance money obligations with amounts & damage categories. Filter by state/incident/program/amount. Monitor mode = daily alerts the hour FEMA acts. No API key. MCP-ready.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Zakaria el bouami
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
12 days ago
Last modified
Categories
Share
🌪️ US Disaster Declarations & FEMA Money Monitor (MCP)
The full OpenFEMA official feed: every US disaster declaration — and every dollar of public-assistance money obligated — with state, county, programs, incident type and amounts. Monitor mode = "a disaster was declared / new FEMA money landed" alerts, daily. Official API. No key. MCP-ready.
✨ The 6 things ChatGPT can't do (built in)
| Ingredient | Here |
|---|---|
| 🔒 Hard-to-get data | Two OpenFEMA v2 entities chained: DisasterDeclarationsSummaries + PublicAssistanceFundedProjectsDetails — federal share obligated, project amounts, damage categories, per-county designations. 100% the federal record. |
| 🛠️ Hardest problems, solved | openFEMA quirks handled: NULL incident dates (EM declarations), per-area rows, PA state via stateAbbreviation, re-obligations at new amounts. |
| ⚙️ Automation | monitor + daily schedule = "Hurricane EM declared for Alabama — Baldwin, Escambia, Mobile counties" the morning it happens. Disaster-recovery contractors, debris/hauling firms, roofers, engineering firms and NGOs mobilize on exactly this signal — and pay for it. |
| 🧠 AI-agent cheap | $0.001 start + $0.001 per item. |
💡 The two money signals, separated: (1) a new county designation on an existing disaster (KV key = disaster + area — you see Isaias gain counties in real time), and (2) a re-obligation when the same project gets MORE money (KV key includes the federal share). Both are charged events. Both are what small Contractors actually act on.
🚀 3 recipes that pay
#1 — Storm-chaser mobilization (disaster contractors)
{ "mode": "monitor", "daysBack": 1, "states": ["FL", "LA", "TX", "AL", "MS"], "incidentTypeIncludes": "Hurricane" }
→ Schedule 06:00 → the hour FEMA declares anything hurricane-ish in the Gulf, your crew knows before the newsrooms do.
#2 — Follow the federal money (subcontractors, bond desks)
{ "mode": "monitor", "scopes": ["pa"], "minFederalShare": 100000, "daysBack": 7 }
→ Only obligations ≥ $100k, nationwide — road damages, utilities, emergency protective measures, with county + damage category.
#3 — Regional risk intel (insurers, journalists, NGOs)
{ "mode": "search", "scopes": ["declarations"], "declarationTypes": ["DR"], "daysBack": 90, "maxResults": 300 }
→ Every major-disaster declaration of the quarter, programs and counties included.
MCP: https://mcp.apify.com/?actors=amygraphics/fema-disaster-monitor — your agent answers "any new FEMA declarations or big obligations in Louisiana this week?" with the official record.
📦 What each row contains
Declaration rows: disasterNumber · declarationType (DR/EM/FM) · title · state/stateCode · designatedArea + countyCode · programs[] (IA/PA/HM/IH) · incidentType + begin/end dates · declarationDateISO · lastIAFilingDateISO (survivor deadline) · tribalRequest · fyDeclared · closeoutDateISO · url.
PA money rows: disasterNumber · pwNumber · applicationTitle · state/county · damageCategoryCode/damageCategory (roads, utilities, water, buildings…) · federalShareObligated / totalObligated / projectAmount / mitigationAmount · projectSize/projectStatus/projectProcessStep · firstObligationISO/lastObligationISO · url.
Plus feed · eventKey · isNew/firstSeenAt (monitor) on every row.
🆚 Competition
| Actor | Users | Monitor | The money feed (PA $) |
|---|---|---|---|
| fortuitous_pirate/fema-flood-scraper | 21 | ❌ flood only | ❌ |
| ryanclinton/fema-disaster-search | 16 | ❌ | ❌ |
| us | — | ✅ KV dedupe both feeds | ✅ obligations + re-obligations |
🧪 Input reference
| Key | Default | What it does |
|---|---|---|
mode | search | monitor = only never-seen items (KV fema-seen) |
scopes | both | declarations / pa |
daysBack | 14 | declarationDate (decl) / firstObligationDate (money) |
states | all | server-side state filter (FL, TX…) |
declarationTypes, programsInclude | all | DR/EM/FM and IA/PA/HM/IH |
incidentTypeIncludes | — | 'Hurricane', 'Flood', 'Fire'… |
minFederalShare | 0 = off | money-feed threshold |
countyIncludes, keywords | — | client-side refinement |
Fair use — OpenFEMA is FEMA's official open-data API (public federal works). Two polite requests per run max, date-windowed server-side.
💰 Pricing
- $0.001 actor start · $0.001 per item — counties, programs, obligations FREE
| Rows | Cost (us) |
|---|---|
| 60 items (weekly storm scan) | ~$0.06 |
| Daily national watch (30 days) | ~$0.30–1/month |
Part of the AmyGraphics data empire — 29 public actors: recalls (FDA + CPSC), tenders (EU/US/UK), registers (companies, grants, trials, regulations), disasters, conferences, jobs & real estate. Contact: morocco.uiux@gmail.com · apify.com/amygraphics