Form U-57 Files Dataset

The Form U-57 Files Dataset is a closed historical corpus of every EDGAR submission of Form U-57 ("Notification of Foreign Utility Company Status") and its amendment counterpart Form U-57/A, filed under Section 33(a) of the Public Utility Holding Company Act of 1935 ("PUHCA 1935") and Rule 57 promulgated thereunder. Each record is a single accession-numbered submission containing a metadata.json index plus the original EDGAR documents (the form body and any non-image exhibits) wrapped in their SGML envelopes. The filings were made by registered public-utility holding companies, their associate or subsidiary companies, and the foreign utility companies ("FUCOs") whose Section 33 eligibility was being asserted. The dataset spans the entire EDGAR-era life of the form, from September 1994 through the form's discontinuation on February 8, 2006, when the Energy Policy Act of 2005 repealed PUHCA 1935 and migrated holding-company oversight to FERC. Because Section 33 and Rule 57 ceased to operate at that point, the corpus is fixed at 940 U-57 and U-57/A accessions and will not receive new records.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures the complete EDGAR universe of Section 33 FUCO notifications. Form U-57 was a short, item-numbered, prose-driven notification — neither a registration statement, an offering document, nor a periodic report — used to put the SEC on notice that a particular non-U.S. entity claimed status as a "foreign utility company" within the meaning of Section 33 of PUHCA 1935. Section 33 was added to PUHCA 1935 by Section 711 of the Energy Policy Act of 1992 and provided that a FUCO would not be treated as a "public-utility company," a "subsidiary company," or an "affiliate" of a registered holding company for most purposes of the Act, subject to the statutory definition: the entity had to derive no part of its income, directly or indirectly, from the generation, transmission, or distribution of electric energy for sale, or the distribution at retail of natural or manufactured gas, within the United States, and its facilities had to be located outside the United States. Form U-57/A served the same purpose as an amendment to a previously filed U-57 — for example, to correct prior disclosures, update ownership, expand the description of facilities, or reflect changes in associate-company sponsorship. Both form types share an identical structural template; the /A variant restates or supplements selected items.

The dataset covers every U-57 and U-57/A submission EDGAR accepted from September 1994 through February 2006. Records are organized into monthly ZIP containers keyed YYYY/YYYY-MM.zip, and each accession folder is keyed by the 18-digit unhyphenated EDGAR accession number (for example 000111667904001874) under a YYYY-MM/ root reflecting the EDGAR acceptance month. File types in the corpus are TXT, JSON, HTML, and PDF. Image attachments (typically GIF or JPG figures of plant photographs, schematic diagrams, or organizational charts) are excluded; everything else from the original EDGAR submission is preserved.

Content Structure of a Single Record

One record in the Form U-57 Files Dataset is a single EDGAR submission of Form U-57 or Form U-57/A. Each accession corresponds to exactly one notification event filed with the SEC under Section 33(a) of PUHCA 1935 and Rule 57 thereunder. A record contains two structural layers:

1. A submission-level metadata layer encoded as metadata.json, derived from the EDGAR header of the original SGML submission and from sec-api.io's filing index. This layer carries identifiers, timestamps, party data, file inventory pointers, and statutory tagging.
2. A document layer composed of the raw EDGAR document files that accompanied the accession, each wrapped in the standard SGML <DOCUMENT> envelope used by EDGAR. The principal document is the form itself, conventionally named u57.txt (or u57a.txt for amendments), and it is supplemented in some accessions by exhibits, cover letters, or organizational charts.

The two layers are complementary: metadata.json carries what is structured and parseable about the filing as a whole, while the document files carry the substantive Section 33 narrative that the filer drafted in prose.

metadata.json fields

The metadata file is keyed at the EDGAR-submission level and includes the following fields:

