Form S-2MEF Files Dataset

The Form S-2MEF Files Dataset is a closed historical corpus of Rule 462(b) "More Equity Filing" registration statements submitted to EDGAR on top of effective Form S-2 registrations between May 1996 and December 1, 2005. Each record corresponds to one S-2MEF accession — an issuer's election to register up to an additional 20% of securities of the same class as those on an already-effective parent S-2 — delivered as a compact cover-page document plus a metadata.json header. The filer is always the seasoned domestic operating-company issuer behind the parent S-2; underwriters, selling shareholders, and counsel are not filers. The dataset's terminal endpoint reflects the elimination of Form S-2 (and therefore Form S-2MEF) under the Securities Offering Reform adopted in SEC Release No. 33-8591, which retired the tiered S-1/S-2/S-3 framework in favor of the modern issuer-status regime. Records are packaged inside monthly ZIP containers and distributed as TXT, JSON, and HTML files.

Dataset APIs

Dataset Files

What This Dataset Contains

The dataset captures the complete EDGAR-era population of Form S-2MEF filings — 243 accessions spanning May 1996 through the form's sunset on December 1, 2005. Form S-2MEF is a Rule 462(b) registration statement whose "MEF" suffix denotes the abbreviated registration mechanism that lets an issuer register up to 20% in additional securities of the same class on top of a registration that has already become effective, without re-running the full registration process. The parent registration here is always a Form S-2 — a simplified registration form available to Exchange Act reporting companies with at least three years of reporting history that permitted heavy use of incorporation by reference to the issuer's periodic reports.

Because Rule 462(b) requires only that the new registration statement (i) identify the prior effective registration, (ii) register additional securities of the same class up to a 20% ceiling, and (iii) become effective upon filing if filed before the time of confirmation of sales, the S-2MEF body itself is extremely compact. It does not re-deliver the prospectus, the business description, the risk factors, or the financial statements; those remain in the underlying S-2 and are pulled in by reference. The dataset is therefore a closed historical population with no further accruals possible: Form S-2 (and Form S-2MEF with it) was eliminated effective December 1, 2005 under the Securities Offering Reform adopted in SEC Release No. 33-8591, which restructured the Securities Act registration regime around the surviving Form S-3/S-1 framework and the well-known seasoned issuer concept.

