# US Power Plant Pipeline (EIA-860M Generators) (`civic_data_feeds/us-power-plant-pipeline`) Actor

Planned, under-construction, canceled, operating and retired US power generators from EIA's monthly Form EIA-860M: owner, plant, state, county, technology, fuel, MW, status and expected online date. Monitor new and changed projects.

- **URL**: https://apify.com/civic_data_feeds/us-power-plant-pipeline.md
- **Developed by:** [Frank Gilroy](https://apify.com/civic_data_feeds) (community)
- **Categories:** Business, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 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.

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

### What does US Power Plant Pipeline do?

It reads the U.S. Energy Information Administration's **Preliminary Monthly Electric Generator Inventory (Form EIA-860M)** and gives you every US generator of 1 MW or more as a tidy dataset row: who owns it, which plant it belongs to, where it is (state, county, coordinates, balancing authority), what it runs on, how many megawatts it has, and where it stands in its life cycle.

The most useful part is the **new-build pipeline**: the *Planned* list (proposed, permitted and under-construction projects with their expected online month) and the *Canceled or Postponed* list. Existing (*Operating*) and *Retired* generators are available too. Turn on **Only new or changed generators** and schedule the Actor monthly to receive just the projects that appeared or moved since your last run.

Who uses it:

- **Pipeline tracking.** Watch solar, wind, battery, gas and nuclear projects move from "planned" to "under construction" to "testing", state by state.
- **Developer and siting research.** See which companies are building where, at what size, and which grid region (balancing authority) they connect to.
- **Supply-chain and EPC lead lists.** Projects with regulatory approval but not yet under construction are the ones about to buy transformers, panels, turbines and construction services.
- **Energy analysts and journalists.** Capacity additions and retirements by technology and month, with the official EIA status wording kept intact.

No login, API key or proxy is needed: the source is a public EIA download.

### How to use it

1. Pick the **inventories** you want. `planned` is the default; add `canceled`, `operating` or `retired` as needed.
2. Narrow it down with **states** (two-letter codes), **technologies** (for example `Batteries`, `Solar Photovoltaic`, `Onshore Wind`), **energy source codes** (`SUN`, `WND`, `MWH`, `NG`, `NUC` and so on), a **minimum MW**, EIA **status codes**, or a **planned online window** (`YYYY-MM`).
3. Run it. For monitoring, schedule a run each month with **Only new or changed generators** switched on and **Fail the run if nothing is found** switched off.

EIA status codes for planned units: `P` planned, approvals not started · `L` approvals pending · `T` approvals received · `U` under construction, up to half done · `V` under construction, more than half done · `TS` built and testing · `OT` other. Operating units use `OP`, `SB`, `OA` and `OS`. This Actor labels retired rows `RE` and canceled or postponed rows `CN`.

#### Input example

Large Texas and Arizona batteries that are under construction or testing and due online during 2027:

```json
{
  "inventories": ["planned"],
  "states": ["TX", "AZ"],
  "technologies": ["Batteries"],
  "minMw": 50,
  "statusCodes": ["U", "V", "TS"],
  "plannedOperationFrom": "2027-01",
  "plannedOperationTo": "2027-12",
  "maxResults": 2000
}
```

### Output

You get one row per generator (a single plant often has several). Download the dataset as JSON, CSV, Excel or XML, or pull it through the Apify API.

```json
{
  "id": "eia860m:68334-EVCRK",
  "inventory": "planned",
  "status": "(V) Under construction, more than 50 percent complete",
  "statusCode": "V",
  "entityId": 66742,
  "entityName": "Evans Creek Energy Storage LLC",
  "plantId": 68334,
  "plantName": "Evans Creek Energy Storage Project",
  "generatorId": "EVCRK",
  "state": "TX",
  "county": "Val Verde",
  "balancingAuthority": "ERCO",
  "sector": "IPP Non-CHP",
  "technology": "Batteries",
  "energySource": "MWH",
  "primeMover": "BA",
  "nameplateMw": 103,
  "summerMw": 103,
  "winterMw": 103,
  "plannedOperationDate": "2026-09",
  "operatingDate": null,
  "retirementDate": null,
  "latitude": 29.746007,
  "longitude": -101.1406,
  "dataMonth": "2026-09",
  "releaseDate": "2026-10-23",
  "sourceUrl": "https://www.eia.gov/electricity/data/eia860m/xls/september_generator2026.xlsx",
  "attribution": "Source: U.S. Energy Information Administration, Preliminary Monthly Electric Generator Inventory (Form EIA-860M), October 2026",
  "scrapedAt": "2026-11-13T10:24:31.512Z"
}
```

| Field | Meaning |
|---|---|
| `id` | `eia860m:` + EIA plant ID + generator ID. Stable from month to month |
| `inventory` | `planned`, `canceled`, `operating` or `retired` (the EIA sheet the row came from) |
| `status`, `statusCode` | EIA's status wording and its short code (see the list above) |
| `entityId`, `entityName` | The reporting owner or operator (a company, utility, co-op or public body) |
| `plantId`, `plantName`, `generatorId` | EIA identifiers for the plant and the unit |
| `balancingAuthority` | Grid balancing area code, e.g. `ERCO`, `PJM`, `MISO`, `CISO` |
| `sector` | EIA sector, e.g. `Electric Utility`, `IPP Non-CHP`, `Industrial CHP` |
| `technology`, `energySource`, `primeMover` | EIA technology description, energy source code and prime mover code |
| `nameplateMw`, `summerMw`, `winterMw` | Nameplate and net seasonal capacity in megawatts |
| `plannedOperationDate` | Expected online month (`YYYY-MM`), planned units only |
| `operatingDate` | Month the unit started operating (operating and retired units) |
| `retirementDate` | Month retired; for operating units, the planned retirement month when one is reported |
| `dataMonth`, `releaseDate` | The month the inventory describes and the day EIA published it |
| `sourceUrl`, `attribution` | The exact EIA file used and a ready-made credit line |

### Get a daily alert

Turn this Actor into a monthly list of new or changed projects (EIA publishes monthly, so a monthly schedule is enough) in a few minutes:

1. Set your filters in the **Input** tab and turn on **Only new or changed generators**. Turn **Fail the run if nothing is found** off.
2. Click **Save as a new task**, then open the task and choose **Schedule**. Pick a cron time (for example every day at 07:00).
3. Open the task's **Integrations** tab and add one of:
   - **Slack:** posts a message to a channel when a run finishes.
   - **Email:** sends a notification with a link to the results.
   - **Google Sheets:** appends the new generators as rows after each run.
   - **Webhook:** sends an HTTP POST to your own URL when the run succeeds; read the new rows from the run's default dataset.
4. The first run returns everything that matches your filters. Every later run returns only generators it has not returned before, so you pay only for what is new.

The list of already returned IDs is kept in a key-value store in your own Apify account. Delete that store if you want a fresh start.

### How much does it cost?

Pricing is **pay-per-event: $4.00 per 1,000 generators** returned ($0.004 per row), plus Apify's small standard Actor-start fee. Compute and storage are included.

- Every planned 100 MW-plus project in Texas (about 350 rows) costs roughly **$1.40**.
- The whole national pipeline, planned plus canceled (about 4,100 rows), costs about **$16.40**.
- A monthly monitor that reports around 300 new or changed projects costs about **$1.20 a month**.
- The full inventory of all four lists (about 40,000 rows) costs about **$160**.

Runs that match nothing are not charged for results. If you set a maximum cost per run, the Actor stops neatly once it reaches it.

### Popular presets

Paste any of these into the Input tab's JSON view and press Start.

**Texas solar and battery projects, 50 MW and up**

```json
{
  "inventories": [
    "planned"
  ],
  "states": [
    "TX"
  ],
  "technologies": [
    "Solar Photovoltaic",
    "Batteries"
  ],
  "minMw": 50,
  "maxResults": 200
}
```

**Batteries of 100 MW or more due online in 2027**

```json
{
  "inventories": [
    "planned"
  ],
  "technologies": [
    "Batteries"
  ],
  "minMw": 100,
  "plannedOperationFrom": "2027-01",
  "plannedOperationTo": "2027-12",
  "maxResults": 200
}
```

**Projects under construction or testing**

```json
{
  "inventories": [
    "planned"
  ],
  "statusCodes": [
    "U",
    "V",
    "TS"
  ],
  "minMw": 100,
  "maxResults": 200
}
```

**Planned wind projects, 50 MW and up**

```json
{
  "inventories": [
    "planned"
  ],
  "energySources": [
    "WND"
  ],
  "minMw": 50,
  "maxResults": 200
}
```

**Monthly monitor: only new or changed projects**

```json
{
  "inventories": [
    "planned"
  ],
  "minMw": 50,
  "onlyNew": true,
  "failOnEmpty": false,
  "maxResults": 500
}
```

### How it compares

Checked against the public Store pages and input schemas on 2026-11-15. Rivals change; check their pages before you buy.

| | This Actor | nexgenwatch/eia-860m-monthly-generator-inventory | afkdigital/us-power-plant-expansion-retirement-pipeline | maydit/eia-power-project-monitor |
|---|---|---|---|---|
| Source | EIA-860M | EIA-860M | EIA-860M and EIA-860 | EIA reporting |
| Inventories | Planned, canceled or postponed, operating, retired | Status categories | Planned, operating, retiring, retired | Planned generators |
| Filters | State, technology, energy source, minimum MW, EIA status, planned online window | State, technology, energy source, balancing authority, owner, status | State, energy source, minimum MW, operator, status, planned dates | Keywords, states, technologies, minimum MW, plant IDs |
| New or changed only | Yes (`onlyNew`) | Not in its input | Not in its input | Yes (`onlyChanges`) |
| Balancing authority and coordinates in output | Yes | Yes | Not stated | Not stated |
| Price (pay per event) | $4.00 per 1,000 generators | $0.02 per run plus per-record fee (see its page) | $9.00 per 1,000 generators | see its page |

Pick this one for a monthly new-build watch with grid region and coordinates on every row. Pick another if you need to filter by owner name or balancing authority up front.

### FAQ

**How often does the source update?** EIA publishes the 860M inventory monthly. Schedule the Actor monthly.

**What counts as the "pipeline"?** The planned list: proposed, permitted, under-construction and testing projects, plus canceled or postponed ones.

**Can I get only projects that changed?** Yes. Turn on **Only new or changed generators**.

**Do I get coordinates and the grid region?** Yes: latitude, longitude, county and balancing authority on every row.

**Does it cover units under 1 MW?** No. EIA-860M lists generators of 1 MW or more.

**Are owner contact details included?** No. Entity names are kept; named people are removed.

### Output sample

Three real rows from a run on 2026-11-15, trimmed to the main fields:

```json
[
  {
    "id": "eia860m:68334-EVCRK",
    "inventory": "planned",
    "status": "(V) Under construction, more than 50 percent complete",
    "statusCode": "V",
    "entityId": 66742,
    "entityName": "Evans Creek Energy Storage LLC",
    "plantId": 68334,
    "plantName": "Evans Creek Energy Storage Project",
    "generatorId": "EVCRK",
    "state": "TX",
    "county": "Val Verde",
    "balancingAuthority": "ERCO",
    "sector": "IPP Non-CHP",
    "technology": "Batteries",
    "energySource": "MWH",
    "primeMover": "BA",
    "nameplateMw": 103,
    "summerMw": 103,
    "winterMw": 103,
    "plannedOperationDate": "2026-09",
    "operatingDate": null,
    "retirementDate": null,
    "latitude": 29.746007,
    "longitude": -101.1406,
    "dataMonth": "2026-09",
    "releaseDate": "2026-10-23",
    "sourceUrl": "https://www.eia.gov/electricity/data/eia860m/xls/september_generator2026.xlsx",
    "attribution": "Source: U.S. Energy Information Administration, Preliminary Monthly Electric Generator Inventory (Form EIA-860M), October 2026",
    "scrapedAt": "2026-11-15T05:25:48.291Z"
  },
  {
    "id": "eia860m:64672-BLUJS",
    "inventory": "planned",
    "status": "(TS) Construction complete, but not yet in commercial operation",
    "statusCode": "TS",
    "entityId": 64266,
    "entityName": "Blue Jay Solar I, LLC",
    "plantId": 64672,
    "plantName": "Blue Jay Solar I, LLC",
    "generatorId": "BLUJS",
    "state": "TX",
    "county": "Grimes",
    "balancingAuthority": "ERCO",
    "sector": "IPP Non-CHP",
    "technology": "Solar Photovoltaic",
    "energySource": "SUN",
    "primeMover": "PV",
    "nameplateMw": 210,
    "summerMw": 210,
    "winterMw": 210,
    "plannedOperationDate": "2026-10",
    "operatingDate": null,
    "retirementDate": null,
    "latitude": 30.705329,
    "longitude": -96.06983,
    "dataMonth": "2026-09",
    "releaseDate": "2026-10-23",
    "sourceUrl": "https://www.eia.gov/electricity/data/eia860m/xls/september_generator2026.xlsx",
    "attribution": "Source: U.S. Energy Information Administration, Preliminary Monthly Electric Generator Inventory (Form EIA-860M), October 2026",
    "scrapedAt": "2026-11-15T05:25:48.372Z"
  },
  {
    "id": "eia860m:65028-ROSES",
    "inventory": "planned",
    "status": "(TS) Construction complete, but not yet in commercial operation",
    "statusCode": "TS",
    "entityId": 64438,
    "entityName": "Enel Green Power Roseland Solar, LLC",
    "plantId": 65028,
    "plantName": "Roseland Solar Project, LLC",
    "generatorId": "ROSES",
    "state": "TX",
    "county": "Falls",
    "balancingAuthority": "ERCO",
    "sector": "IPP Non-CHP",
    "technology": "Solar Photovoltaic",
    "energySource": "SUN",
    "primeMover": "PV",
    "nameplateMw": 500,
    "summerMw": 500,
    "winterMw": 500,
    "plannedOperationDate": "2026-10",
    "operatingDate": null,
    "retirementDate": null,
    "latitude": 31.461242,
    "longitude": -96.82493,
    "dataMonth": "2026-09",
    "releaseDate": "2026-10-23",
    "sourceUrl": "https://www.eia.gov/electricity/data/eia860m/xls/september_generator2026.xlsx",
    "attribution": "Source: U.S. Energy Information Administration, Preliminary Monthly Electric Generator Inventory (Form EIA-860M), October 2026",
    "scrapedAt": "2026-11-15T05:25:48.429Z"
  }
]
```

### Limits and notes

- **Monthly data.** EIA publishes EIA-860M once a month, roughly four weeks after the month it covers. Running more often than that returns the same file; a monthly schedule is enough.
- **Preliminary figures.** These are EIA's early numbers. Planned dates slip, capacities get revised, and the annual Form EIA-860 later supersedes them. Treat `plannedOperationDate` as the owner's latest estimate.
- **1 MW threshold.** Plants with less than 1 MW of total nameplate capacity are not in the source.
- **Owner names of individuals removed.** A few generator owners are individuals. When an owner name looks like a person's name and carries no company or place word, `entityName` is left empty; `entityId` remains so you can still join on it. Plant names are facility names (some honour historical figures) and are kept as EIA publishes them.
- **Respects EIA's rules.** The Actor fetches only the current file linked from EIA's EIA-860M page, never the archive folders that EIA's robots.txt excludes, sends at most one request per second, and backs off when the server is busy.
- **Memory.** The default 1 GB is sized for reading all four lists at once (about 600 MB at peak). 512 MB is enough for the planned and canceled lists alone.

### Sources and licences

Data: U.S. Energy Information Administration, Form EIA-860M, https://www.eia.gov/electricity/data/eia860m/. EIA's copyright and reuse page (https://www.eia.gov/about/copyrights_reuse.php) says: "U.S. government publications are in the public domain and are not subject to copyright protection. You may use and/or distribute any of our data, files, databases, reports, graphs, charts, and other information products that are on our website". EIA asks that reusers credit it as the source and give the date of the publication; every row carries an `attribution` line and a `releaseDate` for this.

This Actor is independent and is not affiliated with, endorsed by or sponsored by the U.S. Energy Information Administration.

### Related

[Queue Ledger](https://beingrealfrank.github.io/queue-ledger/) is a free point-in-time archive of US power-project pipelines (EIA-860M, CAISO, SPP), useful for seeing how a project's status changed between monthly releases.

### Guides and free samples

Background on the data source, with working examples:

- [EIA-860M planned power plants: status codes](https://beingrealfrank.github.io/civic-data-feeds-samples/guides/eia-860m-planned-generators.html)
- [Planned battery storage projects by state](https://beingrealfrank.github.io/civic-data-feeds-samples/guides/planned-battery-storage-projects-by-state.html)
- [Canceled, postponed and retired generators](https://beingrealfrank.github.io/civic-data-feeds-samples/guides/eia-860m-canceled-retired-generators.html)
- [All free weekly samples](https://beingrealfrank.github.io/civic-data-feeds-samples/)

### Related Actors from civic_data_feeds

- [EU & UK Public Tenders Monitor](https://apify.com/civic_data_feeds/public-tenders-monitor): TED, Find a Tender and Contracts Finder notices in one schema.
- [US Federal Grants Monitor](https://apify.com/civic_data_feeds/us-grants-monitor): Grants.gov opportunities with award sizes, eligibility and forecasts.
- [CanadaBuys Tenders Monitor](https://apify.com/civic_data_feeds/canadabuys-tenders-monitor): open Canadian government tender notices from CanadaBuys.

All of them use the same pay-per-event pricing, need no login and can be scheduled with an only-new option.

### Support

Published by Frank Gilroy. Questions get an answer within 7 days. Open an issue on the **Issues** tab if a value looks off or you need another field.

# Actor input Schema

## `inventories` (type: `array`):

Which EIA-860M lists to read. planned = proposed and under-construction generators (the new-build pipeline). canceled = canceled or indefinitely postponed projects. operating = existing generators. retired = retired generators.

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

Two-letter US state codes, e.g. TX, CA, AZ. Leave empty for all states.

## `technologies` (type: `array`):

Keep generators whose EIA technology contains any of these words, case-insensitive, e.g. Batteries, Solar Photovoltaic, Onshore Wind, Natural Gas Fired Combined Cycle, Nuclear.

## `energySources` (type: `array`):

EIA energy source codes, e.g. SUN (solar), WND (wind), MWH (battery storage), NG (natural gas), NUC (nuclear), WAT (hydro).

## `minMw` (type: `integer`):

Only generators with at least this nameplate capacity.

## `statusCodes` (type: `array`):

Planned: P (planned, approvals not started), L (approvals pending), T (approvals received), U (under construction, up to 50%), V (under construction, over 50%), TS (built, testing), OT (other). Operating: OP, SB, OA, OS. Retired rows use RE and canceled rows use CN.

## `plannedOperationFrom` (type: `string`):

Only planned generators expected to start operating in or after this month. Rows without a planned date are excluded when set.

## `plannedOperationTo` (type: `string`):

Only planned generators expected to start operating in or before this month.

## `onlyNew` (type: `boolean`):

For scheduled monitoring: return only generators that are new, or whose status, nameplate MW or planned online date changed, since this Actor last returned them to you. Fingerprints are kept in a named key-value store in your account.

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

Stop after this many generators. You are only charged for generators returned.

## `failOnEmpty` (type: `boolean`):

Turn off for scheduled monitors where 'nothing changed this month' is normal.

## Actor input object example

```json
{
  "inventories": [
    "planned"
  ],
  "states": [
    "TX"
  ],
  "technologies": [
    "Solar Photovoltaic",
    "Batteries"
  ],
  "energySources": [],
  "minMw": 50,
  "statusCodes": [],
  "onlyNew": false,
  "maxResults": 100,
  "failOnEmpty": true
}
```

# 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 = {
    "inventories": [
        "planned"
    ],
    "states": [
        "TX"
    ],
    "technologies": [
        "Solar Photovoltaic",
        "Batteries"
    ],
    "minMw": 50,
    "maxResults": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("civic_data_feeds/us-power-plant-pipeline").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 = {
    "inventories": ["planned"],
    "states": ["TX"],
    "technologies": [
        "Solar Photovoltaic",
        "Batteries",
    ],
    "minMw": 50,
    "maxResults": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("civic_data_feeds/us-power-plant-pipeline").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 '{
  "inventories": [
    "planned"
  ],
  "states": [
    "TX"
  ],
  "technologies": [
    "Solar Photovoltaic",
    "Batteries"
  ],
  "minMw": 50,
  "maxResults": 100
}' |
apify call civic_data_feeds/us-power-plant-pipeline --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,civic_data_feeds/us-power-plant-pipeline"
        }
    }
}
```

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/W5yxG6Ji8ze24f8JR/builds/7LtjyU3OrSOB14Tkn/openapi.json