• formType — either U-57 or U-57/A.
• accessionNo — the dashed EDGAR accession number (e.g. 0001116679-04-001874).
• description — the EDGAR-supplied human-readable form label, typically "Form U-57 - Notification of Foreign Utility Company Status [Section 33(a)(2)]" or its amendment counterpart.
• filedAt — ISO 8601 timestamp with timezone offset, recording the moment EDGAR accepted the submission.
• linkToFilingDetails — URL to the primary form document on sec.gov.
• linkToTxt — URL to the full SGML submission text file on sec.gov.
• linkToHtml — URL to the EDGAR filing index page (*-index.htm).
• linkToXbrl — URL to an XBRL instance when present; effectively always empty for U-57 because the form was never within scope of any XBRL tagging mandate.
• documentFormatFiles[] — one entry per document in the submission, with sequence, size (bytes, as a string), documentUrl, type (typically U-57 for the form, or an exhibit-type label for ancillary documents), and an optional description. The list also includes the umbrella SGML submission .txt that EDGAR generates to bundle every document.
• dataFiles[] — structured-data attachments such as XBRL instance, schema, label, and presentation files. Empty for U-57 filings, since the form was never subject to a structured-data filing requirement.
• entities[] — one object per party on the filing. Each entity carries companyName (often suffixed with a role tag such as (Filer)), cik (10-digit zero-padded), type (mirroring formType), fileNo (SEC file number, drawn from the 073-XXXXXX series reserved for FUCO notifications under PUHCA), filmNo (EDGAR film number), fiscalYearEnd (MMDD), stateOfIncorporation (SEC state/country code; foreign-jurisdiction codes such as O5 for Mexico or M6 for Cayman Islands are typical), irsNo (often 000000000 for foreign filers without a U.S. EIN), and act (35, denoting PUHCA 1935 as the statutory authority).
• id — a 32-character hexadecimal identifier assigned by sec-api.io to the metadata record itself.

The substantive narrative of the form — the description of the foreign facilities, the eligibility statement under Section 33, and the identification of the registered holding company sponsor — lives entirely inside the document body, not in metadata.json.

Document layer and the SGML envelope

Each document inside an accession folder is presented exactly as EDGAR received it, including the SGML <DOCUMENT> envelope. The envelope exposes a small set of header tags before the payload begins:

• <TYPE> — the document classification, e.g. U-57 for the form itself or an exhibit-type label such as EX-99 for supporting exhibits.
• <SEQUENCE> — the document's ordinal position within the submission.
• <FILENAME> — the original on-disk filename (e.g. u57.txt).
• <DESCRIPTION> — an optional free-text label.
• <TEXT> ... </TEXT> — the document payload, which may be plain ASCII, HTML, or a uuencoded/base64 binary block depending on file type.

For PDF or other binary payloads, the bytes are encoded inside the <TEXT> block between <PDF> and </PDF> markers. For HTML payloads, the body is the raw HTML markup. <PAGE> form-feed markers commonly delimit paginated sections within plain-text U-57 documents.

Item-by-item content of the form body

Inside the <TEXT> block, a Form U-57 follows a compact, prescribed item layout drawn from the form's instructions under Rule 57. While individual filings vary in formatting and verbosity, the canonical content elements are:

1. Caption block — centered headers identifying the Securities and Exchange Commission, "FORM U-57," the title "NOTIFICATION OF FOREIGN UTILITY COMPANY STATUS," and a citation to "Section 33(a) of the Public Utility Holding Company Act of 1935, as amended." Filings made on behalf of an associate company of a registered holding company additionally cite Section 33(a)(2).
2. Identification of the foreign utility company — the legal name and principal business address of the FUCO. Where the FUCO is organized under non-U.S. law (typically the case), the legal-entity suffix reflects the home jurisdiction (e.g. S. de R.L. de C.V. for a Mexican limited liability company, Ltd. for a Cayman or U.K. entity, S.A. for a Latin American sociedad anonima).
3. Item I — Description of the FUCO and its facilities — a narrative description of operations: type of facility (generation, transmission, or distribution), capacity (e.g. nameplate megawatts), fuel or technology (gas-fired combined cycle, hydroelectric, transmission line voltage class), location, and customers or counterparties served. For project-financed ventures, this item often discloses joint-venture partners and ownership percentages.
4. Item II — Statutory eligibility under Section 33 — an affirmative statement that the entity (a) is engaged, directly or indirectly, in the ownership or operation of facilities used for the generation, transmission, or distribution of electric energy for sale, or the distribution at retail of natural or manufactured gas for heat, light, or power; (b) operates those facilities exclusively outside the United States; and (c) does not derive any part of its income, directly or indirectly, from the generation, transmission, or distribution of electric energy for sale, or the distribution at retail of natural or manufactured gas, within the United States.
5. Identification of the registered holding company or associate company — where the notification is made under Section 33(a)(2), the form names the registered holding company parent and explains the chain of association.
6. Signature block — executed by an officer of the filer with name, title, and date. For amendments (U-57/A), the signature attests to the amended content.

Because the form is short and item-driven, a typical U-57 document is on the order of one to a few kilobytes of plain text; longer filings reflect more elaborate facility descriptions, multi-asset portfolios, or attached exhibits.

Included content

A record includes:

