[Integrations](https://spiral.ai/integrations) › [opencode](https://spiral.ai/integrations/opencode) › [NIFC wildfire incident details](https://spiral.ai/integrations/opencode/nifc-wildfire-incident-details)

# How to Use NIFC wildfire incident details in opencode

Retrieve one incident's reported record and available perimeter geometry using its fire identifier. Use it to follow up a search result and examine that fire's acreage, containment, and mapped footprint.

|  |  |
| --- | --- |
| Model | NIFC wildfire incident details |
| 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 wildfire incident details in opencode

- Use NIFC wildfire incident details with the fire identifier returned for the largest reported incident near Redding, California, and add its available perimeter geometry to the selected-fire view.
- Use NIFC wildfire incident details to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from NIFC wildfire incident details and tell me what changed since last week.
- Check NIFC wildfire incident details and summarize what you find in three bullet points.
- Pull the newest data from NIFC wildfire incident details and give me the result as a table.

## How to set up NIFC wildfire incident details in opencode

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

### Use Spiral's MCP server

1. **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.

```bash
opencode mcp add spiral --global --url https://api.spiral.ai/mcp
```

2. **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.

```bash
opencode mcp auth spiral
```

3. **Check it**: Spiral shows as connected.

```bash
opencode mcp list
```

### Use the Spiral skill

1. **Send opencode 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 wildfire incident details**: 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/incident_detail",
    "input": {
      "irwin_id": "<irwin_id>"
    }
  }'
```

Then paste one of the prompts above: opencode finds NIFC wildfire incident details on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/opencode

## NIFC wildfire incident details tools and prices

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

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| irwin_id |  | — | IRWIN GUID, with or without braces, e.g. {C63FC371-BC70-4615-841B-B0838C21064F}. |
| unique_fire_id |  | — | UniqueFireIdentifier, e.g. 2021-COBLX-000995. |
| include_perimeter_geometry |  | — | Return the perimeter's GeoJSON geometry (can be hundreds of KB for large fires). |

## What can you do with NIFC wildfire incident details in opencode?

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.

### Create a new fire discovery digest

List newly discovered incidents near a public recreation area and retrieve details for the fires an operations team wants to review.

### Review reported acreage and containment changes

Compare successive records for active incidents near a business site and identify changes in reported fire size or containment for staff review.

### 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 opencode guides](https://spiral.ai/integrations/opencode)

## NIFC wildfire incident details in other agents

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

## More opencode guides

- [NIFC newly discovered fires](https://spiral.ai/integrations/opencode/nifc-newly-discovered-fires)
- [NWS active weather alerts](https://spiral.ai/integrations/opencode/nws-active-weather-alerts)
- [NIFC fire perimeter history](https://spiral.ai/integrations/opencode/nifc-fire-perimeter-history)
- [NWS daily weather forecast](https://spiral.ai/integrations/opencode/nws-daily-weather-forecast)
- [NIFC active fires near a location](https://spiral.ai/integrations/opencode/nifc-active-fires-near-a-location)
- [NWS hourly weather forecast](https://spiral.ai/integrations/opencode/nws-hourly-weather-forecast)

## Questions about NIFC wildfire incident details in opencode

**Can opencode use NIFC wildfire incident details?**

Yes. Add Spiral to opencode as an MCP server, and opencode can find and run NIFC wildfire incident details like any built-in tool.

**How much does NIFC wildfire incident details 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 NIFC wildfire incident details in opencode?**

No. Spiral runs NIFC wildfire incident details 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 wildfire incident details in opencode?**

About two minutes: add the server, then sign in, then check it.

**Does opencode wait while NIFC wildfire incident details runs?**

NIFC wildfire incident details runs in the background. opencode 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.