Each accession is delivered inside monthly ZIP containers organized as YYYY/YYYY-MM.zip and unpacks to a per-accession folder YYYY-MM/<18-digit-accession>/. File types in the corpus are TXT (ASCII-era cover pages and plain-text exhibits), HTML (post-HTML-adoption cover pages), and JSON (the dataset's own metadata.json). Image attachments from the original submission are excluded.

Content Structure of a Single S-2MEF Record

A single record in the Form S-2MEF Files Dataset corresponds to one S-2MEF registration statement submitted to EDGAR under a single accession number. Physically, each record is an accession-numbered folder containing two layers of content: a metadata.json capturing the EDGAR header and document manifest, and the filing's documents themselves — almost always a single short cover-page document, occasionally accompanied by a small number of exhibits.

A record stacks three layers of structure:

1. Packaging layer — the per-accession folder containing metadata.json and the unpacked filing documents.
2. EDGAR submission layer — the SGML envelope that historically wrapped each document inside the full submission. Unpacked documents in this dataset retain the outer SGML <DOCUMENT> wrapper with its header fields (<TYPE>, <SEQUENCE>, <FILENAME>, <DESCRIPTION>) ahead of the <TEXT> payload, so each file is HTML or ASCII text nested inside SGML rather than a clean standalone document.
3. Cover-page document layer — the S-2MEF facing page, fee table, Rule 415 election, incorporation-by-reference statement, and signature block, frequently delivered inside a <PRE> block that preserves the original fixed-width EDGAR layout.

metadata.json contents

The metadata.json file is present in every accession folder and mirrors the EDGAR header for the submission. The meaningful fields are:

• formType — uniformly "S-2MEF".
• accessionNo — the dash-formatted EDGAR accession number, e.g. "0000881453-03-000043".
• filedAt — an ISO-8601 timestamp with timezone offset capturing EDGAR receipt time.
• description — a human-readable filing description, typically "Form S-2MEF - Registration adding securities to prior Form S-2 registration [Rule 462(b)]".
• linkToFilingDetails, linkToHtml, linkToTxt — URLs to the EDGAR filing index page, the primary HTM document, and the complete SGML submission text file, respectively.
• linkToXbrl — empty; S-2MEF predates and does not carry XBRL.
• documentFormatFiles — an array describing each document in the EDGAR submission. Each entry carries sequence, size in bytes (as a string), documentUrl, description, and type. The complete .txt submission is itself listed here alongside the per-document HTM/TXT entries.
• dataFiles — typically empty; S-2MEF submissions carry no separate data files.
• entities — an array of filer entity records. Each entity carries companyName with role appended in parentheses (e.g. "AMERICAN SKANDIA LIFE ASSURANCE CORP/CT (Filer)"), cik (10-digit zero-padded), irsNo, fileNo (the SEC-assigned 333- series file number for the registration), stateOfIncorporation, fiscalYearEnd (MMDD), sic (code plus description, e.g. "6399 Insurance Carriers, NEC"), act (the Securities Act under which the filing is made, e.g. "33"), type (form type), and filmNo.
• id — a 32-character hex identifier internal to the dataset.

The fileNo field is especially load-bearing: Rule 462(b) registers additional securities under the same 333- file number as the parent S-2, so this field is the direct join key linking the MEF record to its parent registration without requiring text extraction from the cover page.

Cover-page document anatomy

The primary document follows the standard EDGAR registration-statement facing-page template, compressed to the minimum required by Rule 462(b). Top-to-bottom, the typical content blocks are:

• Facing-page header — naming the SEC, identifying the document as a Registration Statement under the Securities Act of 1933, and identifying the form as Form S-2MEF.
• Registrant identification block — exact name of the registrant as specified in its charter, state or other jurisdiction of incorporation, primary SIC code, IRS Employer Identification Number, principal executive office address and telephone number, and the name and address of the agent for service of process.
• Cross-reference to the parent registration — the 333- file number of the related Form S-2, together with a Rule 462(b) statement that the filing registers additional securities (up to 20%) of the same class.
• Rule 415 election — a checkbox indicating whether the offering is a delayed or continuous offering pursuant to Rule 415.
• Calculation of Registration Fee table — typically a single row showing the title of each class of securities to be registered, the amount being registered, the proposed maximum offering price per unit, the proposed maximum aggregate offering price, and the registration fee. This table is the operative substantive content of the filing and the primary numeric payload of the record.
• Incorporation-by-reference clause — stating that the prospectus contained in the prior effective Form S-2 (and any amendments to it) is incorporated by reference into the S-2MEF without substantive change, as permitted by Rule 462(b).
• Confirmatory paragraph — short boilerplate confirming that no changes other than the addition of the new securities and the related fee calculation are being made.
• Signatures block — signatures of the registrant, its principal executive officer, principal financial officer, controller or principal accounting officer, and a majority of its board of directors (or persons performing similar functions), generally executed pursuant to powers of attorney previously filed with the parent S-2.

The body is short — a few hundred to a few thousand words — and is delivered as HTML markup wrapped by the EDGAR SGML <DOCUMENT> envelope. Because most filers reused the parent S-2 facing-page template, the prose is often rendered inside a <PRE> block to preserve the column alignment of the fee table and the right-justified signature lines.

What is and is not in the record

Included:

• The metadata.json header for the submission.
• The primary S-2MEF cover page, as an SGML-wrapped HTM or TXT file.
• Any additional documents transmitted in the same submission and listed in documentFormatFiles, such as a legal opinion (Exhibit 5), consent of independent accountants (Exhibit 23), or power of attorney (Exhibit 24), when the issuer chose to file them with the S-2MEF rather than rely solely on those already on file with the parent S-2. These exhibits are delivered as plain text or HTM with their SGML wrappers retained.

Not included:

• The underlying Form S-2 prospectus and all of the substantive disclosure it contains (business description, properties, legal proceedings, market for the registrant's stock, MD&A, financial statements, exhibits). To read the substantive content of the offering, a downstream user must follow the 333- file number back to the parent S-2.
• Image files from the original EDGAR submission (logos, signature graphics, scanned exhibits).
• A standalone unpacked copy of the SGML .txt complete submission file. EDGAR generates this concatenated file for every submission and its URL is recorded in metadata.json under linkToTxt, but it is not present as a separate artefact in the folder.
• XBRL or iXBRL payloads. Form S-2MEF was retired before structured-disclosure tagging applied to registration statements.

Structural stability and terminal event

Form S-2MEF was a stable, narrowly-scoped form throughout its EDGAR life. The Rule 462(b) mechanism that drives its content was adopted in 1996 to let issuers register additional securities quickly when an offering proved larger than originally anticipated, and the form's content requirements did not change in any material way over its nine-and-a-half-year life. Every record contains the same core elements: a facing page identifying the registrant, a cross-reference to the parent S-2's 333- file number, a single Calculation of Registration Fee table, an incorporation-by-reference statement, and signatures.

The form's terminal event is structural rather than internal: under the Securities Offering Reform adopted in Release No. 33-8591, the SEC eliminated Form S-2 effective December 1, 2005, which automatically retired Form S-2MEF as well, since the latter is by construction a Rule 462(b) overlay on an effective S-2. Rule 462(b) itself survived the reform and continues to operate over the remaining registration forms (Form S-1MEF, Form S-3MEF, Form F-1MEF, Form F-3MEF).

Data-format evolution

Form S-2MEF lived entirely inside EDGAR's modern submission era. Early filings (1996–1997) are most often delivered as plain ASCII text wrapped in SGML <DOCUMENT> envelopes; later filings (roughly 1999 onward) increasingly use HTM documents with HTML markup inside the same SGML envelope. The file types found in the dataset are TXT, JSON, and HTML, reflecting this transition: the JSON layer is the dataset's own metadata.json, TXT covers ASCII-era cover pages and plain-text exhibits, and HTML covers post-HTML-adoption cover pages.

A practical consequence is that even the HTM documents in the later years cannot be parsed as standalone HTML without first stripping or accounting for the outer SGML wrapper. The <TYPE>, <SEQUENCE>, <FILENAME>, and <DESCRIPTION> header fields sit above the <TEXT> block, and many filers wrap the body in <PRE> to preserve fixed-column layout inherited from the ASCII facing-page template.

Interpretation notes

• Rule 462(b) shapes everything. An S-2MEF is intentionally not self-contained: it adds securities to an effective registration but does not reproduce the prospectus. Substantive analysis of the offering — pricing, use of proceeds, business and risk disclosure, financials — requires joining the S-2MEF to the parent S-2 via the shared 333- file number, available both on the cover page and in metadata.json under entities[].fileNo.
• filedAt is effectively the effective time. Because Rule 462(b) registrations become effective upon filing (when filed before confirmation of sales), the filedAt timestamp serves, for practical purposes, as the effective time of the additional registration.
• The fee table is the operative payload. The "amount registered" and "maximum aggregate offering price" entries quantify exactly how much additional capacity the issuer is adding, capped at 20% of the dollar amount previously registered on the parent S-2.
• Signatures rely on existing powers of attorney. The S-2MEF generally does not reproduce the powers of attorney themselves; they live in the parent S-2's Exhibit 24.
• Multi-document submissions are rare. When they occur, the additional documents listed in documentFormatFiles are usually a fresh legal opinion or auditor consent supporting the additional securities, rather than a re-filing of the parent S-2's exhibit set.
• Amendments are uncommon. The form's narrow scope leaves little to amend; corrective filings, when they occur, are typically follow-on S-2/A amendments to the parent rather than amendments to the MEF itself.
• Issuer-specific variation is limited. The cover-page template is highly standardized; the most useful free-text field for downstream classification is the description of the title of securities being registered (common stock, depositary shares, variable annuity contracts, debt securities, units), which varies with the parent S-2's offering structure.
• Extraction strategy. The most reliable structured fields live in metadata.json (CIK, file number, filed-at, SIC, state of incorporation, entity role). Fee-table values must be extracted from the cover-page document itself and require parsing through the SGML wrapper and, frequently, through a <PRE> block; column alignment is whitespace-based in ASCII-era filings and table-based in HTM-era filings, so extractors should branch on actual document markup rather than on filing date alone.

Who Files or Publishes This Dataset, and When

The filer of a Form S-2MEF is the same issuer that filed the underlying Form S-2 to which it relates. The MEF is not a standalone registration; it piggybacks on an already-effective Form S-2, adding capacity for the same class of securities under Rule 462(b). The legal filer on EDGAR is the issuer of the securities — underwriters, selling shareholders, and counsel are not filers of the MEF, even when named in the parent S-2.

Filer eligibility

The filer population is defined by Form S-2 eligibility, which was limited to seasoned domestic operating-company issuers that:

• were subject to the periodic reporting requirements of Section 13 or 15(d) of the Exchange Act,
• had been subject to those requirements for at least three years,
• had filed all required Exchange Act reports timely for the prior twelve months, and
• otherwise satisfied the General Instructions to Form S-2.

Form S-2 sat between Form S-1 (issuers without significant reporting history) and Form S-3 (large, more-seasoned issuers eligible for forward incorporation by reference). S-2 filers were typically three-year reporting companies that did not meet S-3's float or other tests.

The following parties fall outside the S-2MEF filing population:

• foreign private issuers (used F-2MEF or other F-series MEFs),
• issuers without three years of Exchange Act reporting,
• issuers whose parent registration was on S-1, S-3, S-4, S-8, S-11, or SB-2 (used the matching MEF variant),
• investment companies and BDCs (N-series regime),
• offerings under Regulation A, D, or S, or other exempt frameworks.

When the record is created

An S-2MEF is event-driven, not periodic. It arises only when an issuer with an effective Form S-2 decides at or near pricing that it wants to sell more securities than the parent S-2 already covers, and elects to register the additional amount through the expedited Rule 462(b) mechanism rather than file a new registration statement.

Rule 462(b) requires that all of the following be true at filing:

• the parent Form S-2 is already effective,
• the additional securities are of the same class as those on the effective S-2,
• the aggregate offering price registered on the MEF does not exceed 20% of the maximum aggregate offering price in the parent S-2's "Calculation of Registration Fee" table,
• the filing is made before the earlier of confirmation of sales of the additional securities or the close of business on the date of filing, and
• the registration fee for the additional securities is paid at or before filing.

When these conditions are met, the S-2MEF becomes effective automatically upon filing — no SEC staff review, no acceleration request, no waiting period. In practice, MEFs are transmitted to EDGAR the same day the underwritten offering prices. The MEF itself is a short cover instrument: facing page, fee table for the additional securities, signatures, and any required opinions and consents. Substantive disclosure remains in the parent S-2 and any Rule 424(b) prospectus supplement. Amendments to S-2MEFs are rare; corrections typically flow through post-effective amendments to the parent S-2 or through prospectus supplements.

Dataset coverage and important distinctions

The dataset spans Form S-2MEF filings made to EDGAR from May 1996 through the form's sunset on December 1, 2005. The start date reflects EDGAR's general phase-in for domestic registrants; the endpoint is set by Securities Offering Reform (Release No. 33-8591), which eliminated the S-1/S-2/S-3 tiered system in favor of an issuer-status framework (WKSI, seasoned, unseasoned reporting, non-reporting) and the modern automatic shelf regime. No Form S-2MEF filings exist after December 1, 2005.

A few practical distinctions:

• An S-2MEF is not a substitute for a new registration statement. Upsizing beyond 20%, registering a different class, or covering an offering not already on an effective S-2 requires a new full registration.
• An S-2MEF is not a post-effective amendment. Post-effective amendments update the parent S-2; the MEF instead registers additional same-class securities under the 462(b) cap.
• S-3-eligible issuers generally used Form S-3 and Form S-3MEF, not S-2/S-2MEF, because S-3 permitted forward incorporation by reference and shelf use.
• Foreign private issuers used F-2MEF under the parallel F-series regime; small business issuers used SB-2MEF in connection with Form SB-2 offerings.
• Because Rule 462(b) makes the MEF effective on filing, SEC staff does not issue comments on the MEF itself; any disclosure review occurred on the parent S-2.

How This Dataset Differs From Similar Datasets or Filings

Form S-2MEF sits at the junction of three filing regimes: the retired Form S-2 family, the Rule 462(b) "MEF" mechanism for adding up to 20% incremental capacity, and the broader universe of registration amendments and prospectus filings. The closest comparators are the parent S-2, the sibling MEFs tied to other base forms, the 424B prospectus filings, and S-2/A amendments.

Form S-2 (the parent registration statement)

Form S-2 was the mid-tier Securities Act registration available to issuers with at least three years of Exchange Act reporting that permitted incorporation by reference of prior Exchange Act filings. An S-2MEF cannot stand alone: it references a specific, already-effective parent S-2 and registers only additional securities of the same class.

Key differences:

• An S-2 contains the full prospectus, risk factors, and incorporated reports; an S-2MEF contains only a cover and fee table.
• S-2 filings span the entire issuer disclosure; S-2MEFs are filed only when an issuer needs to exceed the dollar amount originally registered.
• Both forms were eliminated December 1, 2005 (Release No. 33-8591), but S-2MEF usage is sparse compared to the much larger S-2 population.

Use S-2 for substantive disclosure; use S-2MEF as evidence that the parent registration's capacity was exhausted and topped up.

Other Rule 462(b) MEF variants (S-1MEF, S-3MEF, S-11MEF, F-1MEF, F-3MEF, SB-2MEF)

All MEFs share the same mechanic: Rule 462(b), 20% same-class cap, immediate effectiveness on filing. They differ only in the parent form, which in turn defines the eligible issuer population:

• S-1MEF: extends Form S-1 (general long-form, often IPOs and non-seasoned issuers).
• S-3MEF: extends Form S-3 (large, seasoned shelf issuers; the dominant MEF in modern practice).
• S-11MEF: extends Form S-11 (real estate and REITs).
• F-1MEF / F-3MEF: extend the foreign private issuer analogues.
• SB-2MEF: extends Form SB-2 (small business, retired in 2008).

Mechanically the filings look identical. What S-2MEF uniquely captures is capacity expansion by mid-tier seasoned issuers — those eligible for S-2 but not S-3 — during the 1996–2005 window. For any other issuer tier, use the corresponding sibling MEF.

Form 424B (prospectus filings)

The 424B family carries the priced prospectus actually delivered to investors. Overlap with S-2MEF is purely sequential, not substantive:

• 424B carries pricing, final prospectus text, and offering economics; S-2MEF carries no prospectus content.
• 424B is filed at or near every takedown; S-2MEF is filed once, only when registered capacity is exhausted.
• 424B supplements a registration that is already effective; S-2MEF itself creates new effectiveness for the incremental shares.

An S-2MEF is typically followed by a 424B reflecting the larger offering. The datasets are complementary: MEF documents the capacity expansion, 424B documents what was sold against it.

Form S-2/A (amendments to S-2)

S-2/A and S-2MEF both modify a live S-2, but via different rules:

• S-2/A is the route for substantive disclosure changes, SEC comment responses, or post-effective amendments under Rule 462(c); effectiveness generally requires SEC action.
• S-2MEF, under Rule 462(b), is effective on filing but is strictly limited to a 20% same-class capacity increase with no disclosure changes.
• S-2/A filings are longer and disclosure-driven; S-2MEFs are short and formulaic.

For amended disclosure or staff-comment trails, use S-2/A. For evidence of an immediate, mechanical capacity top-up, use S-2MEF.

Rule 462(a) vs 462(b) vs 462(c)

Only Rule 462(b) produces a distinct form type. Rule 462(a) governs ordinary effectiveness (reflected in the underlying S-1/S-2/S-3 itself), and Rule 462(c) governs post-effective amendments (filed as /A). The S-2MEF dataset is therefore the form-specific record of Rule 462(b) capacity expansions tied to Form S-2 parents — no other dataset captures this slice directly.

Boundary summary

The S-2MEF Files Dataset is narrow by design. It excludes substantive registration disclosure (in the parent S-2), priced prospectus terms (in 424B), amendment-driven changes (in S-2/A), and 462(b) filings tied to other base forms (in sibling MEF datasets). What it uniquely captures is the historical record, May 1996 through December 1, 2005, of mid-tier seasoned issuers — eligible for S-2 but not S-3 — exercising an immediate-effectiveness 20% top-up under a regime that no longer exists. For that specific question it has no substitute; for any broader view of the same offering, pair it with the parent S-2, related 424Bs, and any S-2/A amendments.

Who Uses This Dataset

Because the corpus is closed and narrowly scoped, it supports historical, legal, and template-mining workflows rather than real-time monitoring. The audiences below all anchor their work in metadata.json (accession number, issuer, filing timestamp, parent 333- file number) and pull substantive content from the short-form cover-page text, the fee table, and any exhibits.

Securities and capital markets attorneys

Used as a primary-source archive of pre-2005 Rule 462(b) practice on the retired Form S-2. Counsel pulls the cover page, incorporation-by-reference clauses, parent 333- file number, and legal opinion exhibits to support memoranda comparing 462(b) execution across S-1, S-2, and S-3 contexts and to draft analogous short-form filings under the current regime.

Legal historians and academic researchers

Used to ground empirical work on the simplified registration framework before Release No. 33-8591. Population-level metadata — issuer name, filing date, and parent-filing reference — lets researchers quantify how often the 20% upsizing right was exercised, by which issuer categories, and the lag between parent S-2 effectiveness and the MEF.

Equity capital markets and syndicate desks

Used as the historical control set for upsizing precedent now executed via S-1MEF and S-3MEF. The registration fee table, issuer, and filing timestamp drive precedent decks and training material on how desks sized and timed the 20% expansion relative to pricing.

Registration-statement drafters

Used as a template library for short-form upsizing language. Drafters open filings by accession number and copy cover-page conventions, the explicit reference to the parent registration, the abbreviated fee calculation, and the exhibit list into modern MEF drafts. The HTML and TXT documents are the working artifacts; the metadata file is the index.

RegTech and document-classification engineers

Used as a clean, exhaustive labeled class for a rare form type. The full-text TXT and HTML documents support tokenization, layout parsing, and exhibit segmentation, while metadata supplies ground-truth form type, filing date, and accession number for classifiers that must separate S-2MEF from neighboring S-1, S-2, S-3 and their MEF variants.

Financial historians of equity issuance

Used to identify which issuers exercised the 20% capacity right across the dot-com run-up, the post-bubble correction, and the early Sarbanes-Oxley period. Issuer name and filing date join to external pricing and sector data; the fee table supplies the dollar magnitude of incremental registered capacity.

Compliance and corporate-records teams

Used by long-tenured issuers and their outside counsel to reconstruct legacy registered-offering capacity. The parent 333- file number linkage, filing copy, and accession-level metadata evidence what was registered, by whom, and when, feeding regulator response packages and historical capitalization tables.

Corporate finance and event-study researchers

Used to define a clean event set where the only material change is a 20% upsizing of an already-effective offering. Filing date and issuer anchor the event timestamp and cross-sectional unit for price-impact studies and tests of whether MEFs predicted strong demand. Because the dataset is closed and exhaustive, it functions as a population, not a sample.

Specific Use Cases

The use cases below focus on workflows where the dataset's scope, combined with the cover-page and metadata payload, produces a concrete output.

Quantifying the historical exercise rate of the 20% upsizing right

Build a population-level table of S-2 issuers that topped up registered capacity under Rule 462(b). Use entities[].cik, entities[].fileNo, and filedAt from metadata.json to link each MEF back to its parent S-2, then extract the "amount registered" and "maximum aggregate offering price" rows from the Calculation of Registration Fee table on the cover page. Output is a per-parent capacity-expansion ratio (MEF dollars / parent S-2 dollars) used in academic work on the pre-2005 simplified-registration regime.

Mining cover-page language for modern MEF drafting

Pull the incorporation-by-reference clause, parent 333- file-number reference, and abbreviated fee-table caption from each cover-page TXT or HTM document and cluster by language pattern. Drafters use the resulting template library to model short-form upsizing language for current S-1MEF and S-3MEF filings, where Rule 462(b) mechanics survive but the parent form does not.

Training and evaluating a form-type classifier across the MEF family

Use the SGML-wrapped cover-page documents as a clean, fully labeled class for S-2MEF, paired with formType and accessionNo in metadata.json as ground truth. The corpus supports tokenization and layout-parsing experiments that must distinguish S-2MEF from neighboring S-1, S-2, S-3 base forms and their MEF siblings, particularly across the ASCII-era and HTM-era markup transition.

Reconstructing legacy registered-offering capacity for a single issuer

Given an issuer CIK, retrieve every S-2MEF filed by that registrant, read the parent 333- file number from entities[].fileNo, and sum incremental dollar amounts from each fee table. Output is a per-issuer ledger of registered capacity additions used by compliance teams responding to regulator inquiries or reconstructing legacy capitalization tables for long-tenured registrants.

Building event sets for price-impact and demand-signal studies

Treat each filedAt timestamp as the effective time of an exogenous 20% capacity expansion on an already-effective offering. Join issuer CIK and SIC from metadata.json to external CRSP/Compustat pricing and sector data to test whether MEF filings predict subsequent takedown size or short-window abnormal returns. Because the dataset is closed and exhaustive, no sampling correction is required.

Pairing S-2MEF capacity expansions with subsequent 424B takedowns

For each accession, use entities[].fileNo to retrieve all 424B prospectus filings on the same 333- registration and align them by filing date. The resulting MEF-to-424B sequences quantify how quickly issuers consumed the topped-up capacity, supporting syndicate-desk precedent decks on sizing and timing the 20% expansion relative to pricing.

Dataset Access

Dataset Index JSON API: https://api.sec-api.io/datasets/form-s2mef-files.json This endpoint returns dataset metadata (name, description, last updated timestamp, earliest sample date, total records and total size, form types covered, container format, and file types), the full dataset download URL, and the list of individual container files with per-container metadata such as key, size, records, updatedAt, and downloadUrl. Because Form S-2MEF was discontinued in December 2005, the dataset is static, but the endpoint can still be polled to confirm the latest refresh state and to discover which monthly containers exist. No API key is required to call this endpoint.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ae0-6a1f-a28d-eb58a97f3d9c",
        

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

          4
            "name": "Form S-2MEF Files Dataset",
        

          5
            "updatedAt": "2026-04-16T08:28:49.912Z",
        

          6
            "earliestSampleDate": "1996-05-01",
        

          7
            "totalRecords": 243,
        

          8
            "totalSize": 1156184,
        

          9
            "formTypes": ["S-2MEF"],
        

          10
            "containerFormat": "ZIP",
        

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

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-s2mef-files/1996/1996-05.zip",
        

          15
                "key": "1996/1996-05.zip",
        

          16
                "size": 18432,
        

          17
                "records": 3,
        

          18
                "updatedAt": "2026-04-16T08:28:49.912Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Download Entire Dataset: https://api.sec-api.io/datasets/form-s2mef-files.zip?token=YOUR_API_KEY Downloads the complete dataset as a single ZIP archive containing every S-2MEF filing from May 1996 through December 2005. The archive is small, so a one-shot download is usually the simplest option. This endpoint requires an API key.

Download Single Container: https://api.sec-api.io/datasets/form-s2mef-files/1996/1996-05.zip?token=YOUR_API_KEY Downloads a single monthly container instead of the full archive. Use the key and downloadUrl fields from each entry in the containers array of the index JSON to fetch a specific month. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

The dataset covers Form S-2MEF, a Rule 462(b) "More Equity Filing" registration statement that adds up to 20% in additional securities of the same class on top of an already-effective parent Form S-2. The "MEF" suffix denotes the abbreviated registration mechanism that becomes effective immediately upon filing, without SEC staff review.

What does one record in this dataset represent?

One record represents a single S-2MEF accession on EDGAR, delivered as an accession-numbered folder containing a metadata.json header and the filing documents — typically a single short cover-page document with a Calculation of Registration Fee table, an incorporation-by-reference clause, and signatures. Occasionally a record includes additional documents such as a legal opinion (Exhibit 5), consent of independent accountants (Exhibit 23), or power of attorney (Exhibit 24).

Who is required to file Form S-2MEF?

The filer is always the same issuer that filed the underlying Form S-2. Eligibility tracks Form S-2 eligibility: seasoned domestic operating-company issuers subject to Exchange Act Section 13 or 15(d) reporting for at least three years, that filed all required reports timely for the prior twelve months, and that otherwise satisfied the General Instructions to Form S-2. Foreign private issuers, S-1/S-3/S-11 filers, and investment companies are outside the population.

Why does the dataset end in December 2005?

Form S-2 was eliminated effective December 1, 2005 under Securities Offering Reform Release No. 33-8591, which restructured Securities Act registration around the surviving Form S-3/S-1 framework and the well-known seasoned issuer concept. Because Form S-2MEF is by construction a Rule 462(b) overlay on an effective S-2, it was retired automatically with its parent form. No Form S-2MEF filings exist after December 1, 2005.

What file formats are in the dataset, and how is it distributed?

Files are distributed as TXT, JSON, and HTML inside monthly ZIP containers organized as YYYY/YYYY-MM.zip. The JSON layer is the dataset's own metadata.json; TXT covers ASCII-era cover pages and plain-text exhibits; HTML covers post-HTML-adoption cover pages. Note that the document files retain their outer EDGAR SGML <DOCUMENT> wrapper, so HTM payloads cannot be parsed as standalone HTML without first accounting for the SGML envelope.

How do I link an S-2MEF record back to its parent Form S-2?

Use the entities[].fileNo field in metadata.json. Rule 462(b) registers additional securities under the same 333- series SEC file number as the parent S-2, so fileNo is the direct join key linking the MEF to its parent registration without requiring text extraction from the cover page. The same 333- file number also appears on the cover page itself, in the cross-reference to the parent registration.

How does Form S-2MEF differ from Form S-2/A?

Both modify a live S-2, but via different rules. S-2/A is the route for substantive disclosure changes, SEC comment responses, or post-effective amendments under Rule 462(c), and effectiveness generally requires SEC action. S-2MEF, under Rule 462(b), is effective immediately on filing but is strictly limited to a 20% same-class capacity increase with no disclosure changes — it carries no prospectus content, only a cover page and fee table.