• The metadata.json index for the submission.
• The original EDGAR primary form document (u57.txt or u57a.txt) wrapped in its SGML <DOCUMENT> envelope.
• Any non-image exhibit documents from the EDGAR submission, in their original formats (plain text, HTML, or PDF), each wrapped in its own SGML envelope.

Excluded or separate content

Image files attached to the original EDGAR submission (typically GIF or JPG figures of plant photographs, schematic diagrams, or organizational charts) are excluded from the dataset packaging. The umbrella SGML submission wrapper file (the <accession>.txt aggregate that EDGAR generates to bundle every document into one file) is referenced by URL inside documentFormatFiles[] but is not always materialized as a standalone file inside the accession folder; the individual document files it wraps are present instead. Any correspondence, no-action letters, or staff comments associated with the filing live outside the U-57 accession itself and are not part of the record.

Changes in required content over time

The substantive disclosure requirements of Form U-57 were stable throughout the dataset's coverage period. Section 33 was added to PUHCA 1935 by the Energy Policy Act of 1992, and Rule 57's notification procedure was operative across the entire 1994-2006 EDGAR span. The form's item structure — identification of the FUCO, description of its operations and facilities, identification of any sponsoring registered holding company, and the Section 33 eligibility statement — did not undergo material redrafting.

The most consequential historical change is terminal rather than intra-period: the Energy Policy Act of 2005 repealed PUHCA 1935 in its entirety, effective February 8, 2006. From that date forward, Section 33 and Rule 57 ceased to exist as legal instruments, and no further Form U-57 or U-57/A submissions were filed with the SEC. The FUCO concept was carried forward in modified form under the Public Utility Holding Company Act of 2005 administered by FERC, but that successor regime is outside the EDGAR/Form U-57 universe. The dataset is therefore a closed corpus.

A secondary observation is that the relative mix of U-57 and U-57/A filings shifts modestly across the period, as initial notifications from the mid-1990s aged into amendments in the late 1990s and early 2000s; this is a population effect rather than a change in form structure.

Changes in data format over time

Form U-57 was an EDGAR form type from the inception of mandatory EDGAR filing for PUHCA matters in the mid-1990s. Across the 1994-2006 lifespan, the dominant document format inside the SGML envelope is plain ASCII text (.txt), reflecting both the simplicity of the form and the early-EDGAR convention of plain-text filings. The file types found in the dataset are TXT, JSON, HTML, and PDF; beyond the ubiquitous .txt form bodies and metadata.json indexes, two narrower variants appear:

• HTML (.htm/.html) payloads, which appear sporadically as filers adopted the HTML filing option that EDGAR opened to most form types from 1999-2000 onward. Even in later years, HTML usage for U-57 remained the exception because the form's content is short and well suited to plain text.
• PDF payloads, which appear in a small number of accessions, typically for exhibits (such as a scanned signed cover letter or a project diagram) rather than for the primary form document. PDF documents are carried inside the SGML <TEXT> block as an encoded byte stream wrapped in <PDF>...</PDF> markers.

Interpretation notes

• Amendments do not supersede originals in the dataset. A U-57/A is stored as its own accession folder; readers reconstructing the full disclosure history of a particular FUCO must group records by entity (CIK or by file number from the 073-XXXXXX series) and order them by filedAt.
• Substantive disclosure lives in the document body, not the metadata. Facility capacity, fuel type, geographic location, ownership percentages, and the textual Section 33 eligibility statement are not extracted into structured metadata.json fields. Any analytic use of those attributes requires parsing the prose of u57.txt (or u57a.txt).
• Foreign-jurisdiction signals appear at the entity level. The stateOfIncorporation SEC code on the entity object is the most reliable structured indicator of where the FUCO is organized; codes from the SEC's foreign-jurisdiction set (e.g. O5 Mexico, M6 Cayman Islands) reliably identify the FUCO. A U.S. registered holding company sponsor, when present as a separate entity object, will carry a U.S. state code instead.
• File numbers are diagnostic. SEC file numbers in the 073-XXXXXX series are reserved for FUCO notifications under PUHCA; their presence on the entity object confirms the U-57 statutory context and provides a stable per-FUCO key across multiple amendments.
• The SGML envelope is part of the data. Consumers who want only the form text should strip the <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, and <TEXT> tags before further processing; consumers reproducing the EDGAR submission faithfully should preserve them. <PAGE> form-feed markers inside the body indicate paginated breaks in the original print-formatted text.
• Closed-corpus behavior. Because PUHCA 1935 was repealed effective February 8, 2006, the dataset will not receive new accessions; periodic updates reflect re-packaging of the existing records rather than incremental additions.

Who Files or Publishes This Dataset, and When

Who files or discloses the record

