How to Use NIFC fire perimeter history in Claude Code
Find recorded fire perimeters intersecting or near an area over a historical window. Use it to investigate past fire footprints, keeping NIFC's incomplete coverage before 2021 in mind.
Prompts to try with NIFC fire perimeter history in Claude Code
Copy an example into Claude Code, or ask in your own words.
Use NIFC fire perimeter history to find recorded perimeters within 10 kilometers of Paradise, California, from 2021 through 2025, and add the results to this project's history view.
Use NIFC fire perimeter history for the Lake Tahoe Basin boundary in this project's GeoJSON files, covering 2021 through 2025, and render the returned recorded footprints on the map.
Use NIFC fire perimeter history to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from NIFC fire perimeter history and tell me what changed since last week.
Check NIFC fire perimeter history and summarize what you find in three bullet points.
How to set up NIFC fire perimeter history in Claude Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Add the hosted server
This adds Spiral to the current project. Add --scope user to use it in every project.
claude mcp add --transport http spiral https://api.spiral.ai/mcp
- Sign in
Start claude, type /mcp, choose spiral and Authenticate. Sign in to Spiral in the browser and click Authorize. No API key.
Use the Spiral skill
- Send Claude 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 NIFC fire perimeter history
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": "data-nifc-opendata-arcgis-com/wildfire-incidents-perimeters/fire_history_for_geometry", "input": { "geometry": {} } }'
Then paste one of the prompts above: Claude Code finds NIFC fire perimeter history on Spiral, shows the price and runs it.
NIFC fire perimeter history providers and prices
Spiral runs NIFC fire perimeter history through Alexandria. Open a card for today's price, with every fee included.
$0.00873 per call.
Settings you can ask for
Ask Claude Code for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Buffer km | 0 to 50 | 0 | Also return perimeters within this many kilometres of the geometry (default 0: intersecting only). |
Every API field of NIFC Open Data (WFIGS wildfire incidents and perimeters) · Fire history for geometry is on its tool page: open its card above.
What can you do with NIFC fire perimeter history in Claude Code?
Build a map that connects NIFC incident reports with available fire footprints and recorded history. A coding agent can add those records to your project and make missing perimeters and incomplete older coverage clear.
Prepare a park fire briefing
Combine nearby active incidents, newly discovered fires, recorded perimeter history, and details for selected incidents into a briefing for a national park operations team.
Review fires around a public reservoir
Give watershed staff a list of current and newly discovered incidents around a reservoir, historical perimeter intersections, and individual fire records to investigate.
Build a county wildfire reporting desk
Help reporters find new incidents, check ongoing fires, retrieve individual records, and add recorded historical fire footprints to local coverage.
Review a commercial forestry area
Assemble current nearby fire activity, new discoveries, historical mapped footprints, and selected incident details for a forestry team's area review.
Compare recorded fire footprints
Find historical perimeters intersecting a restoration area, then retrieve available geometry for selected incidents to compare their mapped footprints.
Add fire history to a public land map
Overlay recorded historical perimeters on a public land boundary and let readers inspect selected incident records. Explain the incomplete perimeter coverage before 2021.
More on NIFC fire perimeter history and Claude Code
Overview
NIFC fire perimeter history in other agents
Questions about NIFC fire perimeter history in Claude Code
Can Claude Code use NIFC fire perimeter history?
Yes. Add Spiral to Claude Code as an MCP server, and Claude Code can find and run NIFC fire perimeter history like any built-in tool.
How much does NIFC fire perimeter history cost in Claude 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 Claude Code plan is separate.
Do I need an Alexandria account to use NIFC fire perimeter history in Claude Code?
No. Spiral runs NIFC fire perimeter history on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up NIFC fire perimeter history in Claude Code?
About two minutes: add the hosted server, then sign in.
Does Claude Code wait while NIFC fire perimeter history runs?
NIFC fire perimeter history runs in the background. Claude Code starts the run, checks on it and gives you the json when it's ready.
What geographic area does NIFC cover?
NIFC's current incident locations cover recent and ongoing wildland fires in the United States. This source does not establish worldwide fire coverage.
How fresh are the mapped fire perimeters?
NIFC documents refreshes every five minutes, with changes in the perimeter source taking up to 15 minutes to appear. That refresh schedule describes publication timing, not a guarantee that each fire has just been remapped.
How complete is the historical fire coverage?
NIFC says its consolidated perimeter history is incomplete before 2021 and continues to incorporate older data. The incident location service documents coverage back to 2014, so incident history and mapped perimeter history have different boundaries.
Does every reported fire have a public perimeter?
No. NIFC explicitly says perimeters are unavailable for some incidents, and perimeters without approval for public distribution are excluded from the public WFIGS dataset.
Does disappearance from the current feed mean a fire is out?
Disappearance alone does not establish that a fire is out. The current perimeter service also removes stale records, including fires larger than 100 acres whose information has not been updated for more than 14 days.
Start using NIFC fire perimeter history in Claude Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Claude Code:
set up https://spiral.ai/SKILL.md


