# EIA-861 Advanced Metering (AMR / AMI / Standard) (`nexgenwatch/eia861-advanced-metering`) Actor Structured advanced-meter technology adoption records from the U.S. EIA Form EIA-861 Annual Electric Power Industry Report, read directly from the official current-year ZIP on www.eia.gov. - **URL**: https://apify.com/nexgenwatch/eia861-advanced-metering.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 metering adoption 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-861 Advanced Metering (AMR / AMI / Standard) Structured **advanced-meter technology adoption** records from the U.S. EIA **Form EIA-861** Annual Electric Power Industry Report, read directly from the official current-year ZIP on `www.eia.gov`. One record per utility-state row of `Advanced_Meters_.xlsx`, carried source-native and **verbatim**. Output is one `metering_adoption_record` row per result; billing is pay-per-event, the value event being one metering adoption record (a $0.02 start fee per run, then $0.02 per metering adoption 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-861 Advanced Metering (AMR / AMI / Standard) sample output β€” a table of real metering adoption record rows (data_year, utility_number, utility_name, ownership) from run doejvCOAfOG9SOsTd on build 0.1.5](https://api.apify.com/v2/key-value-stores/80Y7h3rmVN5CWK7Mw/records/eia861-advanced-metering-sample)](https://apify.com/nexgenwatch/eia861-advanced-metering?fpr=2ayu9b) Real rows from run `doejvCOAfOG9SOsTd` 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): | data_year | utility_number | utility_name | ownership | state | ba_code | |---|---|---|---|---|---| | 2024 | 34 | City of Abbeville - (SC) | Municipal | SC | DUK | | 2024 | 162 | Aiken Electric Coop Inc | Cooperative | SC | SC | | 2024 | 1170 | Bamberg Board of Public Works | Municipal | SC | SC | | 2024 | 1613 | Berkeley Electric Coop Inc | Cooperative | SC | SC | | 2024 | 1763 | Black River Electric Coop, Inc - (SC) | Cooperative | SC | SC | | 2024 | 1890 | Blue Ridge Electric Coop Inc - (SC) | Cooperative | SC | DUK | | 2024 | 2212 | Broad River Electric Coop, Inc | Cooperative | SC | DUK | | 2024 | 2890 | City of Camden | Municipal | SC | CPLE | The run finished with the status message: `NORMAL: 46 unique rows (0 duplicates collapsed) from f8612024. billable=46` ### βœ… 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`): - `data_year` (string/null) β€” e.g. `2024` - `utility_number` (string/null) β€” e.g. `34` - `utility_name` (string/null) β€” e.g. `City of Abbeville - (SC)` - `ownership` (string/null) β€” e.g. `Municipal` - `short_form` (string/null) β€” e.g. `Y` - `state` (string/null) β€” e.g. `SC` - `ba_code` (string/null) β€” e.g. `DUK` - `amr_residential` (string/null) β€” e.g. `3061` - `amr_commercial` (string/null) β€” e.g. `473` - `amr_industrial` (string/null) β€” e.g. `0` - `amr_transportation` (string/null) β€” e.g. `.` - `amr_total` (string/null) β€” e.g. `3534` - `ami_residential` (string/null) β€” e.g. `0` - `ami_commercial` (string/null) β€” e.g. `0` - `ami_industrial` (string/null) β€” e.g. `0` - `ami_transportation` (string/null) β€” e.g. `.` - `ami_total` (string/null) β€” e.g. `0` - `han_residential` (string/null) β€” e.g. `.` - `han_commercial` (string/null) β€” e.g. `.` - `han_industrial` (string/null) β€” e.g. `.` - `han_transportation` (string/null) β€” e.g. `.` - `han_total` (string/null) β€” e.g. `.` - `standard_residential` (string/null) β€” e.g. `.` - `standard_commercial` (string/null) β€” e.g. `.` - `standard_industrial` (string/null) β€” e.g. `.` - `standard_transportation` (string/null) β€” e.g. `.` - `standard_total` (string/null) β€” e.g. `.` - `total_meters_residential` (string/null) β€” e.g. `3061` - `total_meters_commercial` (string/null) β€” e.g. `473` - `total_meters_industrial` (string/null) β€” e.g. `0` - `total_meters_transportation` (string/null) β€” e.g. `0` - `total_meters_total` (string/null) β€” e.g. `3534` - `energy_served_ami_mwh_residential` (string/null) β€” e.g. `0` - `energy_served_ami_mwh_commercial` (string/null) β€” e.g. `0` - `energy_served_ami_mwh_industrial` (string/null) β€” e.g. `0` - `energy_served_ami_mwh_transportation` (string/null) β€” e.g. `.` - `energy_served_ami_mwh_total` (string/null) β€” e.g. `0` - `daily_digital_access_residential` (string/null) β€” e.g. `.` - `daily_digital_access_commercial` (string/null) β€” e.g. `.` - `daily_digital_access_industrial` (string/null) β€” e.g. `.` - `daily_digital_access_transportation` (string/null) β€” e.g. `.` - `daily_digital_access_total` (string/null) β€” e.g. `.` - `direct_load_control_residential` (string/null) β€” e.g. `.` - `direct_load_control_commercial` (string/null) β€” e.g. `.` - `direct_load_control_industrial` (string/null) β€” e.g. `.` - `direct_load_control_transportation` (string/null) β€” e.g. `.` - `direct_load_control_total` (string/null) β€” e.g. `.` - `record_type` (string/null) β€” e.g. `metering_adoption_record` - `sheet` (string/null) β€” e.g. `states` - `is_territory` (string/null) β€” e.g. `N` - `meter_classes` (string/null) β€” e.g. `AMR, AMI, Home Area Network, Standard (non AMR/AMI), Total` - `net_metering_note` (string/null) β€” e.g. `meter TECHNOLOGY adoption (AMR/AMI/standard meter counts a utility operates) β€” N` - `release_year` (string/null) β€” e.g. `2024` - `release_file` (string/null) β€” e.g. `f8612024.zip` - `release_note` (string/null) β€” e.g. `EIA-861 is an ANNUAL dataset; each year's file replaces (does not append to) the` - `record_key` (string/null) β€” e.g. `eia861-advmtr:2024:34:SC:f218c0c71e55` - `source_url` (string/null) β€” e.g. `https://www.eia.gov/electricity/data/eia861/zip/f8612024.zip` - `source` (string/null) β€” e.g. `eia861-advanced-metering` - `release_date` (string/null) β€” e.g. `f8612024` - `observed_at` (string/null) β€” e.g. `2026-09-19T04:51:41Z` - `release_checksum` (string/null) β€” e.g. `2024` - `license` (string/null) β€” e.g. `U.S. Energy Information Administration (EIA), Form EIA-861 Annual Electric Power` - `attribution` (string/null) β€” e.g. `U.S. Energy Information Administration β€” Form EIA-861 (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** - `data_year` (string/null) β€” e.g. `2024` - `utility_number` (string/null) β€” e.g. `34` - `utility_name` (string/null) β€” e.g. `City of Abbeville - (SC)` - `ownership` (string/null) β€” e.g. `Municipal` - `short_form` (string/null) β€” e.g. `Y` - `state` (string/null) β€” e.g. `SC` - `ba_code` (string/null) β€” e.g. `DUK` - `amr_residential` (string/null) β€” e.g. `3061` - `amr_commercial` (string/null) β€” e.g. `473` - `amr_industrial` (string/null) β€” e.g. `0` - `amr_transportation` (string/null) β€” e.g. `.` - `amr_total` (string/null) β€” e.g. `3534` - `ami_residential` (string/null) β€” e.g. `0` - `ami_commercial` (string/null) β€” e.g. `0` - `ami_industrial` (string/null) β€” e.g. `0` - `ami_transportation` (string/null) β€” e.g. `.` - `ami_total` (string/null) β€” e.g. `0` - `han_residential` (string/null) β€” e.g. `.` - `han_commercial` (string/null) β€” e.g. `.` - `han_industrial` (string/null) β€” e.g. `.` - `han_transportation` (string/null) β€” e.g. `.` - `han_total` (string/null) β€” e.g. `.` - `standard_residential` (string/null) β€” e.g. `.` - `standard_commercial` (string/null) β€” e.g. `.` - `standard_industrial` (string/null) β€” e.g. `.` - `standard_transportation` (string/null) β€” e.g. `.` - `standard_total` (string/null) β€” e.g. `.` - `total_meters_residential` (string/null) β€” e.g. `3061` - `total_meters_commercial` (string/null) β€” e.g. `473` - `total_meters_industrial` (string/null) β€” e.g. `0` - `total_meters_transportation` (string/null) β€” e.g. `0` - `total_meters_total` (string/null) β€” e.g. `3534` - `energy_served_ami_mwh_residential` (string/null) β€” e.g. `0` - `energy_served_ami_mwh_commercial` (string/null) β€” e.g. `0` - `energy_served_ami_mwh_industrial` (string/null) β€” e.g. `0` - `energy_served_ami_mwh_transportation` (string/null) β€” e.g. `.` - `energy_served_ami_mwh_total` (string/null) β€” e.g. `0` - `daily_digital_access_residential` (string/null) β€” e.g. `.` - `daily_digital_access_commercial` (string/null) β€” e.g. `.` - `daily_digital_access_industrial` (string/null) β€” e.g. `.` - `daily_digital_access_transportation` (string/null) β€” e.g. `.` - `daily_digital_access_total` (string/null) β€” e.g. `.` - `direct_load_control_residential` (string/null) β€” e.g. `.` - `direct_load_control_commercial` (string/null) β€” e.g. `.` - `direct_load_control_industrial` (string/null) β€” e.g. `.` - `direct_load_control_transportation` (string/null) β€” e.g. `.` - `direct_load_control_total` (string/null) β€” e.g. `.` - `record_type` (string/null) β€” e.g. `metering_adoption_record` - `sheet` (string/null) β€” e.g. `states` - `is_territory` (string/null) β€” e.g. `N` - `meter_classes` (string/null) β€” e.g. `AMR, AMI, Home Area Network, Standard (non AMR/AMI), Total` - `net_metering_note` (string/null) β€” e.g. `meter TECHNOLOGY adoption (AMR/AMI/standard meter counts a utility operates) β€” N` - `release_year` (string/null) β€” e.g. `2024` - `release_file` (string/null) β€” e.g. `f8612024.zip` - `release_note` (string/null) β€” e.g. `EIA-861 is an ANNUAL dataset; each year's file replaces (does not append to) the` - `record_key` (string/null) β€” e.g. `eia861-advmtr:2024:34:SC:f218c0c71e55` - `source_url` (string/null) β€” e.g. `https://www.eia.gov/electricity/data/eia861/zip/f8612024.zip` - `source` (string/null) β€” e.g. `eia861-advanced-metering` - `release_date` (string/null) β€” e.g. `f8612024` - `observed_at` (string/null) β€” e.g. `2026-09-19T04:27:18Z` - `release_checksum` (string/null) β€” e.g. `2024` - `license` (string/null) β€” e.g. `U.S. Energy Information Administration (EIA), Form EIA-861 Annual Electric Power` - `attribution` (string/null) β€” e.g. `U.S. Energy Information Administration β€” Form EIA-861 (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 `metering_adoption_record` per utility-state row, carried verbatim: - utility characteristics: `data_year`, `utility_number`, `utility_name`, `ownership`, `short_form`, `state`, `ba_code` - per-sector counts (`residential`, `commercial`, `industrial`, `transportation`, `total`) for every meter class: **AMR** (Automated Meter Reading) `amr_*`, **AMI** (Advanced Metering Infrastructure) `ami_*`, **Home Area Network** `han_*`, **Standard (non AMR/AMI)** `standard_*`, and **Total Meters** `total_meters_*` - technology dimensions: AMI energy served (MWh) `energy_served_ami_mwh_*`, customers with daily digital access `daily_digital_access_*`, customers with direct load control `direct_load_control_*` - `is_territory`, `meter_classes`, `net_metering_note`, `release_year`, `release_file`, `release_note`, `source_url` EIA's `.` not-applicable marker is carried **exactly as published** β€” never coerced to 0. ### βš™οΈ Sample inputs **1. Quick start β€” the Store example (this is what the sample above came from)** ```json { "states": [ "SC" ], "maxRecords": 50 } ``` The sample run charged exactly: 1 Γ— $0.02 apify-actor-start + 46 Γ— $0.02 metering_adoption_record = **$0.94** on the Free tier β€” every delivered row was billed. **2. A smaller, narrowed run** ```json { "states": [ "SC" ], "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 { "states": [ "SC" ], "maxRecords": 3000 } ``` Up to 3000 rows (the schema default for `maxRecords`) β€” about $60.02 on the Free tier ($0.02 start + 3000 Γ— $0.02) if the source has that many. **4. A filtered run** ```json { "states": [ "SC" ], "maxRecords": 50, "fieldMatch": { "utility_name": "City of Abbeville - (SC)" } } ``` Keeps only rows whose `utility_name` contains `City of Abbeville - (SC)` (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 `doejvCOAfOG9SOsTd`, exactly as it lands in the dataset (emails masked, long text shortened): ```json { "data_year": "2024", "utility_number": "34", "utility_name": "City of Abbeville - (SC)", "ownership": "Municipal", "short_form": "Y", "state": "SC", "ba_code": "DUK", "amr_residential": "3061", "amr_commercial": "473", "amr_industrial": "0", "amr_transportation": ".", "amr_total": "3534", "ami_residential": "0", "ami_commercial": "0", "ami_industrial": "0", "ami_transportation": ".", "ami_total": "0", "han_residential": ".", "han_commercial": ".", "han_industrial": ".", "han_transportation": ".", "han_total": ".", "standard_residential": ".", "standard_commercial": ".", "standard_industrial": ".", "standard_transportation": ".", "standard_total": ".", "total_meters_residential": "3061", "total_meters_commercial": "473", "total_meters_industrial": "0", "total_meters_transportation": "0", "total_meters_total": "3534", "energy_served_ami_mwh_residential": "0", "energy_served_ami_mwh_commercial": "0", "energy_served_ami_mwh_industrial": "0", "energy_served_ami_mwh_transportation": ".", "energy_served_ami_mwh_total": "0", "daily_digital_access_residential": ".", "daily_digital_access_commercial": ".", "daily_digital_access_industrial": ".", "daily_digital_access_transportation": ".", "daily_digital_access_total": ".", "direct_load_control_residential": ".", "direct_load_control_commercial": ".", "direct_load_control_industrial": ".", "direct_load_control_transportation": ".", "direct_load_control_total": ".", "record_type": "metering_adoption_record", "sheet": "states", "is_territory": "N", "meter_classes": "AMR, AMI, Home Area Network, Standard (non AMR/AMI), Total", "net_metering_note": "meter TECHNOLOGY adoption (AMR/AMI/standard meter counts a utility operates) β€” NOT customer generation or net metering; for customers who generate their own power see the EIA-861 net-metering data, a separate dataset", "release_year": "2024", "release_file": "f8612024.zip", "release_note": "EIA-861 is an ANNUAL dataset; each year's file replaces (does not append to) the prior year", "record_key": "eia861-advmtr:2024:34:SC:f218c0c71e55", "source_url": "https://www.eia.gov/electricity/data/eia861/zip/f8612024.zip", "source": "eia861-advanced-metering", "release_date": "f8612024", "observed_at": "2026-09-19T04:51:41Z", "release_checksum": "2024", "license": "U.S. Energy Information Administration (EIA), Form EIA-861 Annual Electric Power Industry Report, Advanced Metering β€” U.S. Government work, public domain. Annual dataset; each year replaces the prior year. Acknowledgement: data from the U.S", "attribution": "U.S. Energy Information Administration β€” Form EIA-861 (https://www.eia.gov/electricity/data/eia861/)" } ``` ### πŸ”§ How it works **Source.** The actor reads www.eia.gov β€” endpoints: `https://www.eia.gov`, `https://www.eia.gov/electricity/data/eia861/`, `https://www.eia.gov/electricity/data/eia861/zip/f861`. 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 metering adoption record is charged at the moment it is pushed (`metering_adoption_record`); a row that fails to charge is not delivered, so the dataset count always equals the charged count. **πŸ”§ How it works** **Meter technology adoption β€” NOT net metering** This actor reports how many meters of each **technology class** a utility operates. It is **not** the EIA-861 **net-metering** dataset (customers who generate their own power). A `net_metering_note` states this distinction on every record: **meter technology adoption β‰  customer generation.** **Two-level header integrity** The sheet has a **top group row** (AMR / AMI / Standard / …) and a **sub-header row** (Residential / Commercial / Industrial / Transportation / Total). A **schema canary over both rows** fails loud if the meter-class groups or the utility fields drift β€” the actor refuses to bill on a changed layout. **Annual replacement** EIA-861 is an **annual** dataset β€” each year's file **replaces** (does not append to) the prior year. Every record carries the release year and source file so a buyer always knows the vintage. **Filters** Supply **at least one** of `states`, `utilityNumbers`, or `ownerships` β€” the file is never emitted in full. `maxRecords` caps delivery (one charge per delivered record, hard cap 6000). **Robots & door** `www.eia.gov/robots.txt` disallows `/archive/` β€” only the **current** `f861.zip` is read, never the archive editions. No third-party content or logos; no implied endorsement. **Source & licence** U.S. Energy Information Administration, Form EIA-861 (Advanced Metering) β€” U.S. Government work, **public domain**. Acknowledgement: data from the U.S. Energy Information Administration (https://www.eia.gov/electricity/data/eia861/). **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 | | Metering adoption record (`metering_adoption_record`) | $0.02 | $0.018 | $0.016 | $0.0134 | Worked at the live Free-tier price: - 8 metering adoption records: $0.02 start + 8 Γ— $0.02 = **$0.18** - 25 metering adoption records: $0.02 start + 25 Γ— $0.02 = **$0.52** - 3000 metering adoption records: $0.02 start + 3000 Γ— $0.02 = **$60.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: 46 unique rows (0 duplicates collapsed) from f8612024. billable=46`. `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 3000). 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-860M Monthly Generator Inventory](https://apify.com/nexgenwatch/eia-860m-monthly-generator-inventory?fpr=2ayu9b) β€” One structured generator_record per generating unit in EIA's monthly Form EIA-860M inventory β€” entity, plant, state, balancing authority, technology,… - [EIA Generator Ownership Link Master](https://apify.com/nexgenwatch/eia-generator-ownership-link-master?fpr=2ayu9b) β€” One generator_ownership_record per row of EIA-860's Ownership worksheet β€” the ownership edge linking a plant/generator to an owning organisation, wit… - [EIA-Renewable / Storage Asset Detail](https://apify.com/nexgenwatch/eia-renewable-storage-asset-detail?fpr=2ayu9b) β€” One renewable_storage_record per generator row of EIA-860's wind, solar and energy-storage worksheets β€” the technology-specific fields of each worksh… - [EIA-861 Annual Sales to Ultimate Customers (final)](https://apify.com/nexgenwatch/eia861-annual-sales-final?fpr=2ayu9b) β€” Structured annual final retail electricity sales from the U.S. Energy Information Administration Form EIA-861, read directly from the official curren… - [EIA-861 Filing Frame (schedule presence per utility)](https://apify.com/nexgenwatch/eia861-filing-frame?fpr=2ayu9b) β€” Structured filing-frame records from the U.S. EIA Form EIA-861 Annual Electric Power Industry Report, read directly from the official current-year ZI… - [EIA-861 Utility Service Territory (Counties)](https://apify.com/nexgenwatch/eia861-utility-service-territory?fpr=2ayu9b) β€” Structured utility service-territory records from the U.S. EIA Form EIA-861 Annual Electric Power Industry Report, read directly from the official cu… - 🏒 **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/eia861-advanced-metering?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 ## `states` (type: `array`): Two-letter state/territory codes, e.g. \["SC","TX"]. At least one of states / utilityNumbers / ownerships is REQUIRED β€” the file is never emitted in full. ## `utilityNumbers` (type: `array`): EIA utility_number values, e.g. \["34"]. ## `ownerships` (type: `array`): Ownership type as published (UPPERCASE), e.g. \["MUNICIPAL","INVESTOR OWNED","COOPERATIVE"]. ## `year` (type: `string`): Pin a specific data year, e.g. "2024". Default: the latest annual f861 file. ## `maxRecords` (type: `integer`): Max utility-state advanced-metering records delivered (buyer bound; one charge per delivered record). Hard-capped at 6000. ## `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 { "states": [ "SC" ], "utilityNumbers": [], "ownerships": [], "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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "states": [ "SC" ], "maxRecords": 50 }; // Run the Actor and wait for it to finish const run = await client.actor("nexgenwatch/eia861-advanced-metering").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "states": ["SC"], "maxRecords": 50, } # Run the Actor and wait for it to finish run = client.actor("nexgenwatch/eia861-advanced-metering").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 '{ "states": [ "SC" ], "maxRecords": 50 }' | apify call nexgenwatch/eia861-advanced-metering --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/eia861-advanced-metering" } } } ``` 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 ` 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/LBtU7ngyBFpb3K6RR/builds/LH1XpOBhcBxWoflbz/openapi.json