The Section 33(a) notification claimed FUCO status for a non-U.S. entity that, exclusively outside the United States, owned or operated facilities for the generation, transmission, or distribution of electric energy for sale, or for the retail distribution of natural or manufactured gas, and derived no U.S. income from those activities. The filing population was narrow:

• Registered public-utility holding companies and their associate or subsidiary companies. In practice these were the EDGAR registrants on most U-57 filings. The regulatory benefit of FUCO status (the ability to invest in foreign utility operations free of certain PUHCA constraints) flowed to the U.S. holding company group, so the holding-company side of the chain typically made the filing on behalf of, or jointly with, the foreign entity.
• The foreign utility company itself, identified as the entity whose Section 33(a) eligibility is being asserted.

Outside the population: domestic public-utility companies under Section 2(a)(5), Section 3 exempt holding companies, exempt wholesale generators ("EWGs") under Section 32, and any foreign affiliate engaged in non-utility activities (fuel supply, services, non-utility energy) that did not satisfy the Section 33(a) activity, geographic, and income tests.

When the record is created or required

The trigger was status-based and acquisition-linked, not periodic. A Form U-57 was filed in connection with, or shortly after, the acquisition, formation, or investment in a foreign entity for which FUCO status was being claimed, placing the SEC on notice of the entity's existence, ownership chain, and qualifying foreign operations. There was no fixed business-day deadline analogous to Form 8-K; timing tracked the act of claiming the exempt status.

There was no annual or quarterly U-57 obligation. Form U-57/A was used to amend a prior U-57, typically to update ownership, correct the description of foreign operations, or restate the eligibility analysis. A single underlying FUCO notification can have multiple U-57/A filings attached over time. Continuing oversight of the holding company's foreign utility activities ran through the broader PUHCA registered-system reporting regime, not through repeated U-57 filings.

Administratively, U-57 was processed within the SEC's Division of Investment Management, Office of Public Utility Regulation.

Closed, archival nature of the dataset

The dataset is bounded by external regulatory events, not by ongoing filing activity:

• Front edge (September 1994). Section 33 was added to PUHCA 1935 by the Energy Policy Act of 1992; EDGAR began accepting U-57 filings electronically in 1994, so the earliest record in this dataset is from September 1994. Any pre-EDGAR Section 33 notifications between 1992 and 1994 exist only on paper and are not represented here.
• Back edge (February 8, 2006). The Energy Policy Act of 2005 ("EPAct 2005") repealed PUHCA 1935 effective February 8, 2006. PUHCA 1935 was replaced by the Public Utility Holding Company Act of 2005 ("PUHCA 2005"), and holding company oversight, including FUCO-related matters, was transferred to the Federal Energy Regulatory Commission ("FERC"). The SEC's PUHCA program, and Form U-57 with it, was discontinued.

The result is a closed, archival series of 940 Form U-57 and U-57/A filings spanning September 1994 through February 2006. No new records will be added.

Important distinctions

• Filer vs. subject. The U.S. registered holding company or associate is typically the EDGAR registrant; the FUCO is the entity whose Section 33(a) eligibility is asserted. The two should not be conflated when reading the dataset.
• FUCO vs. EWG. Section 32 EWG status (domestic or foreign wholesale generators) used a different process involving FERC determinations and is not in this dataset. Section 33 FUCO status, claimed via Form U-57, was the parallel mechanism for non-U.S. retail and integrated utility operations.
• Section 3 exempt holding companies. Used their own regime (notably Form U-3A-2) and did not file Form U-57 in their own right. U-57 is tied to the registered system's foreign-investment activities.
• Domestic public-utility companies. Section 2(a)(5) operating utilities serving U.S. customers were regulated through state PUCs and, where applicable, the registered holding-company system; they did not file Form U-57.
• Post-2006 successor disclosure. After February 8, 2006, FUCO-related disclosure does not continue on EDGAR in U-57 form. Researchers tracking foreign-utility investments after that date must look to FERC filings under PUHCA 2005 and to the holding-company group's Exchange Act periodic reports.

How This Dataset Differs From Similar Datasets or Filings

Form U-57 occupies a narrow, now-closed corner of EDGAR. The most useful comparisons are the other PUHCA "U-" forms, the parallel Section 32 EWG regime administered by FERC, and the post-2006 FERC successor regime. General Exchange Act filings are not substitutes and are mentioned only to rule them out.

Form U-3A-2 — Annual exemption statement (Section 3(a))

