[Integrations](https://spiral.ai/integrations) › [dots](https://spiral.ai/integrations/dots) › [FEMA disaster declarations](https://spiral.ai/integrations/dots/fema-disaster-declarations)

# How to Use FEMA disaster declarations in dots

Returns disaster declaration summaries with designated areas, incident information, and declared assistance programs. Use it to find declarations for a place or period, or inspect the areas attached to a disaster number.

|  |  |
| --- | --- |
| Model | FEMA disaster declarations |
| Available through | Alexandria |
| Category | Public Records |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, with a Spiral API key |

## Prompts to try with FEMA disaster declarations in dots

- Each Friday, use FEMA disaster declarations to find Louisiana declarations made during the previous seven days and list the designated areas under each disaster number.
- Every Monday at 9am: use FEMA disaster declarations to look this up and give me the result as a table.
- Pull the latest numbers from FEMA disaster declarations and tell me what changed since last week.
- Check FEMA disaster declarations and summarize what you find in three bullet points.
- Pull the newest data from FEMA disaster declarations and give me the result as a table.

## How to set up FEMA disaster declarations in dots

Pick the way that suits you. Each takes about two minutes.

### Use the Spiral skill

1. **Send dots this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use Spiral's MCP server

1. **Create an API key**: In the console, open API keys and create a key for your dot. Copy it.

2. **Send your dot this message**: Your dot reads Spiral's skill and asks for your API key.

```text
set up https://spiral.ai/SKILL.md
```

3. **Give your dot the key**: When your dot asks for the key, add it where your dot keeps secrets, never in the chat itself.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run FEMA disaster declarations**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "fema-gov/us-disaster-assistance/search_disaster_declarations",
    "input": {
      "skip": 0
    }
  }'
