[Integrations](https://spiral.ai/integrations) › [Muse Code](https://spiral.ai/integrations/muse-code) › [NIFC fire perimeter history](https://spiral.ai/integrations/muse-code/nifc-fire-perimeter-history)

# How to Use NIFC fire perimeter history in Muse 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.

|  |  |
| --- | --- |
| Model | NIFC fire perimeter history |
| Available through | Alexandria |
| Category | Listings |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with NIFC fire perimeter history in Muse Code

- 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 Muse Code

Pick the way that suits you. Each takes about two minutes.

### Use Spiral's MCP server

1. **Install Muse Code**

```bash
curl -fsSL https://dev.meta.ai/install.sh | bash
```

2. **Ask Muse to add the server**: Start `muse` and ask:

```text
Add the Spiral MCP server at https://api.spiral.ai/mcp
```

3. **Sign in**: In your terminal, run:

```bash
muse mcp login spiral
```

### Use the Spiral skill

1. **Send Muse Code 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 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 NIFC fire perimeter history**: 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": "data-nifc-opendata-arcgis-com/wildfire-incidents-perimeters/fire_history_for_geometry",
    "input": {
      "geometry": {}
    }
  }'
```

Then paste one of the prompts above: Muse Code finds NIFC fire perimeter history on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/muse-code

## NIFC fire perimeter history tools and prices

- [NIFC Open Data (WFIGS wildfire incidents and perimeters) · Fire history for geometry](https://spiral.ai/tools/alexandria/data-nifc-opendata-arcgis-com/wildfire-incidents-perimeters/fire_history_for_geometry) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| end |  | — | Last day of the window, YYYY-MM-DD (default today). Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
| start |  | — | First day of the window, YYYY-MM-DD (default 20 years before end). The historic view is filtered by fire year. Pattern: ^[0-9]{4}-[0-9]{2}-[0-9]{2}$. |
| buffer_km | 0 to 50 | 0 | Also return perimeters within this many kilometres of the geometry (default 0: intersecting only). |

## What can you do with NIFC fire perimeter history in Muse 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.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Muse Code guides](https://spiral.ai/integrations/muse-code)

## NIFC fire perimeter history in other agents

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

## More Muse Code guides

- [NIFC active fires near a location](https://spiral.ai/integrations/muse-code/nifc-active-fires-near-a-location)
- [NIFC newly discovered fires](https://spiral.ai/integrations/muse-code/nifc-newly-discovered-fires)
- [NASA POWER weather parameter catalog](https://spiral.ai/integrations/muse-code/nasa-power-weather-parameter-catalog)
- [NIFC wildfire incident details](https://spiral.ai/integrations/muse-code/nifc-wildfire-incident-details)
- [NASA POWER root-zone soil wetness](https://spiral.ai/integrations/muse-code/nasa-power-root-zone-soil-wetness)
- [NWS active weather alerts](https://spiral.ai/integrations/muse-code/nws-active-weather-alerts)

## Questions about NIFC fire perimeter history in Muse Code

**Can Muse Code use NIFC fire perimeter history?**

Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run NIFC fire perimeter history like any built-in tool.

**How much does NIFC fire perimeter history 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 NIFC fire perimeter history in Muse 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 Muse Code?**

About two minutes: install Muse Code, then ask Muse to add the server, then sign in.

**Does Muse Code wait while NIFC fire perimeter history runs?**

NIFC fire perimeter history runs in the background. Muse 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.

