# EIA-923 Generator-Unit Net Generation (Monthly, Preliminary) (`nexgenwatch/eia923-generator-unit-net-generation`) Actor

Structured generator-unit monthly net generation records from the U.S. EIA Form EIA-923 Page 4 Generator Data sheet, read directly from the official current-year monthly ZIP on www.eia.gov.

- **URL**: https://apify.com/nexgenwatch/eia923-generator-unit-net-generation.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Automation, Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $13.40 / 1,000 generator-unit net generation records

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

## 🔔 EIA-923 Generator-Unit Net Generation (Monthly, Preliminary)

Structured **generator-unit monthly net generation** records from the U.S. EIA Form EIA-923 **Page 4 Generator
Data** sheet, read directly from the official current-year monthly ZIP on `www.eia.gov`. One record per
generator-unit line, carried source-native and **verbatim**.

Output is one `generator_output_record` row per result; billing is pay-per-event, the value event being one generator-unit net generation record (a $0.02 start fee per run, then $0.02 per generator-unit net generation record). Source: www.eia.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

### 📊 Sample Output

[![EIA-923 Generator-Unit Net Generation (Monthly, Preliminary) sample output — a table of real generator-unit net generation record rows (plant_id, combined_heat_and_power_plant, operator_name, sector_name) from run 45lvuVemr9Nfj97wB on build 0.1.5](https://api.apify.com/v2/key-value-stores/80Y7h3rmVN5CWK7Mw/records/eia923-generator-unit-net-generation-sample)](https://apify.com/nexgenwatch/eia923-generator-unit-net-generation?fpr=2ayu9b)

Real rows from run `45lvuVemr9Nfj97wB` on build 0.1.5 (2026-09-19), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

| plant_id | combined_heat_and_power_plant | operator_name | sector_name | data_status | release_date |
|---|---|---|---|---|---|
| 3 | N | Alabama Power Co | Electric Utility | preliminary (EIA-923 monthly) | f923_2026 |
| 3 | N | Alabama Power Co | Electric Utility | preliminary (EIA-923 monthly) | f923_2026 |
| 3 | N | Alabama Power Co | Electric Utility | preliminary (EIA-923 monthly) | f923_2026 |
| 3 | N | Alabama Power Co | Electric Utility | preliminary (EIA-923 monthly) | f923_2026 |
| 3 | N | Alabama Power Co | Electric Utility | preliminary (EIA-923 monthly) | f923_2026 |
| 3 | N | Alabama Power Co | Electric Utility | preliminary (EIA-923 monthly) | f923_2026 |
| 3 | N | Alabama Power Co | Electric Utility | preliminary (EIA-923 monthly) | f923_2026 |
| 3 | N | Alabama Power Co | Electric Utility | preliminary (EIA-923 monthly) | f923_2026 |

The run finished with the status message: `NORMAL: 12 unique rows (0 duplicates collapsed) from f923_2026. billable=12`

### ✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is `null`):

- `plant_id` (string/null) — e.g. `3`
- `combined_heat_and_power_plant` (string/null) — e.g. `N`
- `plant_name` (string/null) — e.g. `Barry`
- `operator_name` (string/null) — e.g. `Alabama Power Co`
- `operator_id` (string/null) — e.g. `195`
- `plant_state` (string/null) — e.g. `AL`
- `census_region` (string/null) — e.g. `ESC`
- `nerc_region` (string/null) — e.g. `SERC`
- `naics_code` (string/null) — e.g. `22`
- `sector_number` (string/null) — e.g. `1`
- `sector_name` (string/null) — e.g. `Electric Utility`
- `generator_id` (string/null) — e.g. `1`
- `reported_prime_mover` (string/null) — e.g. `ST`
- `net_generation_january` (string/null) — e.g. `1279`
- `net_generation_february` (string/null) — e.g. `1692`
- `net_generation_march` (string/null) — e.g. `-481`
- `net_generation_april` (string/null) — e.g. `-163`
- `net_generation_may` (string/null) — e.g. `3399`
- `net_generation_june` (string/null) — e.g. `-391`
- `net_generation_july` (string/null) — e.g. `.`
- `net_generation_august` (string/null) — e.g. `.`
- `net_generation_september` (string/null) — e.g. `.`
- `net_generation_october` (string/null) — e.g. `.`
- `net_generation_november` (string/null) — e.g. `.`
- `net_generation_december` (string/null) — e.g. `.`
- `net_generation_year_to_date` (string/null) — e.g. `5335`
- `ba_code` (string/null) — e.g. `SOCO`
- `year` (string/null) — e.g. `2026`
- `record_type` (string/null) — e.g. `generator_output_record`
- `data_status` (string/null) — e.g. `preliminary (EIA-923 monthly)`
- `shape` (string/null) — e.g. `wide`
- `reporting_period` (string/null) — e.g. `2026`
- `record_key` (string/null) — e.g. `eia923-gen:3:1:ST:2026:d3cdcf8153ba49a3`
- `source_url` (string/null) — e.g. `https://www.eia.gov/electricity/data/eia923/xls/f923_2026.zip`
- `source` (string/null) — e.g. `eia923-generator-unit-net-generation`
- `release_date` (string/null) — e.g. `f923_2026`
- `observed_at` (string/null) — e.g. `2026-09-19T02:21:45Z`
- `release_checksum` (string/null) — e.g. `2026`
- `license` (string/null) — e.g. `U.S. Energy Information Administration (EIA), Form EIA-923, Page 4 Generator Dat`
- `attribution` (string/null) — e.g. `U.S. Energy Information Administration — Form EIA-923 (https://www.eia.gov/elect`
- `net_generation` (string/null) — null in every sample row
- `month` (string/null) — null in every sample row
- `month_name` (string/null) — null in every sample row
- `terminal` (string/null) — null in every sample row
- `scope` (string/null) — null in every sample row
- `note` (string/null) — null in every sample row
- `reported_total` (string/integer/null) — null in every sample row
- `raw_seen` (string/integer/null) — null in every sample row
- `duplicates` (string/integer/null) — null in every sample row
- `unique_found` (string/integer/null) — null in every sample row
- `delivered` (string/integer/null) — null in every sample row

**✅ What you get**

- `plant_id` (string/null) — e.g. `3`
- `combined_heat_and_power_plant` (string/null) — e.g. `N`
- `plant_name` (string/null) — e.g. `Barry`
- `operator_name` (string/null) — e.g. `Alabama Power Co`
- `operator_id` (string/null) — e.g. `195`
- `plant_state` (string/null) — e.g. `AL`
- `census_region` (string/null) — e.g. `ESC`
- `nerc_region` (string/null) — e.g. `SERC`
- `naics_code` (string/null) — e.g. `22`
- `sector_number` (string/null) — e.g. `1`
- `sector_name` (string/null) — e.g. `Electric Utility`
- `generator_id` (string/null) — e.g. `1`
- `reported_prime_mover` (string/null) — e.g. `ST`
- `net_generation_january` (string/null) — e.g. `1279`
- `net_generation_february` (string/null) — e.g. `1692`
- `net_generation_march` (string/null) — e.g. `-481`
- `net_generation_april` (string/null) — e.g. `-163`
- `net_generation_may` (string/null) — e.g. `3399`
- `net_generation_june` (string/null) — e.g. `-391`
- `net_generation_july` (string/null) — e.g. `.`
- `net_generation_august` (string/null) — e.g. `.`
- `net_generation_september` (string/null) — e.g. `.`
- `net_generation_october` (string/null) — e.g. `.`
- `net_generation_november` (string/null) — e.g. `.`
- `net_generation_december` (string/null) — e.g. `.`
- `net_generation_year_to_date` (string/null) — e.g. `5335`
- `ba_code` (string/null) — e.g. `SOCO`
- `year` (string/null) — e.g. `2026`
- `record_type` (string/null) — e.g. `generator_output_record`
- `data_status` (string/null) — e.g. `preliminary (EIA-923 monthly)`
- `shape` (string/null) — e.g. `wide`
- `reporting_period` (string/null) — e.g. `2026`
- `record_key` (string/null) — e.g. `eia923-gen:3:1:ST:2026:d3cdcf8153ba49a3`
- `source_url` (string/null) — e.g. `https://www.eia.gov/electricity/data/eia923/xls/f923_2026.zip`
- `source` (string/null) — e.g. `eia923-generator-unit-net-generation`
- `release_date` (string/null) — e.g. `f923_2026`
- `observed_at` (string/null) — e.g. `2026-09-19T01:43:27Z`
- `release_checksum` (string/null) — e.g. `2026`
- `license` (string/null) — e.g. `U.S. Energy Information Administration (EIA), Form EIA-923, Page 4 Generator Dat`
- `attribution` (string/null) — e.g. `U.S. Energy Information Administration — Form EIA-923 (https://www.eia.gov/elect`
- `net_generation` (string/null) — null in every sample row
- `month` (string/null) — null in every sample row
- `month_name` (string/null) — null in every sample row
- `terminal` (string/null) — null in every sample row
- `scope` (string/null) — null in every sample row
- `note` (string/null) — null in every sample row
- `reported_total` (string/integer/null) — null in every sample row
- `raw_seen` (string/integer/null) — null in every sample row
- `duplicates` (string/integer/null) — null in every sample row
- `unique_found` (string/integer/null) — null in every sample row
- `delivered` (string/integer/null) — null in every sample row

**What you get — and shape**

One `generator_output_record` per source row (wide, the default): plant & operator identity (`plant_id`,
`plant_name`, `operator_name`, `operator_id`, `plant_state`, census / NERC region, `naics_code`,
`sector_number`, `sector_name`, `ba_code`), `generator_id`, `reported_prime_mover`, the **twelve monthly Net
Generation (MWh)** columns and the `net_generation_year_to_date` total, plus `data_status`, `source_url`,
`license` — all verbatim.

Set `normalizeMonthly=true` for the **long** shape: one record per month (12 per source row), with the
identifiers repeated and the month's `net_generation` value.

### ⚙️ Sample inputs

**1. Quick start — the Store example (this is what the sample above came from)**

```json
{
  "plantIds": [
    "3"
  ],
  "maxRecords": 50
}
```

The sample run charged exactly: 2 × $0.02 apify-actor-start + 12 × $0.02 generator_output_record = **$0.28** on the Free tier — every delivered row was billed.

**2. A smaller, narrowed run**

```json
{
  "plantIds": [
    "3"
  ],
  "maxRecords": 5
}
```

Caps the run at 5 rows — about $0.12 on the Free tier ($0.02 start + 5 × $0.02).

**3. A full-size run**

```json
{
  "plantIds": [
    "3"
  ],
  "maxRecords": 2500
}
```

Up to 2500 rows (the schema default for `maxRecords`) — about $50.02 on the Free tier ($0.02 start + 2500 × $0.02) if the source has that many.

**4. A filtered run**

```json
{
  "plantIds": [
    "3"
  ],
  "maxRecords": 50,
  "fieldMatch": {
    "plant_name": "Barry"
  }
}
```

Keeps only rows whose `plant_name` contains `Barry` (a value from the sample run above), matched case-insensitively after the source is read and **before** the `maxRecords` cap, so the cap counts matches and only delivered matches are billed. `searchText` does the same across every column. Zero matches end the run as `EMPTY_SELECTION` with no row charged — if the source has moved on since that sample run, pick a value you see in your own first run. The source is still read in full — this narrows what you receive and pay for, not what the source serves.

### 🧾 JSON sample record

One real record from run `45lvuVemr9Nfj97wB`, exactly as it lands in the dataset (emails masked, long text shortened):

```json
{
  "plant_id": "3",
  "combined_heat_and_power_plant": "N",
  "plant_name": "Barry",
  "operator_name": "Alabama Power Co",
  "operator_id": "195",
  "plant_state": "AL",
  "census_region": "ESC",
  "nerc_region": "SERC",
  "naics_code": "22",
  "sector_number": "1",
  "sector_name": "Electric Utility",
  "generator_id": "1",
  "reported_prime_mover": "ST",
  "net_generation_january": "1279",
  "net_generation_february": "1692",
  "net_generation_march": "-481",
  "net_generation_april": "-163",
  "net_generation_may": "3399",
  "net_generation_june": "-391",
  "net_generation_july": ".",
  "net_generation_august": ".",
  "net_generation_september": ".",
  "net_generation_october": ".",
  "net_generation_november": ".",
  "net_generation_december": ".",
  "net_generation_year_to_date": "5335",
  "ba_code": "SOCO",
  "year": "2026",
  "record_type": "generator_output_record",
  "data_status": "preliminary (EIA-923 monthly)",
  "shape": "wide",
  "reporting_period": "2026",
  "record_key": "eia923-gen:3:1:ST:2026:d3cdcf8153ba49a3",
  "source_url": "https://www.eia.gov/electricity/data/eia923/xls/f923_2026.zip",
  "source": "eia923-generator-unit-net-generation",
  "release_date": "f923_2026",
  "observed_at": "2026-09-19T02:21:45Z",
  "release_checksum": "2026",
  "license": "U.S. Energy Information Administration (EIA), Form EIA-923, Page 4 Generator Data (MONTHLY, PRELIMINARY) — U.S. Government work, public domain. Monthly values are preliminary; final figures are published annually. Acknowledgement: data from",
  "attribution": "U.S. Energy Information Administration — Form EIA-923 (https://www.eia.gov/electricity/data/eia923/)"
}
```

### 🔧 How it works

**Source.** The actor reads www.eia.gov — endpoints: `https://www.eia.gov`, `https://www.eia.gov/electricity/data/eia923/`, `https://www.eia.gov/electricity/data/eia923/xls/f923_`. Public pages and feeds only; nothing behind a login.

**Transport.** Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent. Pacing: `CRAWL_DELAY`=0.0.

**Terminal states.** A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

**Charging.** Each generator-unit net generation record is charged at the moment it is pushed (`generator_output_record`); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

**🔧 How it works**

**Preliminary data**

EIA-923 **monthly** data is **preliminary** — final figures are published annually. Every record carries a
`data_status` field stating this.

**Generator Id is plant-scoped — composite keys**

A **Generator Id is not globally unique**; it is only unique **within a plant**. Each record's key is therefore
**composite** — plant + generator + prime-mover + year (+ month in long shape) — so the same generator id at two
different plants stays two distinct records. (Same design as our boiler-fuel actor's composite boiler key.)

**Not to be confused with**

Distinct from plant-level generation & fuel (Page 1, `eia923-plant-generation-fuel`), boiler fuel (Page 3),
fuel **purchases** (Page 5), and the generator **inventory / nameplate master** (EIA-860). This is the
generator-unit monthly **output** feed.

**Filters**

Supply **at least one** of `plantIds`, `plantStates`, `generatorIds`, `primeMovers`, or `sectorNumbers` — the
sheet is never emitted in full. `maxRecords` caps delivery (one charge per delivered record, hard cap 5000).

**Integrity, robots & door**

A per-sheet **schema canary** fails loud on header drift. Only the **current** monthly `f923_<year>.zip` is read
— `www.eia.gov/robots.txt` disallows `/archive/`, which is never fetched; the early-release `...er.zip` is
skipped in favour of the current monthly file. No third-party content or logos.

**Source & licence**

U.S. Energy Information Administration, Form EIA-923 (Page 4) — U.S. Government work, **public domain** (monthly
values preliminary). Acknowledgement: data from the U.S. Energy Information Administration
(https://www.eia.gov/electricity/data/eia923/).

**What is not done.** No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

### 💰 Pricing example

| Event | Free | Bronze | Silver | Gold |
|---|---|---|---|---|
| Actor Start (`apify-actor-start`) | $0.02 | $0.02 | $0.02 | $0.02 |
| Generator-unit net generation record (`generator_output_record`) | $0.02 | $0.018 | $0.016 | $0.0134 |

Worked at the live Free-tier price:

- 8 generator-unit net generation records: $0.02 start + 8 × $0.02 = **$0.18**
- 25 generator-unit net generation records: $0.02 start + 25 × $0.02 = **$0.52**
- 2500 generator-unit net generation records: $0.02 start + 2500 × $0.02 = **$50.02**

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: `NORMAL: 12 unique rows (0 duplicates collapsed) from f923_2026. billable=12`. `maxRecords` is a hard ceiling on what is delivered and billed, never a target.

### ⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by www.eia.gov. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

### ❓ FAQ

**Q: Do I need an API key or a login?**\
A: No. The source (www.eia.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

**Q: Why did my run return 0 rows?**\
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

**Q: How many rows can one run return?**\
A: Up to `maxRecords` (default 2500). Raise the cap for a bigger run; you pay per delivered row.

**Q: How fresh is the data?**\
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

**Q: What formats can I export?**\
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

**Q: How is this different from the other NexGen Watch actors actors?**\
A: Same output shape and billing model; this one covers www.eia.gov. The siblings under **Related Actors** cover the other sources or slices — run several on one schedule for a combined feed.

**Q: Are there rate limits?**\
A: The actor paces itself against the source (`CRAWL_DELAY`=0.0) and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

### 🆘 Troubleshooting

- **Run FAILED with BLOCKED** → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
- **Status says CAPPED** → your cap (`maxRecords`) was reached → raise it for a bigger run.
- **Input validation error on start** → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
- **Run TIMED-OUT** → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

### 🔗 Related Actors

- [EIA-923 Byproduct Disposition (Annual Release)](https://apify.com/nexgenwatch/eia923-byproduct-disposition?fpr=2ayu9b) — Structured combustion-byproduct disposition records from the U.S. EIA Form EIA-923 Schedule 8A — Annual Byproduct Disposition sheet, read directly fr…
- [EIA-923 Cooling System Operations (Annual Release)](https://apify.com/nexgenwatch/eia923-cooling-system-operations?fpr=2ayu9b) — Structured power-plant cooling system operating records from the U.S. EIA Form EIA-923 Schedule 8D Cooling System Information, read directly from the…
- [EIA-923 Fuel Receipts & Costs (Monthly, Preliminary)](https://apify.com/nexgenwatch/eia923-fuel-receipts-costs?fpr=2ayu9b) — Structured fuel receipt records from the U.S. EIA Form EIA-923, Page 5 Fuel Receipts and Costs, read directly from the official current-year EIA-923…
- [EIA-923 Non-Utility Source & Disposition (Annual Release)](https://apify.com/nexgenwatch/eia923-nonutility-source-disposition?fpr=2ayu9b) — Structured electricity source-and-disposition flow ledger records from the U.S. EIA Form EIA-923 Schedules 6/7 Source and Disposition sheet, read dir…
- [EIA-923 Plant Generation & Fuel (Monthly, Preliminary)](https://apify.com/nexgenwatch/eia923-plant-generation-fuel?fpr=2ayu9b) — Structured plant generation and fuel records from the U.S. EIA Form EIA-923 Page 1 Generation and Fuel Data, read directly from the official current-…
- [EPA GHGRP Facility-Year Master](https://apify.com/nexgenwatch/epa-ghgrp-facility-year-master?fpr=2ayu9b) — One facility_year_record per row of EPA's GHGRP PUB_DIM_FACILITY table — one Greenhouse Gas Reporting Program facility per reporting year, with the f…
- 🏢 **About NexGenData** — NexGen Watch is NexGenData's fleet of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at [apify.com/nexgenwatch](https://apify.com/nexgenwatch?fpr=2ayu9b).

### ⭐ Found this useful?

If this actor saved you a manual check, a quick **[review on the Apify Store](https://apify.com/nexgenwatch/eia923-generator-unit-net-generation?fpr=2ayu9b)** helps other teams find it. Feature request or a source that changed? Open it from the **Issues** tab — every one is read.

# Actor input Schema

## `plantIds` (type: `array`):

EIA plant_id values, e.g. \["3"]. At least one of plantIds / plantStates / generatorIds / primeMovers / sectorNumbers is REQUIRED — the sheet is never emitted in full.

## `plantStates` (type: `array`):

Two-letter plant state codes, e.g. \["AL"].

## `generatorIds` (type: `array`):

Generator ids (plant-scoped; e.g. \["1"]). Matched case-insensitively; combine with plantIds to target one plant's unit.

## `primeMovers` (type: `array`):

Reported prime-mover codes, e.g. \["ST","CT"].

## `sectorNumbers` (type: `array`):

EIA sector_number values, e.g. \["1"].

## `normalizeMonthly` (type: `boolean`):

If true, emit one record per month (12 per source row) instead of one wide record. Default false (wide).

## `maxRecords` (type: `integer`):

Max records delivered (buyer bound; one charge per delivered record). Hard-capped at 5000.

## `releaseUrl` (type: `string`):

Pin a specific f923\_<year>.zip URL. Default: newest current monthly resolved.

## `userAgent` (type: `string`):

Override the transparent crawler UA.

## `searchText` (type: `string`):

Optional. Keep only rows where any field contains this text (case-insensitive, substring). Applied after the source is read and BEFORE the maxRecords cap, so the cap counts matches and only delivered matches are billed. Zero matches = EMPTY_SELECTION, nothing charged beyond the start fee.

## `fieldMatch` (type: `object`):

Optional. {"column": "text"} keeps rows whose named output column contains the text (case-insensitive); a list of texts means any of them; several columns must all match. Column names are the dataset fields shown in the sample output. Applied BEFORE the maxRecords cap and before billing.

## Actor input object example

```json
{
  "plantIds": [
    "3"
  ],
  "plantStates": [],
  "generatorIds": [],
  "primeMovers": [],
  "sectorNumbers": [],
  "normalizeMonthly": false,
  "maxRecords": 50
}
```

# 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 = {
    "plantIds": [
        "3"
    ],
    "maxRecords": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/eia923-generator-unit-net-generation").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 = {
    "plantIds": ["3"],
    "maxRecords": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/eia923-generator-unit-net-generation").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 '{
  "plantIds": [
    "3"
  ],
  "maxRecords": 50
}' |
apify call nexgenwatch/eia923-generator-unit-net-generation --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/eia923-generator-unit-net-generation"
        }
    }
}
```

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/nUBGL9UuAgZKDxAeM/builds/PNvP1dNGVypI148Zf/openapi.json
