🔔 EIA-923 Cooling System Operations (Annual Release)

Structured power-plant cooling system operating records from the U.S. EIA Form EIA-923 Schedule 8D Cooling System Information, read directly from the official current-year early-release ZIP on www.eia.gov. One record per plant cooling system per month, carried source-native and verbatim.

Output is one cooling_operation_record row per result; billing is pay-per-event, the value event being one cooling operation record (a $0.02 start fee per run, then $0.02 per cooling operation 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

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

year	month	type_of_cooling_system	method_for_temperatures	data_status	release_date
2025	1	Once through without cooling pond(s) or canal(s)	Measured continuously with a thermometer	FINAL RELEASE — fully edited annual data as published by EIA	f923_2025
2025	2	Once through without cooling pond(s) or canal(s)	Measured continuously with a thermometer	FINAL RELEASE — fully edited annual data as published by EIA	f923_2025
2025	3	Once through without cooling pond(s) or canal(s)	Measured continuously with a thermometer	FINAL RELEASE — fully edited annual data as published by EIA	f923_2025
2025	4	Once through without cooling pond(s) or canal(s)	Measured continuously with a thermometer	FINAL RELEASE — fully edited annual data as published by EIA	f923_2025
2025	5	Once through without cooling pond(s) or canal(s)	Measured continuously with a thermometer	FINAL RELEASE — fully edited annual data as published by EIA	f923_2025
2025	6	Once through without cooling pond(s) or canal(s)	Measured continuously with a thermometer	FINAL RELEASE — fully edited annual data as published by EIA	f923_2025
2025	7	Once through without cooling pond(s) or canal(s)	Measured continuously with a thermometer	FINAL RELEASE — fully edited annual data as published by EIA	f923_2025
2025	8	Once through without cooling pond(s) or canal(s)	Measured continuously with a thermometer	FINAL RELEASE — fully edited annual data as published by EIA	f923_2025

The run finished with the status message: NORMAL: 12 unique rows (0 duplicates collapsed) from f923_2025. 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):

