EIA-923 Byproduct Disposition (Annual Release) avatar

EIA-923 Byproduct Disposition (Annual Release)

Pricing

from $13.40 / 1,000 byproduct disposition records

Go to Apify Store
EIA-923 Byproduct Disposition (Annual Release)

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 from the official current-year early-release ZIP on www.eia.gov.

Pricing

from $13.40 / 1,000 byproduct disposition records

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

🔔 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 from the official current-year early-release ZIP on www.eia.gov. One record per reported byproduct line, carried source-native and verbatim.

Output is one byproduct_record row per result; billing is pay-per-event, the value event being one byproduct disposition record (a $0.02 start fee per run, then $0.02 per byproduct disposition 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 Byproduct Disposition (Annual Release) sample output — a table of real byproduct disposition record rows (year, plant_id, by_product_description, disposal_landfill) from run isdegMrRZS8hcgaLu on build 0.1.9

Real rows from run isdegMrRZS8hcgaLu 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):

yearplant_idby_product_descriptiondisposal_landfilldata_statusrelease_date
202510Fly ash from standard boiler/PCD units.FINAL RELEASE — fully edited annual data as published by EIAf923_2025
202510Fly ash from units with dry FGD.FINAL RELEASE — fully edited annual data as published by EIAf923_2025
202510Fly ash from FBC units.FINAL RELEASE — fully edited annual data as published by EIAf923_2025
202510Bottom ash from standard boiler units.FINAL RELEASE — fully edited annual data as published by EIAf923_2025
202510Bottom (bed) ash from FBC units.FINAL RELEASE — fully edited annual data as published by EIAf923_2025
202510FGD Gypsum.FINAL RELEASE — fully edited annual data as published by EIAf923_2025
202510Other FGD byproducts.FINAL RELEASE — fully edited annual data as published by EIAf923_2025
202510Ash from coal gasification (IGCC) units.FINAL RELEASE — fully edited annual data as published by EIAf923_2025

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

✅ 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
  • plant_id (string/null) — e.g. 10
  • by_product_description (string/null) — e.g. Fly ash from standard boiler/PCD units
  • disposal_landfill (string/null) — e.g. .
  • disposal_ponds (string/null) — e.g. .
  • disposal_offsite (string/null) — e.g. .
  • sold (string/null) — e.g. .
  • used_onsite (string/null) — e.g. .
  • used_offsite (string/null) — e.g. .
  • stored_onsite (string/null) — e.g. .
  • stored_offsite (string/null) — e.g. .
  • total (string/null) — e.g. .
  • no_byproducts (string/null) — e.g. Y
  • record_type (string/null) — e.g. byproduct_record
  • data_status (string/null) — e.g. FINAL RELEASE — fully edited annual data as published by EIA
  • compliance_note (string/null) — e.g. reported disposition values only — no compliance/permit/violation determination
  • reporting_period (string/null) — e.g. 2025
  • record_key (string/null) — e.g. eia923-byproduct:10:fly_ash_from_standard_boiler_pcd_units:2025:da9a3ea9397ca331
  • source_url (string/null) — e.g. https://www.eia.gov/electricity/data/eia923/xls/f923_2025.zip
  • source (string/null) — e.g. eia923-byproduct-disposition
  • release_date (string/null) — e.g. f923_2025
  • observed_at (string/null) — e.g. 2026-09-19T02:20:46Z
  • release_checksum (string/null) — e.g. 2025
  • license (string/null) — e.g. U.S. Energy Information Administration (EIA), Form EIA-923, Schedule 8A Annual B
  • 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
  • plant_id (string/null) — e.g. 10
  • by_product_description (string/null) — e.g. Fly ash from standard boiler/PCD units
  • disposal_landfill (string/null) — e.g. .
  • disposal_ponds (string/null) — e.g. .
  • disposal_offsite (string/null) — e.g. .
  • sold (string/null) — e.g. .
  • used_onsite (string/null) — e.g. .
  • used_offsite (string/null) — e.g. .
  • stored_onsite (string/null) — e.g. .
  • stored_offsite (string/null) — e.g. .
  • total (string/null) — e.g. .
  • no_byproducts (string/null) — e.g. Y
  • record_type (string/null) — e.g. byproduct_record
  • data_status (string/null) — e.g. FINAL RELEASE — fully edited annual data as published by EIA
  • compliance_note (string/null) — e.g. reported disposition values only — no compliance/permit/violation determination
  • reporting_period (string/null) — e.g. 2025
  • record_key (string/null) — e.g. eia923-byproduct:10:fly_ash_from_standard_boiler_pcd_units:2025:da9a3ea9397ca331
  • source_url (string/null) — e.g. https://www.eia.gov/electricity/data/eia923/xls/f923_2025.zip
  • source (string/null) — e.g. eia923-byproduct-disposition
  • release_date (string/null) — e.g. f923_2025
  • observed_at (string/null) — e.g. 2026-09-19T02:03:01Z
  • release_checksum (string/null) — e.g. 2025
  • license (string/null) — e.g. U.S. Energy Information Administration (EIA), Form EIA-923, Schedule 8A Annual B
  • 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 byproduct_record per Schedule 8A row: plant_id, reporting period year (reporting_period), by_product_description, the eight disposition quantity columns plus total, the no_byproducts flag, data_status, compliance_note, 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 + 10 × $0.02 byproduct_record = $0.24 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": {