```

Then paste one of the prompts above: dots finds FEMA disaster declarations on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/dots

## FEMA disaster declarations tools and prices

- [FEMA · Search disaster declarations](https://spiral.ai/tools/alexandria/fema-gov/us-disaster-assistance/search_disaster_declarations) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| skip | 0 to … | 0 | Rows to skip (OpenFEMA $skip); pass the previous page's `next_skip`. |
| limit | 1 to 1000 | 100 | Rows per page (OpenFEMA $top). |
| state |  | — | Two-letter state or territory code as OpenFEMA stores it (AS, MP, VI, GU, PR, TX, ...). Pattern: ^[A-Za-z]{2}$. |
| incident_type |  | — | Exact incident type as OpenFEMA states it, e.g. `Typhoon`, `Hurricane`, `Severe Storm`, `Fire`, `Flood`, `Biological`. |
| declared_after |  | — | Only declarations on or after this date (YYYY-MM-DD). Pattern: ^\d{4}-\d{2}-\d{2}$. |
| declared_before |  | — | Only declarations on or before this date (YYYY-MM-DD). Pattern: ^\d{4}-\d{2}-\d{2}$. |

## What can you do with FEMA disaster declarations in dots?

Keep a FEMA disaster-history briefing current by checking for changed records and revised publications. Separate changes to declaration evidence from changes to the National Risk Index baseline used in an existing community analysis.

### County mitigation plan evidence

Build a declaration history for Harris County, Texas, inspect the records behind selected events, and add relevant OpenFEMA program data. Maintain the collection through updates and check dataset and National Risk Index publication status before revising the plan's evidence.

### Public disaster-history dashboard

Create a dashboard of declared events and designated areas for Florida. Collect the historical records, inspect selected rows, incorporate focused program queries, and maintain revisions; show publication checks alongside any separately maintained National Risk Index analysis.

### Regional business continuity review

Prepare a review of declared disasters affecting business locations in Texas and Louisiana. Use historical collections, focused searches, record inspection, and program queries to document the events, then check record revisions and publication changes before the next review.

### Maintain a disaster research collection

Maintain a research collection comparing California declaration history with selected OpenFEMA program records. Collect a baseline, inspect individual observations, apply supported updates, and track dataset and National Risk Index publication changes that could require rerunning the analysis.

### Check a declaration-area claim

Investigate which areas a particular disaster declaration includes. Search by disaster number, retrieve the selected records, and compare their designated areas before citing them in a report.

### Compare declaration history across states

Compare declared events in Texas, Louisiana, and Florida over a defined period. Collect every page and count distinct disaster numbers so declarations with more designated areas do not inflate the comparison.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All dots guides](https://spiral.ai/integrations/dots)

## FEMA disaster declarations in other agents

- [Amp](https://spiral.ai/integrations/amp/fema-disaster-declarations)
- [ChatGPT](https://spiral.ai/integrations/chatgpt/fema-disaster-declarations)
- [Claude](https://spiral.ai/integrations/claude-desktop/fema-disaster-declarations)
- [Claude Code](https://spiral.ai/integrations/claude-code/fema-disaster-declarations)
- [Cline](https://spiral.ai/integrations/cline/fema-disaster-declarations)
- [Codex](https://spiral.ai/integrations/codex/fema-disaster-declarations)
- [Cursor](https://spiral.ai/integrations/cursor/fema-disaster-declarations)
- [Devin](https://spiral.ai/integrations/devin/fema-disaster-declarations)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/fema-disaster-declarations)
- [Gemini](https://spiral.ai/integrations/gemini/fema-disaster-declarations)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/fema-disaster-declarations)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/fema-disaster-declarations)
- [goose](https://spiral.ai/integrations/goose/fema-disaster-declarations)
- [Grok](https://spiral.ai/integrations/grok/fema-disaster-declarations)
- [Grok Build](https://spiral.ai/integrations/grok-build/fema-disaster-declarations)
- [Hermes](https://spiral.ai/integrations/hermes/fema-disaster-declarations)
- [Instinct](https://spiral.ai/integrations/instinct/fema-disaster-declarations)
- [Manus](https://spiral.ai/integrations/manus/fema-disaster-declarations)
- [Muse](https://spiral.ai/integrations/muse/fema-disaster-declarations)
- [Muse Code](https://spiral.ai/integrations/muse-code/fema-disaster-declarations)
- [n8n](https://spiral.ai/integrations/n8n/fema-disaster-declarations)
- [Notion](https://spiral.ai/integrations/notion/fema-disaster-declarations)
- [OpenClaw](https://spiral.ai/integrations/openclaw/fema-disaster-declarations)
- [opencode](https://spiral.ai/integrations/opencode/fema-disaster-declarations)
- [Perplexity](https://spiral.ai/integrations/perplexity/fema-disaster-declarations)
- [Raycast](https://spiral.ai/integrations/raycast/fema-disaster-declarations)
- [VS Code](https://spiral.ai/integrations/vscode/fema-disaster-declarations)
- [Windsurf](https://spiral.ai/integrations/windsurf/fema-disaster-declarations)
- [Zapier](https://spiral.ai/integrations/zapier/fema-disaster-declarations)

## More dots guides

- [FEMA dataset field definitions](https://spiral.ai/integrations/dots/fema-dataset-field-definitions)
- [FEMA disaster details](https://spiral.ai/integrations/dots/fema-disaster-details)
- [FEMA dataset catalog](https://spiral.ai/integrations/dots/fema-dataset-catalog)
- [FEMA national recovery resources](https://spiral.ai/integrations/dots/fema-national-recovery-resources)
- [FEMA OpenFEMA records](https://spiral.ai/integrations/dots/fema-openfema-records)
- [FEMA recovery directory index](https://spiral.ai/integrations/dots/fema-recovery-directory-index)

## Questions about FEMA disaster declarations in dots

**Can dots use FEMA disaster declarations?**

Yes. Add Spiral to dots as an MCP server, and dots can find and run FEMA disaster declarations like any built-in tool.

**How much does FEMA disaster declarations cost in dots?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your dots plan is separate.

**Do I need an Alexandria account to use FEMA disaster declarations in dots?**

You need no Alexandria account. dots uses one Spiral API key for every tool, and Spiral runs FEMA disaster declarations on its own Alexandria account.

**How long does it take to set up FEMA disaster declarations in dots?**

About two minutes: create an API key, then send your dot this message, then give your dot the key.

**Does dots wait while FEMA disaster declarations runs?**

FEMA disaster declarations runs in the background. dots starts the run, checks on it and gives you the json when it's ready.

**How far back does FEMA's disaster history go?**

The declaration history starts in 1953. County information is unavailable before 1964, and FEMA describes historical Fire Management records as partial.

**Does one declaration record equal one disaster?**

No. Disaster Declarations Summaries is organized at the county level, so one disaster can appear in multiple records. Count distinct disaster numbers to count declarations.

**What geographic detail does the National Risk Index provide?**

The National Risk Index provides a baseline relative risk measurement for counties and Census tracts across 18 natural hazards. It describes community risk rather than an individual property's assessment.

**Does every OpenFEMA dataset follow the same update schedule?**

OpenFEMA publishes update frequency separately for each dataset. Its dataset metadata also identifies versions and deprecation status, so freshness should be checked against the particular dataset being analyzed.

**Can previously published FEMA records change?**

Yes. FEMA's official collection example checks whether a dataset has refreshed and then retrieves new or refreshed records. A declaration-history collection therefore needs to account for revisions as well as additions.

