# NIFC Wildfire Incidents Scraper (`acquistion-automation/nifc-wildfire-incidents-scraper`) Actor

Scrapes active wildfire incidents from the NIFC public feed. Returns each fire as a flat row with its name, acreage, containment percentage, location, and discovery date. Filter by US state and minimum fire size.

- **URL**: https://apify.com/acquistion-automation/nifc-wildfire-incidents-scraper.md
- **Developed by:** [Acquisition Automation Co.](https://apify.com/acquistion-automation) (community)
- **Categories:** Business, Automation, Integrations
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $7.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

![Acquisition Automation Co. Search less. Close more.](https://api.apify.com/v2/key-value-stores/AOdPHdOpeDpzEPS5f/records/banner.jpg)

## 🔥 NIFC Wildfire Incidents Scraper

> **Fire incidents from the National Interagency Fire Center feed, one per row, with name, state, county, coordinates, discovery date, cause and incident type.** Filter by state or minimum size, cap the run, export to CSV, Excel, JSON or XML. No API key and no registration.

The NIFC feed is the federal record of fire incidents across the United States, including both wildfires and planned prescribed burns. It is served for mapping software, not for a spreadsheet. This Actor reads it and writes each incident into a dataset, so the fire history around a property becomes a table you can filter by county.

| Who uses it | What they use the feed for |
|---|---|
| 🏢 Buyers of businesses with physical sites | Checking the fire history around a plant, a yard or a portfolio of locations before the insurance quote arrives |
| 🌲 Buyers of land, timber and agriculture | Seeing what has burned nearby, and how recently |
| 📋 Insurance and risk analysts | Building a county level incident history with coordinates attached |
| 🏛 Local government and researchers | Tracking incident counts by state and county over a season |

### 📋 What it does

> 💡 **Why it matters:** fire exposure shows up in the insurance premium, and the premium shows up in EBITDA. The federal incident feed is the cheapest way to check the ground truth around an address.

- 🗺 **Reads the NIFC public incident feed** with no account and no key.
- 🏷 **Filters by state code**, for example `CA`, `OR` or `TX`.
- 📏 **Filters by minimum acreage**, for runs where only larger fires matter.
- 📍 **Returns latitude and longitude**, so you can measure distance to a specific site.
- 🔥 **Marks the incident type** in `status`: `WF` for a wildfire, `RX` for a prescribed burn.
- 💾 **Exports to CSV, Excel, JSON or XML**, from the run page or the API.

### 📊 Output

Every incident is one flat row. `null` means the feed carried no value for that field on that incident.

| Field | Type | Description |
|---|---|---|
| 🔥 `incident_name` | string | Incident name as filed, for example `2026 DOUGLAS PILES RX` |
| 🇺🇸 `state` | string | Two letter state code, for example `AZ` |
| 🗺 `county` | string | County the incident is recorded in |
| 🧭 `lat` | number | Latitude in decimal degrees |
| 🧭 `lon` | number | Longitude in decimal degrees |
| 📅 `discovery_date` | string | ISO timestamp of discovery |
| ❓ `cause` | string | Reported cause, for example `Undetermined` |
| 🏷 `status` | string | Incident type: `WF` for wildfire, `RX` for prescribed burn |
| 📏 `acres` | number | Fire size in acres. `null` across every row in the runs observed so far |
| 🚧 `containment_pct` | number | Containment percentage. `null` across every row in the runs observed so far |
| 🌿 `fuel_type` | string | Fuel type. `null` across every row in the runs observed so far |
| 🕒 `scrapedAt` | string | ISO timestamp of collection |
| ⚠️ `error` | string | `null` on a normal row |

#### Example rows

```json
{
  "incident_name": "2026 DOUGLAS PILES RX",
  "state": "AZ",
  "county": "Cochise",
  "lat": 31.755346,
  "lon": -109.360056,
  "acres": null,
  "containment_pct": null,
  "cause": "Undetermined",
  "discovery_date": "2026-01-01T21:56:51.000Z",
  "status": "RX",
  "fuel_type": null,
  "scrapedAt": "2026-09-14T16:23:20.615Z",
  "error": null
}
```

```json
{
  "incident_name": "2026 SIERRA VISTA PILES RX",
  "state": "AZ",
  "county": "Santa Cruz",
  "lat": 31.551709,
  "lon": -110.516882,
  "acres": null,
  "containment_pct": null,
  "cause": "Undetermined",
  "discovery_date": "2026-01-01T21:58:27.000Z",
  "status": "RX",
  "fuel_type": null,
  "scrapedAt": "2026-09-14T16:23:20.704Z",
  "error": null
}
```

### ✨ Why choose this Actor

| | What you get |
|---|---|
| **The federal feed** | Incidents come from the National Interagency Fire Center, not from a news map. |
| **No credentials** | The feed is public. No key, no account, no quota. |
| **Coordinates on every row** | State and county narrow it down, latitude and longitude let you measure the distance. |
| **Thirteen fields, every run** | The same columns each time, so repeat runs append into one history. |
| **You pay per row** | No subscription. Ten incidents cost under a dime. |

### 🚀 How to use it

1. [Create a free Apify account](https://console.apify.com/sign-up). New accounts start with $5 of credit.
2. Open the Actor and select **Try for free**.
3. Put a state code in `state`, or leave it empty for the whole country.
4. Set `minAcres` if you only want larger fires, and `maxItems` to cap the run.
5. Select **Start**, then export from the **Dataset** tab as CSV, Excel, JSON or XML.

A first run:

```json
{
  "maxItems": 10
}
```

One state, a deeper pull:

```json
{
  "state": "CA",
  "maxItems": 500
}
```

### ⚙️ Input

| Field | Required | Description |
|---|---|---|
| `state` | No | US state code to filter on, for example `CA`, `OR`, `TX`. Empty returns every state |
| `minAcres` | No | Only include fires at least this many acres |
| `maxItems` | No | How many incidents to collect per run. Default 10 |

### 💰 Pricing

Pay per result. No subscription, and no Apify platform usage on top.

| Apify plan | Free | Bronze | Silver | Gold | Platinum | Diamond |
|---|---|---|---|---|---|---|
| Per incident row | $0.0085 | $0.0082 | $0.0078 | $0.0075 | $0.0075 | $0.0075 |

| Rows collected | Cost on the Free plan |
|---|---|
| 100 | $0.85 |
| 1,000 | $8.50 |
| 10,000 | $85.00 |

**Free plan runs** return up to 10 rows as a preview. Any paid Apify plan lifts that to 1,000,000 per run.

### 🔌 Integrate with any app

The dataset is available through the Apify API as soon as the run finishes. Use `run-sync-get-dataset-items` for a one-shot call, webhooks to trigger what happens next, or the Make, Zapier, Airbyte and LangChain integrations listed on the Actor page.

### 🤖 Use with an AI agent

Give an agent live access to the incident feed over the Model Context Protocol:

```bash
claude mcp add --transport http apify "https://mcp.apify.com?tools=acquistion-automation/nifc-wildfire-incidents-scraper"
```

Then ask it in plain language which incidents were recorded in a county and have it read the result back.

### ❓ Frequently asked questions

**Why are `acres` and `containment_pct` empty?**
The feed did not carry a value for them on any row in the runs observed so far. Treat the rows as an incident register with location, date, cause and type, and read size and containment from the incident's own reporting.

**What do `WF` and `RX` mean in `status`?**
`WF` is a wildfire. `RX` is a prescribed burn, a fire set deliberately by a land manager. Both appear in the feed, so filter on `status` when you only want unplanned fires.

**Does the `minAcres` filter still work if `acres` is empty?**
It filters on the value the feed supplies. With acreage missing, a `minAcres` run can come back with fewer rows than you expect, so start with the filter off.

**How do I find incidents near one address?**
Filter by `state` and `county`, then compute the distance from your coordinates to `lat` and `lon` after export.

**Is this real time?**
It reads the feed at the moment of the run. Attach a schedule if you want the dataset kept current, and treat it as a record rather than an emergency alert.

**What can I export?**
CSV, Excel, JSON and XML from the run page, or JSON straight from the API.

### 🔗 More from Acquisition Automation Co.

- [Seattle Crime Data Scraper](https://apify.com/acquistion-automation/seattle-crime-data-scraper)
- [SAM.gov Contract Opportunities Scraper](https://apify.com/acquistion-automation/sam-gov-contracts-scraper)
- [PublicSurplus Scraper](https://apify.com/acquistion-automation/publicsurplus-scraper)
- [IRS Exempt Organizations Scraper](https://apify.com/acquistion-automation/irs-eo-master-file-scraper)
- [BizBuySell Scraper](https://apify.com/acquistion-automation/bizbuysell-scraper)

### About Acquisition Automation Co.

We build automation for people buying businesses. The repetitive part of an acquisition search, checking listings, pulling public records, tracking owners and assets, is work a machine should do, so the buyer's time goes into judging deals instead of collecting them.

We add new Actors regularly. If there is a source you need and do not see here, tell us.

### 🆘 Support

Open an issue in the **Issues** tab of this Actor with your run ID, the input you used, and what you expected to get back.

### ⚠️ Disclaimer

This Actor is independent and is not affiliated with, endorsed by, or sponsored by the National Interagency Fire Center or any government agency. It collects only publicly available data and is not an emergency warning service. You are responsible for using that data in compliance with the source's terms of service and applicable law.

# Actor input Schema

## `state` (type: `string`):

Filter incidents by US state code (e.g. CA, OR, TX).

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

Only include fires at least this many acres.

## `maxItems` (type: `integer`):

How many wildfire incidents to collect per run.

## Actor input object example

```json
{
  "maxItems": 10
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("acquistion-automation/nifc-wildfire-incidents-scraper").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 = { "maxItems": 10 }

# Run the Actor and wait for it to finish
run = client.actor("acquistion-automation/nifc-wildfire-incidents-scraper").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 '{
  "maxItems": 10
}' |
apify call acquistion-automation/nifc-wildfire-incidents-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,acquistion-automation/nifc-wildfire-incidents-scraper"
        }
    }
}
```

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/9ARhk0BnpiFVn9haU/builds/i0PJbAXvadARHB76v/openapi.json