The closest cousin in spirit. U-3A-2 is the recurring annual statement by which a domestic holding company claims exemption under Sections 3(a)(1)-(5) (e.g., intrastate or predominantly-utility systems). U-57 is the one-time entity-level notification that a foreign utility qualifies for exemption under Section 33. Same underlying logic (assert exemption, avoid full registration), opposite jurisdictional side, opposite cadence.

Form U-3A3-1 — Section 3(a)(3) exemption mechanics

Domestic-side exemption filing tied to Section 3(a)(3). Like U-3A-2, it concerns U.S. holding-company structures, not foreign utilities, and is filed by the parent rather than for a single foreign subsidiary.

Form U-1 — Application or declaration under PUHCA

The general transactional vehicle by which a registered holding company sought affirmative SEC authorization for securities issuances, acquisitions, intra-system financings, or service arrangements. Form U-1 produces SEC orders; U-57 produces no order. U-1 is transactional and bilateral; U-57 is a unilateral status notice.

Forms U-5A / U-5B — Holding-company registration statements

The filings that make a parent a "registered" holding company under PUHCA. They define the system perimeter against which U-1, U-5S, U-13-1, and U-57 then operate. Complementary to U-57, not overlapping: U-5A/U-5B identify the parent system; U-57 carves a specific foreign subsidiary out of full PUHCA reach.

Form U-5S — Annual report of registered holding companies

The system-wide annual report of a registered holding-company group (analogous in role to a 10-K but PUHCA-specific). Periodic, consolidated, tabular. A FUCO disclosed via U-57 will typically also surface in the parent's U-5S subsidiary roster, but U-5S is the recurring system snapshot whereas U-57 is the threshold single-entity status filing.

Form U-13-1 — Mutual or subsidiary service company application

Approval filing for an intra-system service company providing services at cost. Subject matter (service-company economics) is unrelated to foreign utility status; only the regulatory umbrella is shared.

Form U-13E-1 — Annual service-company report

Recurring report by service companies authorized under U-13-1. Periodic, internal-services oriented; no substantive overlap with U-57 beyond the PUHCA family.

Form U-9C-3 — Quarterly energy/gas-related activities report

Rule 58 / Section 9(c)(3) report covering non-utility energy-adjacent activities of registered systems. Periodic activity report, parent-level, often international in scope but not the FUCO status notice itself.

Form U-6B-2 — Statement of securities issued

Transactional certificate describing securities issued by a registered holding company or subsidiary under PUHCA authority. Securities-issuance content, not status content.

Form U-7D — Lease of utility assets

Transactional filing covering certain lease arrangements involving utility assets. Domestic-asset focus, no foreign-utility content.

Section 32 EWG certifications (FERC, not EDGAR)

The Exempt Wholesale Generator regime under PUHCA Section 32 (Energy Policy Act of 1992) is the sibling of Section 33: EWGs are domestic wholesale generators exempt from PUHCA, FUCOs are foreign utilities exempt from PUHCA. The critical operational difference is venue: EWG self-certifications were filed with FERC (FERC Form 65 / EWG application series), not the SEC, and are not present in EDGAR. Researchers who want the full PUHCA exempt-entity universe must combine U-57 (EDGAR, foreign side) with FERC's EWG dockets (domestic side).

Post-2006 PUHCA 2005 / FERC successor filings

PUHCA 1935 was repealed effective February 8, 2006, and replaced by PUHCA 2005, administered by FERC. The FUCO concept survived but the notification mechanism moved out of SEC jurisdiction (FERC Form 65-A and FERC Form 65-B company-status notifications cover the analogous post-repeal ground). These FERC filings are the substantive successors to U-57 content but are not in EDGAR and are not part of any SEC dataset.

10-K, 10-Q, and Exhibit 21 of registered holding companies

Parent periodic reports describe FUCOs narratively in business and risk sections, segment data, or MD&A; Exhibit 21 lists them by name and jurisdiction. These are aggregated, parent-level views under Exchange Act standards. They lack the entity-level address, operations description, and Section 33 eligibility statement that define a U-57.

Key differences

• Trigger. U-57 is filed once per FUCO when status is first established (plus U-57/A amendments on material change). U-3A-2, U-5S, U-13E-1, U-9C-3 are recurring; U-1, U-13-1, U-6B-2, U-7D are transactional.
• Filer and subject. U-57 covers a single foreign utility entity and is filed by or on behalf of that entity. U-1, U-5A/B, U-5S, U-3A-2/3A3-1, U-9C-3 are parent- or system-level. U-13-1/13E-1 cover intra-system service companies.
• Regulatory section. U-57 implements Section 33 (foreign). U-3A-2/3A3-1 implement Section 3(a) (domestic exemption). EWG certifications implement Section 32 at FERC (domestic wholesale generation).
• Venue. U-57 lives in EDGAR. EWG certifications and all post-February 2006 FUCO-equivalent filings live in FERC dockets.
• Output. U-57 is a notification with no Commission order. U-1 produces SEC orders; U-13-1 produces approvals.

