# US Wildfire Incidents & History Since 2014 (NIFC, Radius) (`bigsky-data-tools/us-wildfire-incidents-tracker`) Actor

Live US wildfire incidents plus history since 2014 (430,000+ records) from NIFC: radius search around any property, several states per run, acres, containment, cost, personnel and a plain status (active, contained, out). Schedule hourly for alerts.

- **URL**: https://apify.com/bigsky-data-tools/us-wildfire-incidents-tracker.md
- **Developed by:** [BigSky Data Tools](https://apify.com/bigsky-data-tools) (community)
- **Categories:** News, Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## US Wildfire Incidents Tracker: Wildfire data from NIFC (Multi-State, Radius Search, History Since 2014)

Get **US wildfire and prescribed-fire incidents** from **National Interagency Fire Center (NIFC) WFIGS** public data in one clean table: fire name, acres burned, % containment, discovery and containment dates, cause, personnel, estimated cost, county, landowner category (not names), and coordinates. **No API key, no login.**

> **NOT FOR SAFETY-CRITICAL USE: data may be delayed or incomplete; not for life-safety, navigation or emergency decisions; use official sources: the National Interagency Fire Center (NIFC) WFIGS service, InciWeb and local fire authorities.**

### Why this wildfire scraper?

- 🗺️ **Radius search**: "every wildfire within 50 miles of this property, ranch, power line or town". Each row has `distanceMiles`.
- 🇺🇸 **Several states in one run**: MT, ID, WY, CA, OR, WA, CO, and more.
- 📜 **History since 2014**: over 430,000 incident records, filterable by date range. Use it for underwriting, risk scoring and research.
- 🔥 **Live feed**: current incidents refreshed by NIFC throughout the day. Schedule it hourly to get alerts.
- 🧯 Wildfires (WF), prescribed burns (RX) and complexes (CX), with a minimum-acre filter.
- 🚦 **`status` in plain words**: `active`, `contained`, `controlled` or `out`, worked out from the containment, control and out dates.

### How it compares

| | This tool | Typical alternatives |
|---|---|---|
| History | **Since 2014, 430,000+ records** | Active incidents only |
| Radius search | **Yes** | Yes (some tools) |
| Several states per run | **Yes** | Usually one state or country |
| Plain-word status | **Yes** | Varies |

### Who uses it

Insurance underwriters and adjusters, utilities and grid operators, real-estate and land buyers, ranchers and farm lenders, journalists, emergency managers, researchers and GIS teams.

### Input example

```json
{ "source": "history", "latitude": "45.7833", "longitude": "-108.5007", "radiusMiles": 50,
  "incidentTypes": ["WF"], "minAcres": 100, "discoveredAfter": "2020-01-01" }
```

### Output example

```json
{ "incidentName": "BO", "uniqueFireId": "2024-MT...", "incidentType": "WF", "acres": 250.68,
  "percentContained": 100, "discoveredAt": "2024-06-29T18:53:00+00:00", "state": "MT",
  "county": "Yellowstone", "cause": "...", "personnel": null, "estimatedCostUsd": null,
  "latitude": 45.8, "longitude": -108.4, "distanceMiles": 5.3, "source": "NIFC WFIGS (public domain)" }
```

You can export to JSON, CSV, Excel or XML, or call it from the Apify API, Make, Zapier or n8n.

### Pricing

**$7 per 1,000 results** ($0.007 per result) plus a $0.01 start fee per run.

You pay per incident saved. A typical state's current wildfires cost a few cents.

### FAQ

**Where does the data come from?** From the public WFIGS ArcGIS feed published by NIFC. It is US government data and generally in the public domain. You are responsible for how you use the data.
**How fresh is it?** The current feed is refreshed from the source on each run; upstream delays apply. History covers 2014 to today.
**Does it include fire perimeters?** This version returns point locations. Perimeter polygons are on the roadmap.
**Is this tool run by the data agency?** No. BigSky Data Tools is independent and not affiliated with or endorsed by NIFC. Do not use it for life-safety decisions; follow local authorities.

# Actor input Schema

## `source` (type: `string`):

Live WFIGS current feed or the full incident history.

## `states` (type: `array`):

Two-letter US state codes, e.g. MT, ID, WY. Leave empty for all states.

## `latitude` (type: `string`):

Optional. With longitude and radius, returns only fires near this point (e.g. 45.7833 for Billings, MT).

## `longitude` (type: `string`):

Optional, e.g. -108.5007.

## `radiusMiles` (type: `integer`):

Search radius around the center point.

## `incidentTypes` (type: `array`):

WF = wildfire, RX = prescribed fire, CX = complex.

## `minAcres` (type: `integer`):

Skip incidents smaller than this.

## `discoveredAfter` (type: `string`):

YYYY-MM-DD. Optional.

## `discoveredBefore` (type: `string`):

YYYY-MM-DD. Optional.

## `maxResults` (type: `integer`):

Maximum incidents to save (each saved incident is one billable result).

## Actor input object example

```json
{
  "source": "current",
  "states": [
    "MT"
  ],
  "radiusMiles": 50,
  "incidentTypes": [
    "WF"
  ],
  "minAcres": 0,
  "maxResults": 1000
}
```

# Actor output Schema

## `dataset` (type: `string`):

Default dataset containing all output records

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "states": [
        "MT"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("bigsky-data-tools/us-wildfire-incidents-tracker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "states": ["MT"] }

# Run the Actor and wait for it to finish
run = client.actor("bigsky-data-tools/us-wildfire-incidents-tracker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "states": [
    "MT"
  ]
}' |
apify call bigsky-data-tools/us-wildfire-incidents-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,bigsky-data-tools/us-wildfire-incidents-tracker"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Ha3d50QSmIegg7BEn/builds/hno83tFh4zNmgdp1w/openapi.json