[Integrations](https://spiral.ai/integrations) › [opencode](https://spiral.ai/integrations/opencode) › [NASA FIRMS fire file status](https://spiral.ai/integrations/opencode/nasa-firms-fire-file-status)

# How to Use NASA FIRMS fire file status in opencode

Returns status information for FIRMS regional fire files so you can check whether a file changed. Use it to decide when to refresh a map or regional download.

|  |  |
| --- | --- |
| Model | NASA FIRMS fire file status |
| Available through | Alexandria |
| Category | Public Records |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with NASA FIRMS fire file status in opencode

- Use NASA FIRMS fire file status to check Europe's NOAA-21 files and add a comparison against the previous result in our refresh job.
- Use NASA FIRMS fire file status to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from NASA FIRMS fire file status and tell me what changed since last week.
- Check NASA FIRMS fire file status and summarize what you find in three bullet points.
- Pull the newest data from NASA FIRMS fire file status and give me the result as a table.

## How to set up NASA FIRMS fire file status 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 NASA FIRMS fire file status**: 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": "firms-modaps-eosdis-nasa-gov/wildfire-detections/source_status",
    "input": {
      "region": "Global"
    }
  }'
```

Then paste one of the prompts above: opencode finds NASA FIRMS fire file status on Spiral, shows the price and runs it.

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

## NASA FIRMS fire file status tools and prices

- [NASA FIRMS active fire detections · Source status](https://spiral.ai/tools/alexandria/firms-modaps-eosdis-nasa-gov/wildfire-detections/source_status) (Alexandria): $0.00873 per call.

## Settings you can ask for

| Setting | Allowed values | Default | Description |
| --- | --- | --- | --- |
| region | Global, Canada, Alaska, USA_contiguous_and_Hawaii, Central_America, South_America, Europe, Northern_and_Central_Africa, Southern_Africa, Russia_Asia, South_Asia, SouthEast_Asia, Australia_NewZealand | Global | File region stem (from /api/coordinates/all). Default Global. |
| sensor | suomi-npp-viirs-c2, noaa-20-viirs-c2, noaa-21-viirs-c2, modis-c6.1, landsat | — | File family (path segment under /data/active_fire/). Omitted: every sensor that publishes the region (landsat only publishes Canada and USA_contiguous_and_Hawaii). |
| window | 24h, 48h, 7d | — | Rolling window of the file. Omitted: all three. |

## What can you do with NASA FIRMS fire file status in opencode?

Build a map of recent satellite hotspots with acquisition times, sensor labels, and confidence. A coding agent can connect FIRMS observations and file checks to the project's map and data-refresh code.

### Prepare a park activity brief

Check whether the regional file changed, collect recent detections around Yosemite National Park, and summarize observation times and confidence for an analyst.

### Refresh a regional hotspot map

Check Canada's fire files for changes, download regional detections, and inspect selected areas around Jasper. Show satellite observations as points rather than drawing inferred fire boundaries.

### Build a newsroom research brief

Check for revised source files, collect regional observations, and examine the reported location of a public fire event. Separate satellite detection times from claims about when the incident began.

### Compare sensor observations

Check the available MODIS and VIIRS files, compare regional detections, and inspect a shared area around Yellowstone. Keep each sensor's pixel size and observation time visible.

### Maintain a recent observation dataset

Check regional file changes before refreshing a stored dataset. Collect all regional pages and use local queries to examine selected public parks or research areas.

### Teach satellite sampling limits

Use recent detections near Jasper and the wider Canadian region to demonstrate observation gaps and different pixel sizes. Include a file-status check to distinguish source revisions from changes in the observations being compared.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All opencode guides](https://spiral.ai/integrations/opencode)

## NASA FIRMS fire file status in other agents

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

## More opencode guides

- [NASA Exoplanet Archive planetary system](https://spiral.ai/integrations/opencode/nasa-exoplanet-archive-planetary-system)
- [NASA FIRMS local fire detections](https://spiral.ai/integrations/opencode/nasa-firms-local-fire-detections)
- [NASA Exoplanet Archive planet search](https://spiral.ai/integrations/opencode/nasa-exoplanet-archive-planet-search)
- [NASA FIRMS regional fire detections](https://spiral.ai/integrations/opencode/nasa-firms-regional-fire-detections)
- [NASA Exoplanet Archive planet details](https://spiral.ai/integrations/opencode/nasa-exoplanet-archive-planet-details)
- [NASA Sentry asteroid impact details](https://spiral.ai/integrations/opencode/nasa-sentry-asteroid-impact-details)

## Questions about NASA FIRMS fire file status in opencode

**Can opencode use NASA FIRMS fire file status?**

Yes. Add Spiral to opencode as an MCP server, and opencode can find and run NASA FIRMS fire file status like any built-in tool.

**How much does NASA FIRMS fire file status 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 NASA FIRMS fire file status in opencode?**

No. Spiral runs NASA FIRMS fire file status on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up NASA FIRMS fire file status in opencode?**

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

**Does opencode wait while NASA FIRMS fire file status runs?**

NASA FIRMS fire file status runs in the background. opencode starts the run, checks on it and gives you the json when it's ready.

**How quickly does FIRMS publish satellite observations?**

NASA says global near real-time active fire data are available within three hours of satellite observation. That interval starts at observation, so it does not describe the time since a fire began.

**How precise are FIRMS detection locations?**

MODIS detections represent approximately 1 km pixels, while VIIRS detections represent approximately 375 m pixels. A detection does not mean the entire pixel is burning.

**Does an empty result mean there was no fire?**

No. NASA documents missed detections when a fire starts and ends between satellite overpasses; heavy cloud or smoke can also hide activity.

**Can FIRMS detections be counted as separate wildfires?**

No. FIRMS reports thermal anomalies at the pixel level, and NASA identifies hot smoke, agriculture, and other sources among their possible causes. These records do not provide a count of confirmed wildfire incidents.

**Where does NASA provide older fire data?**

NASA directs requests for detections older than seven days to its separate archive download. That archive is distinct from the recent regional files.