• year (string/null) — e.g. 2025
• month (string/null) — e.g. 1
• plant_id (string/null) — e.g. 10
• cooling_system_id (string/null) — e.g. 1-2
• type_of_cooling_system (string/null) — e.g. Once through without cooling pond(s) or canal(s)
• cooling_system_status (string/null) — e.g. OP
• hours_in_service (string/null) — e.g. 744
• chlorine_thousand_lbs (string/null) — e.g. 0
• diversion_rate_gallons_per_minute (string/null) — e.g. 0
• withdrawal_rate_gallons_per_minute (string/null) — e.g. 267414
• discharge_rate_gallons_per_minute (string/null) — e.g. 267414
• consumption_rate_gallons_per_minute (string/null) — e.g. 0
• method_for_flow_rates (string/null) — e.g. Estimated based on stated pump capacity and pump running time
• intake_average_temperature_f (string/null) — e.g. 47
• intake_maximum_temperature_f (string/null) — e.g. 54
• discharge_average_temperature_f (string/null) — e.g. 55
• discharge_maximum_temperature_f (string/null) — e.g. 70
• method_for_temperatures (string/null) — e.g. Measured continuously with a thermometer
• diversion_volume_million_gallons (string/null) — e.g. 0
• withdrawal_volume_million_gallons (string/null) — e.g. 11938.14
• discharge_volume_million_gallons (string/null) — e.g. 11938.14
• consumption_volume_million_gallons (string/null) — e.g. 0
• record_type (string/null) — e.g. cooling_operation_record
• data_status (string/null) — e.g. FINAL RELEASE — fully edited annual data as published by EIA
• record_key (string/null) — e.g. eia923-8d:10:1:1-2:d70344338a9383c7
• source_url (string/null) — e.g. https://www.eia.gov/electricity/data/eia923/xls/f923_2025.zip
• source (string/null) — e.g. eia923-cooling-system-operations
• release_date (string/null) — e.g. f923_2025
• observed_at (string/null) — e.g. 2026-09-19T02:16:36Z
• release_checksum (string/null) — e.g. 2025
• license (string/null) — e.g. U.S. Energy Information Administration (EIA), Form EIA-923, Schedule 8D Cooling
• attribution (string/null) — e.g. U.S. Energy Information Administration — Form EIA-923 (https://www.eia.gov/elect
• 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

• year (string/null) — e.g. 2025
• month (string/null) — e.g. 1
• plant_id (string/null) — e.g. 10
• cooling_system_id (string/null) — e.g. 1-2
• type_of_cooling_system (string/null) — e.g. Once through without cooling pond(s) or canal(s)
• cooling_system_status (string/null) — e.g. OP
• hours_in_service (string/null) — e.g. 744
• chlorine_thousand_lbs (string/null) — e.g. 0
• diversion_rate_gallons_per_minute (string/null) — e.g. 0
• withdrawal_rate_gallons_per_minute (string/null) — e.g. 267414
• discharge_rate_gallons_per_minute (string/null) — e.g. 267414
• consumption_rate_gallons_per_minute (string/null) — e.g. 0
• method_for_flow_rates (string/null) — e.g. Estimated based on stated pump capacity and pump running time
• intake_average_temperature_f (string/null) — e.g. 47
• intake_maximum_temperature_f (string/null) — e.g. 54
• discharge_average_temperature_f (string/null) — e.g. 55
• discharge_maximum_temperature_f (string/null) — e.g. 70
• method_for_temperatures (string/null) — e.g. Measured continuously with a thermometer
• diversion_volume_million_gallons (string/null) — e.g. 0
• withdrawal_volume_million_gallons (string/null) — e.g. 11938.14
• discharge_volume_million_gallons (string/null) — e.g. 11938.14
• consumption_volume_million_gallons (string/null) — e.g. 0
• record_type (string/null) — e.g. cooling_operation_record
• data_status (string/null) — e.g. FINAL RELEASE — fully edited annual data as published by EIA
• record_key (string/null) — e.g. eia923-8d:10:1:1-2:d70344338a9383c7
• source_url (string/null) — e.g. https://www.eia.gov/electricity/data/eia923/xls/f923_2025.zip
• source (string/null) — e.g. eia923-cooling-system-operations
• release_date (string/null) — e.g. f923_2025
• observed_at (string/null) — e.g. 2026-09-19T02:02:13Z
• release_checksum (string/null) — e.g. 2025
• license (string/null) — e.g. U.S. Energy Information Administration (EIA), Form EIA-923, Schedule 8D Cooling
• attribution (string/null) — e.g. U.S. Energy Information Administration — Form EIA-923 (https://www.eia.gov/elect
• 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

One cooling_operation_record per 8D row, carried verbatim, including:

• year, month, plant_id, cooling_system_id, type_of_cooling_system, cooling_system_status
• hours_in_service, flow rates (withdrawal_rate_gallons_per_minute, discharge_rate…, consumption_rate…)
• intake/discharge temperatures, and monthly volumes (withdrawal_volume_million_gallons, …)
• data_status (early-release boundary), release_date, release_checksum, source_url, license

⚙️ Sample inputs

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

{
  "plantIds": [
    "10"
  ],
  "maxRecords": 50
}

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

2. A smaller, narrowed run

{
  "plantIds": [
    "10"
  ],
  "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

{
  "plantIds": [
    "10"
  ],
  "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

{
  "plantIds": [
    "10"
  ],
  "maxRecords": 50,
  "fieldMatch": {
    "method_for_temperatures": "Measured continuously with a thermometer"
  }
}

Keeps only rows whose method_for_temperatures contains Measured continuously with a thermometer (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 JeSYDeg7KK4s3mkTP, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "year": "2025",
  "month": "1",
  "plant_id": "10",
  "cooling_system_id": "1-2",
  "type_of_cooling_system": "Once through without cooling pond(s) or canal(s)",
  "cooling_system_status": "OP",
  "hours_in_service": "744",
  "chlorine_thousand_lbs": "0",
  "diversion_rate_gallons_per_minute": "0",
  "withdrawal_rate_gallons_per_minute": "267414",
  "discharge_rate_gallons_per_minute": "267414",
  "consumption_rate_gallons_per_minute": "0",
  "method_for_flow_rates": "Estimated based on stated pump capacity and pump running time",
  "intake_average_temperature_f": "47",
  "intake_maximum_temperature_f": "54",
  "discharge_average_temperature_f": "55",
  "discharge_maximum_temperature_f": "70",
  "method_for_temperatures": "Measured continuously with a thermometer",
  "diversion_volume_million_gallons": "0",
  "withdrawal_volume_million_gallons": "11938.14",
  "discharge_volume_million_gallons": "11938.14",
  "consumption_volume_million_gallons": "0",
  "record_type": "cooling_operation_record",
  "data_status": "FINAL RELEASE — fully edited annual data as published by EIA",
  "record_key": "eia923-8d:10:1:1-2:d70344338a9383c7",
  "source_url": "https://www.eia.gov/electricity/data/eia923/xls/f923_2025.zip",
  "source": "eia923-cooling-system-operations",
  "release_date": "f923_2025",
  "observed_at": "2026-09-19T02:16:36Z",
  "release_checksum": "2025",
  "license": "U.S. Energy Information Administration (EIA), Form EIA-923, Schedule 8D Cooling System Information (current annual release) — U.S. Government work, public domain. When the file is an early release the data is not fully edited and must not b",
  "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 cooling operation record is charged at the moment it is pushed (cooling_operation_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

🔧 How it works

⚠️ Early-release boundary (read this)

This is EIA EARLY-RELEASE data — not fully edited. Per EIA, it do not aggregate to state, regional, or national totals. Every record carries a data_status field stating this boundary. These are operating facts as filed for the reporting period — never a live or real-time plant-status claim.

Filters

Supply at least one of plantIds, months, or coolingSystemStatuses — the 8D 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 early-release f923_<year>er.zip is read — www.eia.gov/robots.txt disallows /archive/, which is never fetched. EIA's own early-release watermark column is dropped and replaced by the clean data_status field. No third-party content or logos.

Source & licence

U.S. Energy Information Administration, Form EIA-923 (Schedule 8D) — U.S. Government work, public domain (early release). 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
Cooling operation record (cooling_operation_record)	$0.02	$0.018	$0.016	$0.0134

Worked at the live Free-tier price:

• 8 cooling operation records: $0.02 start + 8 × $0.02 = $0.18
• 25 cooling operation records: $0.02 start + 25 × $0.02 = $0.52
• 2500 cooling operation 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_2025. 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 Air Emissions Control Operations (Annual Release) — Structured air-emissions-control operating records from the U.S. EIA Form EIA-923 Schedule 8C — Air Emissions Control Information sheet, read directl…
• EIA-923 Boiler Fuel Data (Monthly, Preliminary) — Structured boiler-level fuel consumption records from the U.S. EIA Form EIA-923 Page 3 Boiler Fuel Data, read directly from the official current-year…
• EIA-923 Byproduct Disposition (Annual Release) — Structured combustion-byproduct disposition records from the U.S. EIA Form EIA-923 Schedule 8A — Annual Byproduct Disposition sheet, read directly fr…
• EIA-923 Fuel Receipts & Costs (Monthly, Preliminary) — 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 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…
• EIA-923 Non-Utility Source & Disposition (Annual Release) — 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…
• 🏢 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.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.