How to Use FEMA OpenFEMA record updates in opencode
Returns records changed since an earlier collection from datasets that support updates. Use it to maintain a disaster-history database and catch revisions to existing records.
Prompts to try with FEMA OpenFEMA record updates in opencode
Copy an example into opencode, or ask in your own words.
Use FEMA OpenFEMA record updates to retrieve declaration records changed since November 1, 2026, and update this project's existing collection while preserving each record's ID.
Use FEMA OpenFEMA record updates to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from FEMA OpenFEMA record updates and tell me what changed since last week.
Check FEMA OpenFEMA record updates and summarize what you find in three bullet points.
Pull the newest data from FEMA OpenFEMA record updates and give me the result as a table.
How to set up FEMA OpenFEMA record updates in opencode
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the server
Leave out --global to add Spiral to the current project only. No header and no client ID or secret: opencode registers itself with Spiral.
opencode mcp add spiral --global --url https://api.spiral.ai/mcp
- Sign in
Your browser opens. Sign in to Spiral, pick the organization and click Authorize, then return to the terminal. No API key. Inside opencode, /mcps starts the same sign-in.
opencode mcp auth spiral
- Check it
Spiral shows as connected.
opencode mcp list
Use the Spiral skill
- Send opencode 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 record updates
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_changes", "input": { "since": "<since>", "dataset": "<dataset>", "version": 1 } }'
Then paste one of the prompts above: opencode finds FEMA OpenFEMA record updates on Spiral, shows the price and runs it.
FEMA OpenFEMA record updates providers and prices
Spiral runs FEMA OpenFEMA record updates through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask opencode for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Version | 1 to 20 | version | |
| Page size | 1 to 5000 | 1000 | page_size |
Every API field of FEMA · Records changes is on its tool page: open its card above.
What can you do with FEMA OpenFEMA record updates in opencode?
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.
More on FEMA OpenFEMA record updates and opencode
Overview
FEMA OpenFEMA record updates in other agents
Questions about FEMA OpenFEMA record updates in opencode
Can opencode use FEMA OpenFEMA record updates?
Yes. Add Spiral to opencode as an MCP server, and opencode can find and run FEMA OpenFEMA record updates like any built-in tool.
How much does FEMA OpenFEMA record updates cost in opencode?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your opencode plan is separate.
Do I need an Alexandria account to use FEMA OpenFEMA record updates in opencode?
No. Spiral runs FEMA OpenFEMA record updates 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 record updates in opencode?
About two minutes: add the server, then sign in, then check it.
Does opencode wait while FEMA OpenFEMA record updates runs?
FEMA OpenFEMA record updates runs in the background. opencode 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 record updates in opencode
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into opencode:
set up https://spiral.ai/SKILL.md


