# FEMA · Records list

Search public records with FEMA · Records list from Alexandria through one Spiral API key. Collect the whole of DisasterDeclarationsSummaries v2 (~71k rows, ~15 pages of 5,000), NfipClaims v3 by state, HmaSubapplications v2 or any other OpenFEMA dataset as records pinned to one publication; `query_dataset` is for ad-hoc filtered reads. It runs in the background and returns structured JSON. Pay as you go, with no subscription.

- Provider: Alexandria
- Category: Public Records
- Runs: In the background
- Returns: json
- Tool id: `alexandria` / `fema-gov/us-disaster-assistance/records_list`
- Page: https://spiral.ai/tools/alexandria/fema-gov/us-disaster-assistance/records_list

## Pricing

$0.00873 per call.

## Limits

- Longest queue wait: 1 hour
- Run deadline: 5 minutes
- Longest run, end to end: 225 minutes
- Largest inline input: 1 MB
- Largest input file: 2 GB
- Largest output: 5 GB

## Input

| Field | Kind | Allowed | Default | Description |
| --- | --- | --- | --- | --- |
| `dataset` (required) | text |  | — | OpenFEMA entity name (case sensitive), e.g. `DisasterDeclarationsSummaries`, `NfipClaims`, `HmaSubapplications`. Pattern: ^[A-Za-z][A-Za-z0-9]*$. |
| `version` (required) | number | 1 to 20 | — | version |
| `year` | number | 1900 to 2100 | — | Calendar year (UTC) of `year_field`. |
| `cursor` | text |  | — | `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` | number | 1 to 5000 | 1000 | Rows per page (OpenFEMA $top). |
| `year_field` | text |  | — | Date field of a calendar-year segment, e.g. `policyEffectiveDate`, `declarationDate`. Requires `year`. Pattern: ^[A-Za-z][A-Za-z0-9_]*$. |
| `segment_field` | text |  | — | Field of an equality segment, e.g. `state` (NfipClaims), `propertyState` (NfipPolicies). Requires `segment_value`. Pattern: ^[A-Za-z][A-Za-z0-9_]*$. |
| `segment_value` | text |  | — | String value of the segment, e.g. `TX`. Requires `segment_field`. |

## Example

```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
    }
  }'
```

Try it in the Playground: https://spiral.ai/start?provider=alexandria&model=fema-gov%2Fus-disaster-assistance%2Frecords_list

## Common questions

### FEMA · Records list

**How much does FEMA · Records list cost?**

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

**How do I use FEMA · Records list through an API?**

Send `POST /v1/runs` with `"provider": "alexandria"`, `"model": "fema-gov/us-disaster-assistance/records_list"` and the input fields on this page, using one Spiral API key. It runs in the background: poll the run, or name a webhook to be told when it finishes.

**Do I need an account with Alexandria to use FEMA · Records list?**

No. Spiral runs it on its own Alexandria account and charges your Spiral balance.

**Can my AI agent use FEMA · Records list?**

Yes. Agents find and run it through Spiral's MCP server, CLI or agent skill, with the same API key.

