The Form 486B24E Files Dataset is a closed historical collection of EDGAR submissions filed on Form 486B24E, a hybrid post-effective amendment that closed-end interval funds used to amend a registration statement on an immediately effective basis under Rule 486(b) of the Securities Act of 1933 while simultaneously registering additional shares under former Rule 24e-2 of the Investment Company Act of 1940. Each record is a single accession identified by its EDGAR accession number and packages the post-effective amendment, the underlying prospectus and statement of additional information, the Rule 24e-2 fee calculation, and the accompanying exhibits, together with a metadata.json descriptor of the submission. The legal filer is always the registrant interval fund itself. Coverage spans the brief regulatory window from March 1, 1996 — when the Rule 486(b) framework for closed-end interval funds and the corresponding EDGAR form code were introduced — through October 1997, when the SEC rescinded Rule 24e-2 and split the form's two functions into Form 486BPOS amendments and separate Form 24F-2NT annual notices. Because no new Form 486B24E filings can be made, the dataset is final and does not accrue new records.
Programmatically retrieve the full list of dataset archive files, download URLs and dataset metadata.
Dataset Index JSON API
Download the entire dataset as a single archive file.
Download Entire Dataset:
Download a single container file (e.g. monthly archive) from the dataset.
Download Single Container:
The dataset captures every EDGAR submission carrying the 486B24E form type. Form 486B24E is a hybrid post-effective amendment used by registered closed-end management investment companies operating as interval funds — funds that make periodic repurchase offers under Rule 23c-3. The "486B" component invokes Rule 486(b) under the Securities Act of 1933, which permits certain post-effective amendments by interval funds to become effective immediately upon filing rather than awaiting SEC declaration of effectiveness. The "24E" component invokes former Rule 24e-2 under the Investment Company Act of 1940, which allowed an investment company to register additional shares of an existing series by paying a registration fee tied to net sales during the prior fiscal year, computed on a specified offset basis. Combining the two rules in a single filing let an interval fund both refresh its registration statement on an immediately effective basis and increase the number of shares covered by that registration statement in one administrative act.
The underlying filing is therefore the entire amended registration statement in the form prescribed for the registrant — typically Form N-2 for a closed-end registrant, occasionally Form N-1A where the registrant's structure permitted it — together with the cover-page disclosures, fee table, and exhibits required by Rules 486(b) and 24e-2. The dataset description characterizes the underlying form as a "Post Effective Amendment of N-2s," but the actual N-form used inside the document body is a property of the registrant rather than of the 486B24E wrapper.
The dataset covers a closed historical population. Form 486B24E was usable only inside the narrow regulatory window during which Rule 486(b) post-effective amendments could simultaneously register additional shares under former Rule 24e-2, spanning roughly March 1996 through October 1997. Records are grouped into ZIP containers partitioned by filing year and month at the path YYYY/YYYY-MM.zip; inside each container, an accession lives at YYYY-MM/<18-digit-accession>/, where the folder name is the dashed accession number with hyphens removed and zero-padded to 18 digits. All records are pre-XBRL legacy SGML and ASCII text, distributed as .txt body files with a single metadata.json per accession. Image files attached to the original submission are intentionally omitted; only text-bearing per-document segments are materialized.
One record in the Form 486B24E Files Dataset is a single EDGAR submission of a Form 486B24E filing, identified by its accession number. On disk, the record is an accession-numbered folder containing a metadata.json descriptor and every text-bearing body document that arrived in the original SGML submission. The record therefore carries both the structured submission metadata (registrant identity, form type, dates, document inventory, EDGAR links, filer entity record) and the full text of the post-effective amendment, the underlying prospectus and statement of additional information, the Rule 24e-2 fee disclosures, and the accompanying exhibits.
An accession folder contains:
metadata.json file describing the EDGAR submission as a whole;document-1.txt, document-2.txt, ... document-N.txt, whose ordinal corresponds to the sequence value inside the metadata's documentFormatFiles array.The body documents are the per-document segments that EDGAR carved out of the original SGML submission. They are stored without their <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> SGML wrappers; those header values survive only inside metadata.json. Each body file therefore begins directly with its document content, almost always opening with a <PAGE> form-feed marker that establishes the first printed page of the underlying paper-equivalent document.
The original EDGAR filenames assigned by the filer (for example monetta.txt, ex11.txt) are not preserved on disk; the dataset uses the positional document-<n>.txt convention so that filenames are predictable and collisions impossible. Recovery of a body file's original document type, description, and EDGAR filename requires reading the matching documentFormatFiles[] entry whose sequence equals <n>.
metadata.json fieldsmetadata.json is a flat JSON object describing one accession. The substantive keys are:
formType — always "486B24E" for this dataset.accessionNo — dashed accession number, e.g. "0000950131-96-001610".filedAt — ISO-8601 timestamp with timezone offset, recording when the submission was accepted.periodOfReport — the period-of-report date carried on the cover page; for this form type it generally coincides with the filing date.description — human-readable form description (for example "Form 486B24E - Post Effective Amendments of N-2s").linkToFilingDetails — URL to the EDGAR archive directory for the accession.linkToTxt — URL to the original complete submission .txt on EDGAR.linkToHtml — URL to the EDGAR *-index.htm index page.linkToXbrl — empty string for every record in this dataset; these legacy filings predate XBRL entirely.documentFormatFiles — array of per-document descriptors. Each entry carries sequence, type (the EDGAR document type, e.g. 486B24E, EX-27, EX-99.B11, EX-99.18, EX-99), description (a short human label written by the filer), size, and documentUrl pointing to the per-document file on EDGAR. The numeric sequence values map 1:1 to the document-<n>.txt files materialized on disk. The trailing entry of the array is always a "Complete submission text file" pseudo-record with a blank sequence, representing the concatenated SGML submission on EDGAR; that pseudo-record is not materialized as a file inside the record.dataFiles — empty array; no XBRL or other structured data attachments existed for this form type.seriesAndClassesContractsInformation — array reserved for investment-company series/class identifiers; typically empty for these legacy 1996–1997 records because EDGAR's series/class infrastructure had not yet been introduced.entities — array of entity descriptors associated with the submission. For 486B24E filings the array commonly contains a single filer object holding cik, companyName (typically suffixed with a role tag such as "(Filer)"), fileNo (Investment Company Act file number, in the 811- series), act ("40", denoting the 1940 Act), fiscalYearEnd (in MMDD form), filmNo, and type ("486B24E").id — opaque 32-character hexadecimal identifier assigned by the dataset publisher, stable across re-downloads.Body documents are stored as plain text with legacy SGML markers. Five categories appear in practice:
The amended registration statement, prospectus, and SAI body. This is the largest document in the accession, carrying type equal to the form-type code (486B24E). It opens with the EDGAR cover page identifying the Securities Act and Investment Company Act file numbers, declaring the post-effective amendment number and the registrant's election of immediate effectiveness under Rule 485(b) (the parent rule under which 486(b) operates for interval funds), and presenting the Rule 24e-2 calculation of the registration fee. The body then continues into the prospectus, statement of additional information, and Part C information of the underlying N-form, including the fee table, financial highlights, investment-objective and policy disclosures, management and adviser disclosures, distribution and repurchase-offer mechanics, tax discussion, and the Part C undertakings, signatures, and exhibit index. Pagination is conveyed by <PAGE> form-feed markers, and tabular content (fee tables, financial highlights, condensed financial information) is delimited with the legacy EDGAR <TABLE>, <CAPTION>, <S>, and <C> tags that mark column boundaries for ASCII layout.
EX-27 Financial Data Schedule. Carried as a small text file using SGML-style tag/value pairs (for example <INVESTMENTS-AT-COST>, <TOTAL-ASSETS>, <NET-ASSETS>, <NET-ASSET-VALUE>). EX-27 is the Article 6 of Regulation S-X financial data schedule for investment companies — the structured summary of fund financial data that EDGAR required during the pre-XBRL era. It is the closest analogue in these filings to the structured financial reporting later supplied by XBRL.
EX-99.B11 (or similar) auditor consent. A short consent letter from the registrant's independent accountants permitting use of their audit report in the registration statement, signed /s/.
EX-99 counsel consent or opinion. A letter from outside legal counsel opining on the legality of the additional shares being registered, typically signed /s/ and addressed to the registrant's board.
EX-99.18 form-of-application or similar subscription document. A blank investor application or subscription form with checkbox and underscore field placeholders for individual, joint, custodial, trust, and entity accounts, intended for distribution alongside the prospectus.
The exact set of exhibits varies by registrant. The EX-27 schedule and the auditor and counsel consents are the most consistently present, because they are required to support the post-effective amendment and the additional-share registration.
Each record packages every per-document segment that appeared in the original EDGAR submission, with the following content directly readable inside the folder:
metadata.json covering form type, accession number, filing timestamp, period of report, EDGAR links, the document inventory, and the filer entity record.Image files attached to the original submission are intentionally omitted; only text-bearing documents are materialized. The "Complete submission text file" pseudo-entry that EDGAR appends to every accession's document list is described in the metadata but not stored on disk — it is the concatenated SGML envelope, redundant with the per-document segments. The SGML <DOCUMENT>, <TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>, and <TEXT> wrappers from the original submission are not retained inside the body files; their values survive only as fields in documentFormatFiles. There are no XBRL instance documents, no inline XBRL, and no auxiliary data attachments for this form type. Subsequent amendments to a 486B24E filing, where they exist, are filed under separate accession numbers as their own form-type submissions and are not bundled inside the original record.
Because Form 486B24E was usable only between roughly March 1996 and October 1997, there is essentially no within-form evolution to track. The form's content requirements were fixed by the joint application of Rule 486(b) and Rule 24e-2 throughout that period. When the SEC rescinded Rule 24e-2 in October 1997 in favor of the streamlined annual share-registration mechanism of Rule 24f-2, the 24E half of the form's mandate became obsolete, and registrants migrated to the plain Form 486BPOS post-effective amendment combined with a separate annual Rule 24f-2 notice (Form 24F-2NT). Every record in the dataset therefore exhibits the same structural conventions: a Rule 24e-2 fee calculation on the cover, an immediately-effective declaration under Rule 485(b)/486(b), and the underlying N-form registration statement body.
All records are pre-XBRL legacy SGML and ASCII text. The body files contain <PAGE> page-break markers, <TABLE>/<CAPTION>/<S>/<C> table delimiters, ASCII rule lines for visual separation, and SGML tag-style structured payloads in the EX-27 financial data schedule. The dataset does not carry HTML, XBRL, or inline iXBRL for this form: the form was discontinued before HTML became the EDGAR norm and roughly a decade before XBRL was introduced for fund financial reporting. File extensions inside accession folders are uniformly .txt, with metadata.json providing the only JSON content.
document-<n>.txt against the documentFormatFiles[] entry whose sequence field equals <n>. The body file alone carries no embedded type or description.accessionNo value and the on-disk folder name is a pure string transformation (accessionNo.replace(/-/g, "")).companyName strings inside entities carry parenthetical role suffixes (for example "(Filer)") that should be stripped if the role is wanted as a separate field.<S> (string column) and <C> (numeric column) tags. Plain whitespace splitting will misalign the columns; structural extraction should respect the legacy EDGAR table conventions.linkToXbrl and dataFiles are always empty for records in this dataset; downstream schemas should treat them as optional rather than required fields.Each record is a single post-effective amendment filed on EDGAR by a registered closed-end management investment company operating as an interval fund. The legal filer is always the registrant fund itself, identified by its own CIK and signed by its officers and trustees. Sponsors, advisers, distributors, and shareholders are not filers, even where an external adviser performs day-to-day operations.
Use of Form 486B24E was limited to registrants that met all of the following:
Open-end funds, unit investment trusts, traditional non-interval closed-end funds, business development companies, foreign private issuers, and operating companies were outside the form's scope.
A filing was triggered when an interval fund needed to do two things in one submission:
If only the disclosure update was needed, the fund used Form 486BPOS instead. The "486B" portion of the form code denotes the Rule 486(b) immediately effective route; the "24E" suffix denotes the Rule 24e-2 share-registration leg.
Upon filing under Rule 486(b), the post-effective amendment became effective on the filing date, or on a later date the registrant designated within the rule's window (generally up to 60 days after filing). No SEC declaration of effectiveness was required, allowing the interval fund's continuous offering to proceed without interruption while the share pool was topped up.
The form's lifespan is closed and the dataset is therefore final:
Form 486B24E sits at the intersection of two regulatory mechanisms: Rule 486(b) post-effective amendments for closed-end interval funds and Rule 24e-2 additional-share registration. Because the form was only valid during a roughly nineteen-month window (March 1996 to October 1997), the most useful comparisons fall into three groups: the 486-series amendments that surround it, the 24f-2 notice mechanism that absorbed its share-registration function, and the N-series registration statements that all 486 amendments modify.
Form 486BPOS. The closest living relative. Same Rule 486(b) safe harbor, same immediately effective treatment, same closed-end interval-fund filer population. The decisive difference: 486BPOS amends the registration statement only, with no Rule 24e-2 share-registration overlay or 24e-2 fee calculation. After Rule 24e-2 was rescinded in October 1997, interval funds shifted entirely to 486BPOS for amendments and used separate 24f-2 notices for share counts. 486BPOS spans a far longer history and a much larger population; 486B24E captures only the brief dual-purpose window.
Form 486APOS. The delayed-effective sibling under Rule 486(a), used when proposed changes are too material for the immediately effective 486(b) lane and carry a default sixty-day delayed effective date. 486APOS has no share-registration component. 486B24E required both 486(b) eligibility and a 24e-2 share registration; 486APOS satisfies neither condition.
Form 24F-2NT. The post-1997 successor to the share-registration function. Rule 24f-2 replaced Rule 24e-2 in October 1997 and shifted from prospective fixed-quantity registration to a retrospective annual notice filed within ninety days of fiscal year-end, reporting actual shares sold and the corresponding fee. 24F-2NT is decoupled from any prospectus amendment; 486B24E bundled share registration into a contemporaneous amendment. Continuity studies of additional-share registration must bridge the two datasets at the October 1997 transition.
Form N-2. The base closed-end registration statement that every 486B24E amendment modifies. Complementary, not substitutable: N-2 supplies the original registration architecture, fund strategy, fundamental policies, and initial share authorization; 486B24E supplies mid-life prospectus updates and incremental share registrations during the 1996-1997 window.
Form N-1A. The open-end fund registration statement (mutual funds and ETFs). Filer populations are mutually exclusive: open-end funds use the 485-series (485APOS and 485BPOS) for analogous post-effective amendments and never file in the 486-series. The structural parallel between 485(a)/485(b) and 486(a)/486(b) invites confusion, but 486B24E never appears on an N-1A registrant's filing history.
Form N-14 8C. The closed-end registration statement tied to mergers, consolidations, or reorganizations, paired with a proxy statement/prospectus describing a specific transaction. Although both involve registering closed-end shares, N-14 8C is an initial transaction-specific registration, while 486B24E is an ongoing amendment to an already-effective N-2 registering additional shares for routine interval-fund repurchase-offer operations. The two are not substitutes.
Form 486B24E is distinct because three constraints had to hold simultaneously: a closed-end interval-fund filer, an amendment eligible for Rule 486(b) immediate effectiveness, and additional-share registration under Rule 24e-2. 486BPOS shares the first two but lacks the share-registration leg. 486APOS shares the filer population but fails both the 486(b) and 24e-2 conditions. 24F-2NT carries the share-registration function but in a backward-looking annual notice decoupled from any amendment. N-2, N-1A, and Form N-14 8C are registration statements rather than amendments, and N-1A's population is entirely outside the 486-series. The result is a small, historically bounded dataset documenting a brief regulatory experiment that combined post-effective amendment and additional-share registration in a single immediately effective filing, before the SEC split the two functions into 486BPOS and 24F-2NT in late 1997.
Because Form 486B24E was usable only between March 1996 and October 1997, was filed exclusively by closed-end interval funds, and was retired when Rule 24e-2 was rescinded, its users are specialists who need exact historical coverage rather than market analysts.
Counsel practicing under the 1940 Act use the dataset to research the mechanics of Rule 486(b) combined with former Rule 24e-2. They read the prospectus body and amendment cover to see how immediately-effective post-effective amendments and additional-share registrations were drafted, and rely on the Rule 24e-2 fee calculation pages to support memos and opinion letters tracing the lineage to today's Rule 24f-2 framework.
Compliance staff at closed-end complexes use the dataset when reconstructing the registration history of legacy interval-fund products. They pull metadata.json (CIK, accession number, filed-as-of date) to sequence post-effective amendments and the Rule 24e-2 fee tables to verify share counts and fees paid, supporting recordkeeping reviews and SEC examination responses covering the 1996 to 1997 period.
Structuring lawyers documenting why current repurchase-program disclosures and effectiveness mechanics work as they do use the prospectus bodies and fee calculation pages as reference points for the operational difference between Rule 24e-2 share-by-share registration and the continuous Rule 24f-2 model.
Researchers cataloguing the evolution of investment-company share registration treat the dataset as the complete primary source for the form's nineteen-month regulatory episode. The metadata supports a comprehensive issuer timeline; the document text supports substantive analysis of how filers actually implemented the combined Rule 486(b) and Rule 24e-2 procedure.
Legal and finance academics writing on closed-end and interval-fund regulation cite the filings as documentary evidence on post-effective amendment regimes. The EX-27 financial data schedules, where present, provide point-in-time fund-level metrics for the small set of mid-1990s interval-fund issuers.
Teams ingesting the full EDGAR corpus consume metadata.json for indexing and CIK linkage and store original submission documents to keep archives byte-faithful. Even at this small population size, omitting the form type creates a visible gap in form-coverage reports and search interfaces.
Vendors building retrieval systems and classifiers over SEC filings use the dataset to ensure rare, discontinued form types are represented in training and evaluation sets. The amendments and prospectuses supply era-specific drafting conventions, and the form-type label itself trains classifiers to tag obscure filings rather than collapse them into common categories.
Audit and litigation-support teams working on disputes that reach back to 1996 to 1997 share issuances use the Rule 24e-2 fee pages to confirm shares registered and fees paid, the prospectus disclosures to establish what investors were told, and the metadata to anchor each filing to a specific accession number and date for evidentiary citation.
The use cases below reflect the dataset's scope as a closed historical population from the March 1996 to October 1997 window: precise reference work, archival completeness, and training-data coverage rather than ongoing market analysis.
A fund compliance officer responding to an SEC examination of a closed-end interval fund's pre-1998 registration history pulls each accession's metadata.json to sequence post-effective amendments by accessionNo, filedAt, and CIK, then reads the Rule 24e-2 fee calculation table on the cover page of the 486B24E body document to confirm the number of additional shares registered, the aggregate offering price, and the fee paid. The output is a per-CIK timeline of share authorizations and fees that ties cleanly into post-October-1997 Form 24F-2NT filings.
Investment-company counsel preparing a memo on the historical mechanics of combined Rule 486(b) immediate effectiveness and former Rule 24e-2 share registration reads the cover-page declarations and Rule 24e-2 calculation pages across the prospectus bodies in the dataset to extract canonical drafting language. The exhibit set (EX-99.B11 auditor consents, EX-99 counsel opinions) supplies model consent and opinion language that traces directly into modern 486BPOS practice.
Data engineers building a comprehensive EDGAR mirror ingest the dataset to close the 486B24E form-type gap in coverage dashboards and search facets. They consume metadata.json for CIK linkage, accession indexing, and documentFormatFiles[] mapping, and persist the document-<n>.txt bodies byte-faithful so that downstream consumers can reconstruct each original SGML segment. Even at the dataset's small size, the form type's absence shows up as a visible hole in form-coverage reports.
Legal-tech vendors building form-type classifiers and retrieval systems over the EDGAR corpus add the dataset to ensure rare, discontinued form types are represented. The formType field in metadata.json supplies ground-truth labels, and the prospectus and exhibit bodies supply era-specific 1996-1997 SGML and ASCII-table drafting conventions (<PAGE>, <TABLE>, <S>, <C>) that classifiers would otherwise misroute into more common categories such as 486BPOS.
Academic researchers studying mid-1990s closed-end interval funds parse the EX-27 financial data schedules using the SGML tag/value pairs (<INVESTMENTS-AT-COST>, <TOTAL-ASSETS>, <NET-ASSETS>, <NET-ASSET-VALUE>) to assemble a small panel of pre-XBRL fund-level metrics. Combined with the prospectus narrative on investment objectives and repurchase offers mechanics, this supports published work on how interval funds operated under the original Rule 23c-3 framework.
Auditors and litigation-support staff working disputes tied to 1996-1997 share issuances cite the Rule 24e-2 fee table to establish exactly how many shares were registered and what fee was paid, the prospectus body to establish what was disclosed to investors at the time, and metadata.json (accessionNo, filedAt, linkToFilingDetails) to anchor each filing to an immutable EDGAR location. The EX-99.B11 auditor consent and EX-99 counsel opinion provide the original signed attestations that may themselves become evidentiary exhibits.
SEC historians and regulatory archivists treating the dataset as the complete primary source for the form's nineteen-month life use the full document set to document how filers actually implemented the joint Rule 486(b) and Rule 24e-2 procedure before the SEC split the two functions into 486BPOS and 24F-2NT in late 1997. The fixed, closed population means an exhaustive read of every body document is feasible.
The dataset is accessible through three endpoints: a public JSON index for metadata discovery, a single-archive download for the entire dataset, and per-container downloads for individual monthly archives.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-486b24e-files.json
This endpoint returns dataset metadata and a list of all available container files. The metadata includes the dataset name, description, last updated timestamp, earliest sample date (1996-03-01), form types covered (486B24E), container format (ZIP), and the included file types (TXT, JSON). For each container, the response includes the file key, size, record count, last updated timestamp, and direct download URL. Although this dataset is fully historical and will not receive new records, the index can still be polled to confirm container availability or detect republished archives. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-6a91-963a-c72a3545ac29",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-486b24e-files.zip",
4
"name": "Form 486B24E Files Dataset",
5
"updatedAt": "2026-04-16T09:02:20.300Z",
6
"earliestSampleDate": "1996-03-01",
7
"totalRecords": 8,
8
"totalSize": 237133,
9
"formTypes": ["486B24E"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-486b24e-files/1996/1996-03.zip",
15
"key": "1996/1996-03.zip",
16
"size": 29641,
17
"records": 1,
18
"updatedAt": "2026-04-16T09:02:20.300Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-486b24e-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing all monthly containers from March 1996 through October 1997. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-486b24e-files/1996/1996-03.zip?token=YOUR_API_KEY
Downloads one monthly container ZIP, which contains accession-numbered subdirectories with a metadata.json file and the original EDGAR submission documents as document-<n>.txt files. Replace the year and month path segment to fetch a different month. This endpoint requires an API key.
The dataset covers EDGAR submissions filed on Form 486B24E, a hybrid post-effective amendment used by closed-end interval funds. It combines a Rule 486(b) immediately effective amendment to the registration statement with a Rule 24e-2 registration of additional shares under the Investment Company Act of 1940.
One record is a single EDGAR submission of a Form 486B24E filing, identified by its accession number. On disk it is an accession-numbered folder containing a metadata.json descriptor and every text-bearing body document from the original SGML submission — the amended prospectus, the statement of additional information, the Rule 24e-2 fee calculation, the EX-27 financial data schedule when present, and exhibits such as auditor consents and counsel opinions.
Only registered closed-end management investment companies operating as interval funds (funds that make periodic repurchase offers under Rule 23c-3) could file Form 486B24E, and only when they needed both an immediately effective Rule 486(b) post-effective amendment and a Rule 24e-2 registration of additional shares in the same submission. The legal filer is always the registrant fund itself; sponsors, advisers, distributors, and shareholders are not filers.
The dataset spans the form's full regulatory lifespan, from March 1, 1996 through October 1997. Form 486B24E became obsolete in October 1997 when the SEC rescinded Rule 24e-2 and replaced it with Rule 24f-2, under which interval funds register an indefinite number of shares and report sales retrospectively on Form 24F-2NT. After that transition, what had been a single 486B24E submission split into a Form 486BPOS amendment plus a separate Form 24F-2NT notice, and no new Form 486B24E filings can be made.
Both forms are immediately effective post-effective amendments under Rule 486(b) and share the same closed-end interval-fund filer population. The decisive difference is that 486BPOS amends the registration statement only, with no Rule 24e-2 share-registration overlay and no 24e-2 fee calculation. 486B24E bundled an additional-share registration into the amendment, while 486BPOS leaves share registration to a separate mechanism (Form 24F-2NT after October 1997).
The dataset is distributed as ZIP containers partitioned by filing year and month at YYYY/YYYY-MM.zip. Inside each container, every accession lives at YYYY-MM/<18-digit-accession>/ and contains a metadata.json file plus body documents named document-1.txt, document-2.txt, and so on. All body files are pre-XBRL legacy SGML and ASCII text; there are no HTML, XBRL, or inline iXBRL artifacts for this form.
Three endpoints are available. A public JSON index at https://api.sec-api.io/datasets/form-486b24e-files.json returns dataset metadata and a list of all containers and does not require an API key. The full dataset can be downloaded as one ZIP from https://api.sec-api.io/datasets/form-486b24e-files.zip?token=YOUR_API_KEY, and individual monthly containers can be downloaded from https://api.sec-api.io/datasets/form-486b24e-files/YYYY/YYYY-MM.zip?token=YOUR_API_KEY. The download endpoints require an API key.