Spiral gives your agent every tool with one account. Browse the tools →

Muse Code · Listings

How to Use NIFC wildfire incident details in Muse Code

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.

Prompts to try with NIFC wildfire incident details in Muse Code

Copy an example into Muse Code, or ask in your own words.

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.

NIFC wildfire incident detailsMuse Code
Try asking
  • 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 Muse Code

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

Use Spiral's MCP server

  1. Install Muse Code
    curl -fsSL https://dev.meta.ai/install.sh | bash
  2. Ask Muse to add the server

    Start muse and ask:

    Add the Spiral MCP server at https://api.spiral.ai/mcp
  3. Sign in

    In your terminal, run:

    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.

    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.

    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: Muse Code finds NIFC wildfire incident details on Spiral, shows the price and runs it.

NIFC wildfire incident details providers and prices

Spiral runs NIFC wildfire incident details through Alexandria. Open a card for today's price, with every fee included.

AlexandriaListings
NIFC Open Data (WFIGS wildfire incidents and perimeters) · Incident detail
data-nifc-opendata-arcgis-com/wildfire-incidents-perimeters/incident_detail

Settings you can ask for

Ask Muse Code for any of these in your prompt.

SettingAllowed valuesDefaultDescription
Include perimeter geometryon or off

Return the perimeter's GeoJSON geometry (can be hundreds of KB for large fires).

Every API field of NIFC Open Data (WFIGS wildfire incidents and perimeters) · Incident detail is on its tool page: open its card above.

What can you do with NIFC wildfire incident details 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.

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.

Questions about NIFC wildfire incident details in Muse Code

Can Muse Code use NIFC wildfire incident details?

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

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

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

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

Does Muse Code wait while NIFC wildfire incident details runs?

NIFC wildfire incident details 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.

Get started

Start using NIFC wildfire incident details 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 Muse Code

set up https://spiral.ai/SKILL.md
Are you an AI agent? See setup options