Boundary summary

The Form U-57 Files Dataset is the only EDGAR corpus containing the Section 33 threshold eligibility filing for foreign utility companies, with entity-level name, address, operations description, and eligibility statement. Other PUHCA "U-" datasets (U-1, U-5A/B, U-5S, U-3A-2, U-3A3-1, U-13-1, U-13E-1, U-9C-3, U-6B-2, U-7D) are complements when reconstructing a registered holding company system but never substitutes for the FUCO notification. Section 32 EWG certifications and post-2006 PUHCA 2005 filings cover analogous regulatory ground but reside in FERC's docket system, outside EDGAR.

Who Uses This Dataset

Users of the Form U-57 Files Dataset key on specific record components: entity CIK, sponsor holding company, country and stateOfIncorporation, facility description, the Section 33 eligibility statement, and U-57/A amendment dates.

Energy M&A and regulatory counsel

Transaction lawyers working on legacy international power assets use the sponsor holding company field, facility description, and Section 33 eligibility statement to establish whether an asset was historically held under a FUCO exemption rather than as a U.S. public utility subsidiary. This supports drafting representations, regulatory pedigree schedules, and FERC inquiry responses for assets still on current balance sheets.

In-house compliance at successor holding companies

Compliance staff at firms that absorbed former PUHCA registrants through merger or reorganization join entity CIK and sponsor identification against internal asset registries and contemporaneous U-1, U-5S, and U-13 filings. U-57/A amendment dates flag ownership transfers and restructurings up to the 2006 repeal, supporting current FERC, state PUC, and tax positions.

Forensic accountants and litigation support

Used to reconstruct ownership chains in disputes over legacy power plants, joint ventures, and project finance vehicles. The U-57/A amendment trail often signals sponsor changes or operating-entity restructurings; cross-referenced with Form 10-K, Form 10-Q, and 8-K disclosures to build exhibit-ready timelines for arbitration and breach-of-warranty claims.

Energy and business historians

Researchers studying 1990s cross-border utility investment treat the archive as a structured census of FUCO activity. Operations descriptions and Section 33 statements classify each entity as generation, transmission, or distribution; filing and amendment dates align with privatization waves in Latin America, the U.K., continental Europe, and parts of Asia.

Energy-economics and infrastructure researchers

Analysts at infrastructure research desks and academic energy economists extract country, stateOfIncorporation, facility description, and sponsor holding company to build longitudinal datasets of where U.S. holding-company capital flowed and how it correlates with host-country reform programs.

Federal energy policy researchers

Policy staff studying the PUHCA 1935-to-2005 transition aggregate filings by year, sponsor, and host country to size the regulatory population that moved to FERC books-and-records jurisdiction in 2006. Section 33 eligibility statements are read for recurring legal arguments used to claim FUCO status.

Entity-resolution data engineers

Teams building cross-regulator entity graphs use entity CIK, sponsor CIK, address, country, and stateOfIncorporation to link U-57 entities to parent U-1 applications, FERC Form 1 and EQR records, and host-country utility registries. U-57/A filings act as edge updates for ownership and name changes across the 1994 to 2006 window.

Diligence teams on secondary infrastructure transactions

Buy-side diligence on legacy international power assets repackaged into infrastructure funds uses operations description, sponsor identification, and amendment history to confirm an asset's original regulatory classification matches seller representations and current-owner disclosures.

NLP and retrieval engineers

The closed, bounded corpus (TXT, HTML, PDF, with structured metadata for accession, CIK, and form type) is convenient for benchmarking extraction of Section 33 eligibility language, sponsor names, and country fields without the drift of an actively updated form type. The form's text density also supports comparative work versus inline XBRL corpora when contrasting prose filings against structured-data filings.

Specific Use Cases

The use cases below tie directly to specific record fields and document items in the closed historical census of U-57 and U-57/A accessions.

Reconstructing FUCO ownership timelines for legacy international power assets

Group accessions by FUCO entity CIK (or by the SEC 073-XXXXXX file number) and order by filedAt to chain the original U-57 with each subsequent U-57/A. The amendment sequence exposes sponsor changes, expansions of facility descriptions, and restated Section 33 eligibility statements. Output is an entity-level disclosure history used by transactional counsel and forensic accountants to support representations, breach-of-warranty exhibits, and FERC inquiry responses for assets still on balance sheets.

