# US Power Project Changes — EIA Generator Leads (`scrapesignal_labs/eia-power-project-change-feed`) Actor

Compare the newest EIA-860M reports to find new, delayed, resized, operating, retired, and canceled US power-generation projects.

- **URL**: https://apify.com/scrapesignal\_labs/eia-power-project-change-feed.md
- **Developed by:** [ScrapeSignal Labs](https://apify.com/scrapesignal_labs) (community)
- **Categories:** Lead generation, Automation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 power project changes

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## US Power Project Changes — EIA Generator Leads

Track what changed in the US power-generation pipeline—not just what exists. This Actor automatically finds the two newest valid EIA-860M generator workbooks, compares them generator by generator, and surfaces new planned capacity, projects entering operation, schedule changes, capacity changes, retirements, and cancellations or postponements.

The result is a practical change feed for teams selling into power developers, utilities, owners, operators, EPCs, and project ecosystems. Each record includes the current and previous state, capacity delta, technology, fuel code, planned dates, owner/operator, plant location, coordinates, and both official source workbooks.

### Built for

- renewable-energy, storage, transmission, engineering, construction, and equipment sales
- project finance, insurance, environmental, legal, and site-services teams
- power-market research, competitive intelligence, due diligence, and data products
- scheduled project alerts, CRM enrichment, and AI research agents

### Signals detected

- new planned generator
- new operating generator
- planned generator moved to operating
- generator status change
- planned operation month or year change
- nameplate capacity change
- newly retired generator
- newly canceled or postponed generator
- planned retirement date change

### Filters

Filter by change type, state, technology text, EIA energy-source code, minimum nameplate capacity, and whether to include Puerto Rico. You can also supply two official workbook URLs for a reproducible historical comparison.

### Example input

```json
{
  "changeTypes": ["new-planned", "became-operating", "operation-date-change", "capacity-change"],
  "states": ["TX", "AZ", "NM"],
  "technologies": ["Solar", "Batteries"],
  "minimumCapacityMw": 20,
  "maxItems": 1000
}
```

### Output highlights

Change types and score, entity and plant IDs, owner/operator and plant name, state and county, generator and unit IDs, current and previous lifecycle category, status, current and prior MW, calculated capacity change, technology, fuel and prime-mover codes, planned operation dates, retirement dates, latitude/longitude, and source reports.

### Source and caveats

The Actor uses the [official US Energy Information Administration EIA-860M data](https://www.eia.gov/electricity/data/eia860m/). EIA-860M is preliminary monthly reporting. A change can reflect a real project event, a reporting correction, or a classification update. Project schedules and capacities can change; verify important decisions with the developer, relevant permitting authorities, interconnection sources, and later EIA publications.

Run monthly after EIA updates the workbook, or schedule more frequently and let automatic discovery pick up the next valid release.

# Actor input Schema

## `changeTypes` (type: `array`):

Select the generator lifecycle, schedule, status, and capacity changes to return.

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

Two-letter state codes. Empty means nationwide.

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

Examples: Solar Photovoltaic, Batteries, Natural Gas, Onshore Wind.

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

Examples: SUN, WND, NG, MWH.

## `minimumCapacityMw` (type: `number`):

Only include generators at or above this current nameplate capacity.

## `includePuertoRico` (type: `boolean`):

Also compare the separate Puerto Rico generator worksheets.

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

Stop after saving this many highest-scoring project changes.

## `currentWorkbookUrl` (type: `string`):

Advanced: official .xlsx URL. Set both custom workbook fields together.

## `previousWorkbookUrl` (type: `string`):

Advanced: official .xlsx URL. Set both custom workbook fields together.

## Actor input object example

```json
{
  "changeTypes": [
    "new-planned",
    "new-operating",
    "became-operating",
    "status-change",
    "operation-date-change",
    "capacity-change",
    "newly-retired",
    "newly-canceled-or-postponed",
    "retirement-date-change"
  ],
  "states": [],
  "technologies": [],
  "energySources": [],
  "minimumCapacityMw": 1,
  "includePuertoRico": false,
  "maxItems": 500,
  "currentWorkbookUrl": "",
  "previousWorkbookUrl": ""
}
```

# Actor output Schema

## `dataset` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesignal_labs/eia-power-project-change-feed").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("scrapesignal_labs/eia-power-project-change-feed").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 '{}' |
apify call scrapesignal_labs/eia-power-project-change-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesignal_labs/eia-power-project-change-feed"
        }
    }
}

```

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/79ie45go1I6GEHikc/builds/ykXUh4vLrowuikWwf/openapi.json