"by_product_description": "Fly ash from standard boiler/PCD units"
}
}

Keeps only rows whose by_product_description contains Fly ash from standard boiler/PCD units (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 isdegMrRZS8hcgaLu, exactly as it lands in the dataset (emails masked, long text shortened):

{
"year": "2025",
"plant_id": "10",
"by_product_description": "Fly ash from standard boiler/PCD units",
"disposal_landfill": ".",
"disposal_ponds": ".",
"disposal_offsite": ".",
"sold": ".",
"used_onsite": ".",
"used_offsite": ".",
"stored_onsite": ".",
"stored_offsite": ".",
"total": ".",
"no_byproducts": "Y",
"record_type": "byproduct_record",
"data_status": "FINAL RELEASE — fully edited annual data as published by EIA",
"compliance_note": "reported disposition values only — no compliance/permit/violation determination is made or implied; 'No Byproducts = Y' is the plant's own report and is carried verbatim",
"reporting_period": "2025",
"record_key": "eia923-byproduct:10:fly_ash_from_standard_boiler_pcd_units:2025:da9a3ea9397ca331",
"source_url": "https://www.eia.gov/electricity/data/eia923/xls/f923_2025.zip",
"source": "eia923-byproduct-disposition",
"release_date": "f923_2025",
"observed_at": "2026-09-19T02:20:46Z",
"release_checksum": "2025",
"license": "U.S. Energy Information Administration (EIA), Form EIA-923, Schedule 8A Annual Byproduct Disposition (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",
"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 byproduct disposition record is charged at the moment it is pushed (byproduct_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, do not aggregate to state, regional, or national totals. Every record carries a data_status field stating this boundary.

Reported disposition — NOT a compliance determination

This actor mirrors what plants reported to EIA. It makes no environmental-compliance determination: it never infers whether a disposition is permitted, compliant, or in violation. Every record carries a compliance_note restating this.

Raw flags carried verbatim — including "No Byproducts = Y"

The disposition cells (Disposal Landfill / Ponds / Offsite, Sold, Used Onsite / Offsite, Stored Onsite / Offsite, Total) and the source no_byproducts flag are carried exactly as reported. Rows where the plant reported No Byproducts = Y are kept, not dropped and not reinterpreted — they are a real reported fact. A . in a quantity cell is the source's own not-applicable marker and is preserved as-is. Set onlyWithByproducts=true if you want to exclude the No-Byproducts rows.

Coverage, cadence & limits

The current early release of Schedule 8A carries roughly 3,325 byproduct rows — about 1.33× the 2,500 delivery floor. That is a modest margin over the floor and is stated plainly: coverage is a single annual early-release snapshot, a majority of rows are No Byproducts = Y, and the figures are preliminary until EIA's final release. This is a focused annual byproduct feed, not a high-volume stream.

Filters

Supply at least one of plantIds or byproductContains — 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 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 8A) — 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

EventFreeBronzeSilverGold
Actor Start (apify-actor-start)$0.02$0.02$0.02$0.02
Byproduct disposition record (byproduct_record)$0.02$0.018$0.016$0.0134

Worked at the live Free-tier price:

  • 8 byproduct disposition records: $0.02 start + 8 × $0.02 = $0.18
  • 25 byproduct disposition records: $0.02 start + 25 × $0.02 = $0.52
  • 2500 byproduct disposition 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: 10 unique rows (0 duplicates collapsed) from f923_2025. billable=10. maxRecords is a hard ceiling on what is delivered and billed, never a target.

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.

⭐ 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.