Building a country-by-country map of US holding company foreign utility investment

Pivot the corpus on the foreign-jurisdiction stateOfIncorporation codes on FUCO entity objects (e.g. O5 Mexico, M6 Cayman Islands) joined to the sponsor registered holding company entity, with filedAt as the time axis. The result is a longitudinal panel of where U.S.-sponsored capital was deployed, used by energy economists and infrastructure research desks to align FUCO formation dates with privatization waves in Latin America, the U.K., continental Europe, and parts of Asia.

Linking FUCOs to their PUHCA registered holding company parents

Use the registered holding company named in the form body (the Section 33(a)(2) sponsor) and any sponsor entity CIK on the filing to attach each FUCO to its parent system. Cross-reference against U-5A/U-5B registration statements, U-1 applications, and U-5S annual subsidiary rosters to complete a registered holding company's foreign asset roster as of a chosen reference date. Used by compliance teams at successor registrants and entity-resolution engineers building cross-regulator graphs.

Sizing the regulated population that migrated to FERC in February 2006

Aggregate filings by sponsor, host country, and facility type extracted from the Item I narrative (generation, transmission, or distribution; nameplate megawatts; fuel or technology) to estimate the FUCO universe carried into PUHCA 2005 jurisdiction. The closed terminus on 2006-02-08 makes the dataset a complete denominator for federal energy policy researchers studying the SEC-to-FERC handoff.

Benchmarking extraction of Section 33 eligibility language and facility attributes

Use the prose Item II eligibility statement and Item I facility description as a stable, bounded NLP corpus for training and evaluating extractors that recover sponsor name, facility type, capacity, fuel, jurisdiction, and the three statutory eligibility prongs (foreign location, no U.S.-derived income, qualifying utility activity). The closed-corpus property and the small set of file types (TXT, HTML, PDF inside the SGML envelope) eliminate filing-population drift across runs.

Diligence on secondary sales of legacy international power assets

For an asset offered into an infrastructure fund or strategic buyer, locate the original U-57 by FUCO name or sponsor CIK, then walk the U-57/A trail to verify that joint-venture partners, ownership percentages, and facility descriptions disclosed by the seller match what was on file with the SEC at exemption inception and through the last amendment before the 2006 repeal. Output is a regulatory-pedigree memo or schedule supporting the purchase agreement.

Dataset Access

The Form U-57 Files Dataset is accessible through three endpoints: a public JSON index for metadata, a full archive download, and per-container downloads for incremental access.

Dataset Index JSON API: https://api.sec-api.io/datasets/form-u57-files.json

This endpoint returns dataset-level metadata (name, description, earliest sample date, last updated timestamp, total records, total size, form types covered, container format, and file types) along with the full list of container files. Each container entry includes its key, size, record count, last updated timestamp, and a direct download URL. The index is the recommended way to monitor refresh cycles: poll it daily and compare each container's updatedAt value against your local copy to determine which monthly archives have changed and need to be re-downloaded.

This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-69a7-b690-337740d15d64",
        

          3
            "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-u57-files.zip",
        

          4
            "name": "Form U-57 Files Dataset",
        

          5
            "updatedAt": "2026-04-15T12:06:50.450Z",
        

          6
            "earliestSampleDate": "1994-09-01",
        

          7
            "totalRecords": 940,
        

          8
            "totalSize": 3173218,
        

          9
            "formTypes": ["U-57", "U-57/A"],
        

          10
            "containerFormat": "ZIP",
        

          11
            "fileTypes": ["TXT", "JSON", "HTML", "PDF"],
        

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-u57-files/2026/2026-03.zip",
        

          15
                "key": "2026/2026-03.zip",
        

          16
                "size": 13818783,
        

          17
                "records": 154,
        

          18
                "updatedAt": "2026-04-15T12:06:50.450Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Download Entire Dataset: https://api.sec-api.io/datasets/form-u57-files.zip?token=YOUR_API_KEY

Returns the complete dataset as a single ZIP archive covering all U-57 and U-57/A filings since September 1994. This endpoint requires an API key passed as the token query parameter.

Download Single Container: https://api.sec-api.io/datasets/form-u57-files/2026/2026-03.zip?token=YOUR_API_KEY

Each container holds one calendar month of filings, organized as YYYY/YYYY-MM.zip. Use this endpoint to fetch only the months you need or to refresh just the containers flagged as updated by the index API. This endpoint requires an API key.

Authentication: All download endpoints accept the API key as a token query parameter. Your API key is available in your sec-api.io dashboard. The JSON index endpoint is public and does not require authentication.

