# US Disaster Declarations & FEMA Money Monitor (MCP) (`amygraphics/fema-disaster-monitor`) Actor

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.

- **URL**: https://apify.com/amygraphics/fema-disaster-monitor.md
- **Developed by:** [Zakaria el bouami](https://apify.com/amygraphics) (community)
- **Categories:** Lead generation, Automation, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## 🌪️ 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)

```json
{ "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)

```json
{ "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)

```json
{ "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

# Actor input Schema

## `mode` (type: `string`):

search = window of items. monitor = only items never returned before (KV dedupe) — schedule daily.

## `scopes` (type: `array`):

declarations (new disasters + new county designations) / pa (public-assistance money obligations) — empty = both.

## `daysBack` (type: `integer`):

Declarations: declarationDate. PA money: firstObligationDate (fresh money lands here).

## `states` (type: `array`):

US state abbreviations, server-side: FL, TX, LA, AL… — empty = all.

## `declarationTypes` (type: `array`):

DR (major disaster) / EM (emergency) / FM (fire management) — empty = all. Declarations feed only.

## `incidentTypeIncludes` (type: `string`):

Client-side: 'Hurricane', 'Flood', 'Fire', 'Severe Storm', 'Tornado'…

## `programsInclude` (type: `array`):

PA (public assistance) / IA (individual) / HM (hazard mitigation) / IH (individual & households) — declarations feed only.

## `minFederalShare` (type: `integer`):

PA feed only: keep only obligations ≥ this amount. 0 = off.

## `countyIncludes` (type: `string`):

Client-side match on designated area or county (e.g. 'Baldwin', 'Monroe').

## `keywords` (type: `string`):

Client-side match on title, applicant, damage category, county, incident type (e.g. 'road', 'water', 'debris').

## `maxResults` (type: `integer`):

Stop after this many items (both feeds combined).

## `requestDelaySecs` (type: `number`):

Politeness pacing toward the official portal.

## `proxyConfiguration` (type: `object`):

NOT needed — official API.

## Actor input object example

```json
{
  "mode": "search",
  "scopes": [
    "declarations",
    "pa"
  ],
  "daysBack": 14,
  "states": [],
  "declarationTypes": [],
  "incidentTypeIncludes": "",
  "programsInclude": [],
  "minFederalShare": 0,
  "countyIncludes": "",
  "keywords": "",
  "maxResults": 60,
  "requestDelaySecs": 0.3,
  "proxyConfiguration": {}
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("amygraphics/fema-disaster-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("amygraphics/fema-disaster-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call amygraphics/fema-disaster-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,amygraphics/fema-disaster-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/9pJv02XatdwELixdy/builds/TovyRqIEDYfFw5YZu/openapi.json