[Integrations](https://spiral.ai/integrations) › [dots](https://spiral.ai/integrations/dots) › [FEMA OpenFEMA records](https://spiral.ai/integrations/dots/fema-openfema-records)

# How to Use FEMA OpenFEMA records in dots

Returns pages of records from a selected OpenFEMA dataset. Use it to collect a historical baseline or a state or year segment for analysis, then maintain supported datasets through record updates.

|  |  |
| --- | --- |
| Model | FEMA OpenFEMA records |
| 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 OpenFEMA records in dots

- At the start of each month, use FEMA OpenFEMA records to collect California declarations made during the previous month and report distinct disaster numbers separately from area records.
- Every Monday at 9am: use FEMA OpenFEMA records to look this up and give me the result as a table.
- Pull the latest numbers from FEMA OpenFEMA records and tell me what changed since last week.
- Check FEMA OpenFEMA records and summarize what you find in three bullet points.
- Pull the newest data from FEMA OpenFEMA records and give me the result as a table.

## How to set up FEMA OpenFEMA records 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 OpenFEMA records**: 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/records_list",
    "input": {
      "dataset": "<dataset>",
      "version": 1
    }
  }'
```

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

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

## FEMA OpenFEMA records tools and prices

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

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| year | 1900 to 2100 | — | Calendar year (UTC) of `year_field`. |
| cursor |  | — | `next_cursor` of the previous page: `v1:<skip>:<total>:<segment tag>:<publication_id>`. Must be used with the same dataset, version and segment inputs. |
| page_size | 1 to 5000 | 1000 | Rows per page (OpenFEMA $top). |
| year_field |  | — | Date field of a calendar-year segment, e.g. `policyEffectiveDate`, `declarationDate`. Requires `year`. Pattern: ^[A-Za-z][A-Za-z0-9_]*$. |
| segment_field |  | — | Field of an equality segment, e.g. `state` (NfipClaims), `propertyState` (NfipPolicies). Requires `segment_value`. Pattern: ^[A-Za-z][A-Za-z0-9_]*$. |
| segment_value |  | — | String value of the segment, e.g. `TX`. Requires `segment_field`. |

## What can you do with FEMA OpenFEMA records 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.

### 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 OpenFEMA records in other agents

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

## More dots guides

- [FEMA OpenFEMA record updates](https://spiral.ai/integrations/dots/fema-openfema-record-updates)
- [FEMA dataset catalog](https://spiral.ai/integrations/dots/fema-dataset-catalog)
- [FEMA OpenFEMA record details](https://spiral.ai/integrations/dots/fema-openfema-record-details)
- [FEMA dataset field definitions](https://spiral.ai/integrations/dots/fema-dataset-field-definitions)
- [FEMA OpenFEMA dataset status](https://spiral.ai/integrations/dots/fema-openfema-dataset-status)
- [FEMA disaster declarations](https://spiral.ai/integrations/dots/fema-disaster-declarations)

## Questions about FEMA OpenFEMA records in dots

**Can dots use FEMA OpenFEMA records?**

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

**How much does FEMA OpenFEMA records 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 OpenFEMA records in dots?**

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

**How long does it take to set up FEMA OpenFEMA records 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 OpenFEMA records runs?**

FEMA OpenFEMA records 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.