Examples

Fetch the index with curl:

          1
          curl https://api.sec-api.io/datasets/form-u57-files.json
        

Download the full archive with wget:

          1
          wget "https://api.sec-api.io/datasets/form-u57-files.zip?token=YOUR_API_KEY"
        

Iterate the containers array and download each monthly archive in Node.js:

          1
          const fs = require("fs");
        

          2
          const https = require("https");
        

          3
          
        

          4
          const API_KEY = "YOUR_API_KEY";
        

          5
          const INDEX_URL = "https://api.sec-api.io/datasets/form-u57-files.json";
        

          6
          
        

          7
          const get = (url) =>
        

          8
            new Promise((resolve, reject) => {
        

          9
              https.get(url, (res) => {
        

          10
                let body = "";
        

          11
                res.on("data", (chunk) => (body += chunk));
        

          12
                res.on("end", () => resolve(body));
        

          13
                res.on("error", reject);
        

          14
              });
        

          15
            });
        

          16
          
        

          17
          (async () => {
        

          18
            const index = JSON.parse(await get(INDEX_URL));
        

          19
            for (const c of index.containers) {
        

          20
              const url = `${c.downloadUrl}?token=${API_KEY}`;
        

          21
              const file = fs.createWriteStream(c.key.replace("/", "-"));
        

          22
              https.get(url, (res) => res.pipe(file));
        

          23
              console.log(`Downloading ${c.key} (${c.records} records)`);
        

          24
            }
        

          25
          })();
        

The same pattern works in any language: read the index, filter containers by updatedAt against your last sync timestamp, then download only the changed archives.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form U-57 ("Notification of Foreign Utility Company Status") and its amendment counterpart Form U-57/A, the SEC notification filings made under Section 33(a) of the Public Utility Holding Company Act of 1935 and Rule 57 promulgated thereunder. Both form types share an identical structural template; the /A variant restates or supplements selected items of a previously filed U-57.

What does one record in the Form U-57 Files Dataset represent?

One record is a single EDGAR submission of Form U-57 or U-57/A, materialized as one accession-numbered folder containing a metadata.json index plus the original EDGAR documents (the form body and any non-image exhibits) wrapped in their SGML <DOCUMENT> envelopes. Each accession corresponds to exactly one notification event placing the SEC on notice of a non-U.S. entity's claimed FUCO status.

Who was required to file Form U-57?

Filings were made by registered public-utility holding companies and their associate or subsidiary companies (typically the EDGAR registrant making the filing on behalf of, or jointly with, the foreign entity) and by the foreign utility company itself, identified as the entity whose Section 33(a) eligibility was being asserted. Domestic public-utility companies, Section 3 exempt holding companies, and Section 32 EWGs did not file Form U-57.

When was Form U-57 filed?

The trigger was status-based and acquisition-linked, not periodic: a Form U-57 was filed in connection with, or shortly after, the acquisition, formation, or investment in a foreign entity for which FUCO status was being claimed. There was no annual or quarterly U-57 obligation; Form U-57/A amendments were filed when prior disclosures needed correction or when ownership, facilities, or sponsorship changed.

What time period does the dataset cover?

The dataset spans the entire EDGAR-era life of the form, from September 1994 through February 8, 2006. The Energy Policy Act of 2005 repealed PUHCA 1935 effective February 8, 2006, transferring holding-company oversight to FERC under PUHCA 2005 and discontinuing Form U-57. The corpus is therefore closed and will not receive new accessions.

What file formats appear in the dataset?

Records contain TXT, JSON, HTML, and PDF files. The metadata.json is JSON; the principal form body is plain ASCII text (u57.txt or u57a.txt) wrapped in an SGML <DOCUMENT> envelope; HTML payloads appear sporadically from 1999-2000 onward; PDF payloads appear in a small number of accessions, usually for exhibits, with bytes encoded inside the <TEXT> block between <PDF> and </PDF> markers. Image attachments (GIF, JPG) from the original EDGAR submissions are excluded.

How does the Form U-57 Files Dataset differ from Section 32 EWG filings?

Section 32 Exempt Wholesale Generator certifications are the sibling regime to Section 33 FUCO notifications: EWGs are domestic wholesale generators exempt from PUHCA, FUCOs are foreign utilities exempt from PUHCA. The decisive operational difference is venue. EWG self-certifications were filed with FERC (FERC Form 65 / EWG application series), not the SEC, and are not present in EDGAR or in this dataset. To assemble the complete PUHCA exempt-entity universe, the Form U-57 corpus must be combined with FERC's EWG dockets.