How to Use FEMA OpenFEMA records in Muse Code
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.
Prompts to try with FEMA OpenFEMA records in Muse Code
Copy an example into Muse Code, or ask in your own words.
Use FEMA OpenFEMA records to collect the California declaration-history baseline for 2020 through 2024 and save the returned records in the project's data directory.
Use FEMA OpenFEMA records to look this up and give me the result as a table. Save the result in ./assets.
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 Muse Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Install Muse Code
curl -fsSL https://dev.meta.ai/install.sh | bash
- Ask Muse to add the server
Start muse and ask:
Add the Spiral MCP server at https://api.spiral.ai/mcp
- Sign in
In your terminal, run:
muse mcp login spiral
Use the Spiral skill
- Send Muse Code this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run FEMA OpenFEMA records
One request; the result comes back by polling or a webhook.
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: Muse Code finds FEMA OpenFEMA records on Spiral, shows the price and runs it.
FEMA OpenFEMA records providers and prices
Spiral runs FEMA OpenFEMA records through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Muse Code for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Version | 1 to 20 | version | |
| Year | 1900 to 2100 | Calendar year (UTC) of | |
| Page size | 1 to 5000 | 1000 | Rows per page (OpenFEMA $top). |
Every API field of FEMA · Records list is on its tool page: open its card above.
What can you do with FEMA OpenFEMA records in Muse Code?
Build a county disaster-history report that keeps designated areas separate from distinct declarations. Add collection updates and publication checks so the project's FEMA evidence can be refreshed when its source data changes.
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.
More on FEMA OpenFEMA records and Muse Code
Overview
FEMA OpenFEMA records in other agents
Questions about FEMA OpenFEMA records in Muse Code
Can Muse Code use FEMA OpenFEMA records?
Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run FEMA OpenFEMA records like any built-in tool.
How much does FEMA OpenFEMA records cost in Muse Code?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.
Do I need an Alexandria account to use FEMA OpenFEMA records in Muse Code?
No. Spiral runs FEMA OpenFEMA records on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up FEMA OpenFEMA records in Muse Code?
About two minutes: install Muse Code, then ask Muse to add the server, then sign in.
Does Muse Code wait while FEMA OpenFEMA records runs?
FEMA OpenFEMA records runs in the background. Muse Code 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.
Start using FEMA OpenFEMA records in Muse Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Muse Code:
set up https://spiral.ai/SKILL.md


