HUMXN, a marketplace, states "Field inspections, maintenance records, sensor and grid data" for energy and utilities, and Mercor's manufacturing listing names "utilities and energy operators" (both read 2026-11-17).
18 CFR 388.113(c)(2) defines the engineering, vulnerability and design details that count as critical energy infrastructure information (CEII), and GDPR and CCPA reach any record that names a customer.
No buyer page checked publishes an energy-specific price, and every figure here is a dated claim of the party that states it. Energy and utility records are one sector in AI training data licensing.
DataPacts Editorial Team checked the buyer pages and rules cited here on 2026-11-09 and 2026-11-17, following how we source, date and check every figure.
What Energy and Utility Companies Hold That AI Buyers Ask For
Energy and utility companies hold three kinds of records that buyers' pages describe: field inspection and maintenance records, imagery of assets, and sensor, meter and grid data.
Field Inspections, Maintenance and Work-Order Records
A utility's own maintenance history, the inspections, work orders and correction records for its assets, is the record type buyers' pages name for energy.
HUMXN lists "field inspections, maintenance records" in its energy line, and Mercor's manufacturing listing asks for work orders and inspection reports, alarm logs and process data, with asset photos, drone imagery and scans linked to work orders as nice to have.
It names Maximo and OSIsoft PI among the tools its records come from (read 2026-11-17).
Mercor's "not a fit" line for that listing is data restricted by customer contracts. Photos or drone imagery of substations or lines can show design details, which the infrastructure section below treats separately.
Sensor, Meter and Grid Telemetry Held Under Contract
Sensor, meter and grid telemetry is the measurement stream a device writes, and a utility often holds it under a contract with the device maker, a regulator or a customer. HUMXN names "sensor and grid data" and gives no record list beyond that and no price (read 2026-11-17).
Regulation (EU) 2023/2854 Art. 4(13)-(14) lets a data holder use non-personal product data only under its contract with the user and bars making it available to third parties outside that contract, and it applies from 2025-09-12. Art. 3(1) requires access by design for products placed on the market after 2026-09-12, which is how connected equipment from device makers falls under the EU Data Act and AI training data.
Interval and sensor readings tied to a customer account or address are personal data, so the customer section below applies to them first.
Buyer and Marketplace Statements That Name Energy
Two programs name energy or utility records on their own pages, checked 2026-11-17, and neither publishes an energy-specific price.
The table compares what each states for energy, as of 2026-11-17, in alphabetical order.
| Program | Role | What it names for energy, or excludes | Source |
|---|---|---|---|
| HUMXN | M | "Energy & utilities: Field inspections, maintenance records, sensor and grid data" among 24 industries | humxn.io/sell-company-data |
| Mercor Manufacturing & Industrial Company listing | B | industries include "utilities and energy operators"; work orders and inspection reports, alarm logs and process data, asset imagery; 20 to 2,000 employees; not a fit: data restricted by customer contracts | api.data.mercor.com listings /manufacturing |
B = buyer or licensee program; M = marketplace. "Not stated" does not mean allowed.
Mercor's program page lists 8 target industries without energy (checked 2026-11-09), Handshake AI's 11 industries do not name energy (checked 2026-11-09) and micro1's six functional areas do not name it either (checked 2026-11-09).
A buyer that does not name energy has not closed to it, and HUMXN as a marketplace is a different role from Mercor as a buyer program. Each program's terms sit in payouts and program terms compared.
Critical Infrastructure Information Comes Out Before Any License
Grid engineering and vulnerability details are the part of an energy archive that federal rules single out, so the company decides which records fall under that line before it describes any set to a buyer.
What 18 CFR 388.113 Defines as CEII
18 CFR 388.113(c)(2) defines critical energy infrastructure information as specific engineering, vulnerability or detailed design information about proposed or existing critical infrastructure.
It must meet four tests: it relates details about the production, generation, transportation, transmission or distribution of energy; it could be useful to a person planning an attack on critical infrastructure; it is exempt from mandatory disclosure under the Freedom of Information Act, 5 U.S.C. 552; and it does not simply give the general location of the critical infrastructure (eCFR text as of 2026-11-10, read 2026-11-17).
Paragraph (c)(1) separately covers critical electric infrastructure information that the Commission or the Secretary of Energy designates under section 215A(d) of the Federal Power Act, exempt under 5 U.S.C. 552(b)(3).
Paragraph (a) limits the section to CEII "submitted to or generated by the Commission", so it does not classify every utility record, and paragraph (f)(3) requires entities that receive CEII the Commission voluntarily shares to sign a non-disclosure agreement or an acknowledgement and agreement.
In practice a company treats detailed design and vulnerability information as outside the licensed set unless counsel clears it. The handling rules of NERC CIP for bulk-system cyber information are not summarized on this page.
Technical Data an Annotator Abroad Could Receive
Controlled technical data in an energy archive can be exported when it reaches a foreign person, even inside the United States. 15 CFR 734.13 treats release of controlled technology to a foreign person in the United States as a deemed export to that person's most recent country of citizenship or permanent residency (paragraph (b)). micro1 states in s.5.7 of its data license terms that export-controlled or ITAR/EAR-restricted information is excluded unless the Order Form allows it (terms last updated 2026-11-12, re-read 2026-11-16).
Whether a given file is controlled is the company's own question, and this page does not answer it; the rules are set out in export controls and licensing technical data to AI buyers.
Customer and Meter Records: Privacy Rules Before a License
A utility's customer records name households and businesses at every step, from the billing account to the interval reading, and each group of rules attaches to the person named.
The table lists the two instruments stated here, as of 2026-11-17.
| Jurisdiction | Rule | What it requires | In force | Source |
|---|---|---|---|---|
| European Union | Regulation (EU) 2016/679 (GDPR) | personal data of customers and staff needs a legal basis and notices | applies from 2018-05-25 | eur-lex.europa.eu |
| California | Cal. Civ. Code 1798.120 (CCPA) | right to opt out of sale or sharing | 2020-01-01 | cppa.ca.gov |
State utility commission smart-meter rules, Directive (EU) 2019/944 data-access provisions and any pending smart-meter bills are not summarized on this page.
Smart-Meter and Account Records
Interval readings, billing accounts and service addresses relate to an identifiable customer, so a utility licenses them only under the privacy law of the people named. Regulation (EU) 2016/679 applies from 2018-05-25 under Art. 99(2), and its legal basis rules are set out under GDPR and AI training data.
Cal. Civ. Code 1798.120 gives California consumers the right to opt out of the sale or sharing of their personal information, and it binds a business that meets the CCPA thresholds.
The rules that reach meter data specifically, state utility commission rules and the data-access provisions of Directive 2019/944, are not stated here.
De-identification is a separate step with its own test, and no claim is made that aggregation removes these rules. A company checks bulk personal data rules itself, starting from the opt-out in California CCPA/CPRA and AI training data.
Field Crews and Employee Records
Inspection photos, work orders and vehicle logs name or show crew members, so employee data rules apply next to the company's rights.
Benefits, Risks, Downsides and Alternatives for an Energy or Utility Company
Licensing can earn income from inspection and maintenance archives a company keeps anyway, but infrastructure, customer-privacy and contract limits shrink what can go, and not licensing is a valid outcome.
Benefits
- Buyers' own pages name field inspection and maintenance records for energy (HUMXN and Mercor, read 2026-11-17).
- A company's own work orders that hold no customer data do not raise the customer privacy rules stated on this page.
Risks
- CEII-type engineering, vulnerability or design details leaving the company with a file.
- Customer privacy claims under GDPR and CCPA for records that name households.
- Export of controlled technical data to a foreign person under 15 CFR 734.13.
Downsides
- Scoping and screening work before any sample can be described.
- Mercor lists data restricted by customer contracts as not a fit, which removes any set bound by such terms.
- Mercor's listing states its referral base and size band as its own claims, not outcomes.
Alternatives
- License only maintenance records stripped of design details.
- Keep the archive for in-house models.
- Not licensing at all, set out under alternatives to selling data, including not selling at all.
Where Energy Licensing Meets the Seller Path, the Law and Other Industries
Energy companies share plant and maintenance records with manufacturers, project records with construction and engineering firms, and each industry page sets out its own limits.
Energy is one sector in data licensing by industry, next to manufacturers licensing industrial data, engineering and architecture firms licensing data and construction companies licensing data, with telecom operators licensing data to follow.
Inspection reports and work orders follow the rules for selling documents for AI training, while meter and grid streams are sensor, IoT and telemetry data for AI training.
The full map is AI training data law by jurisdiction, and crew and customer records fall under employee data and AI training and privacy law and AI training data.
- Check data sale readiness.
- Review customer consent and confidentiality clauses.
- Remove customer data through de-identification before licensing data.
- Start choosing a buyer for your data.
- Negotiate the clauses of AI data licensing agreements.
This page is information, not legal advice.
Buyer, Marketplace and Law Pages Named on This Page
Each buyer and marketplace above has its own page with dates and sources.
- Handshake AI data buyer profile
- HUMXN data marketplace profile
- Mercor data buyer profile
- micro1 data buyer profile
Frequently Asked Questions
Can a utility license smart-meter data to AI companies?
Only under the privacy and utility rules that apply to the customers named. This page states GDPR and CCPA and leaves state utility commission rules open.
How much do AI companies pay energy companies for data?
No buyer page checked publishes an energy-specific price. Mercor's manufacturing listing, which names utilities and energy operators, states a deal range of USD 100,000 to USD 1,500,000, its own claim read 2026-11-17.
See what company data is worth to AI companies.
Can a grid operator license engineering and design data?
Not if the records are CEII or controlled technical data. 18 CFR 388.113(c)(2) describes the protected engineering, vulnerability and design information, and 15 CFR 734.13 covers release to foreign persons.