The Form SB-1MEF Files Dataset is a complete EDGAR archive of every Form SB-1MEF submission filed under Rule 462(b) of the Securities Act of 1933, the abbreviated registration statement that small-business issuers used to register up to 20% in additional securities on top of an already-effective Form SB-1. Each record is one EDGAR submission, identified by an 18-digit accession number and packaged as a per-accession folder containing a structured metadata.json plus the original filer-submitted registration-statement HTML and PDF rendition. Filers are domestic or Canadian small-business issuers that qualified under Regulation S-B (annual revenues and public float each below $25 million, with an additional $10 million rolling-12-month cash-offering ceiling on the parent SB-1). The dataset spans the entire operational life of the form on EDGAR, from the earliest sample on 2001-11-01 through the SEC's August 2008 elimination of Regulation S-B, and is delivered as ZIP containers holding HTML, PDF, and JSON file types.
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 is a closed historical archive of Form SB-1MEF filings as the issuers submitted them to EDGAR. Form SB-1MEF was an abbreviated registration statement filed under Rule 462(b) of the Securities Act of 1933 by small-business issuers to register up to 20% in additional securities of an offering already covered by a previously effective Form SB-1. The "MEF" suffix marks the 462(b) variant: the registration statement became effective immediately upon filing, on the strength of the parent SB-1 registration and without an additional staff review cycle. Form SB-1 itself was an optional simplified registration form available under Regulation S-B to issuers whose annual revenues and aggregate public float were each below $25 million. The SEC eliminated Regulation S-B and all its associated forms — SB-1 and SB-1MEF included — in 2008, folding small-business issuers back into the scaled disclosure regime under Regulation S-K. SB-1MEF had a short operational life on EDGAR running from November 2001 through August 2008, and the dataset spans that entire window.
The MEF nature of the filing is signalled not by a different form template but by a checkbox election on the SB-1 cover page invoking Rule 462(b), accompanied by the SEC file number of the parent SB-1 registration the issuer is augmenting. The substantive new content of an MEF filing is concentrated in two places: the 462(b) cross-reference and the Calculation of Registration Fee table, which together quantify the incremental securities being registered. Everything else in the document is the inherited Form SB-1 cover and prospectus layout. The dataset is distributed as ZIP containers holding HTML, PDF, and structured JSON file types; image attachments referenced from the EDGAR submission are excluded by design.
One record in the Form SB-1MEF Files Dataset is a single EDGAR submission of Form SB-1MEF, identified by its 18-digit accession number and packaged as a per-accession folder inside a year-month ZIP container. Each record bundles a single structured metadata.json describing the submission together with the original EDGAR-submitted documents of that filing, with image attachments stripped. The record unit is the complete Rule 462(b) abbreviated registration statement as the issuer filed it — not an extracted section, not a derived event, and not a per-document row.
A record consists of three layers:
YYYY-MM/ root inside the year-month ZIP container.metadata.json file holding EDGAR submission-header fields, a document inventory, and the filer entity records.The complete-submission .txt SGML wrapper that EDGAR generates for the filing is referenced from metadata.json by URL but is not stored as a separate file inside the record folder. Sequence numbers in documentFormatFiles[] are therefore not contiguous on disk: gaps mark images that were stripped, and the trailing complete-submission entry has no on-disk counterpart.
metadata.json blockmetadata.json is the structured spine of the record. It exposes filing-level identifiers, document-level inventory, and entity-level filer information.
Filing-level fields include formType (always SB-1MEF), accessionNo in canonical dashed form (e.g. 0001103132-01-500055), filedAt as a timezoned ISO timestamp, periodOfReport as a date, a human-readable description (Form SB-1MEF - Registration adding securities to prior Form SB-1 registration [Rule 462(b)]), and a stable internal id. URL fields point back to EDGAR: linkToFilingDetails for the primary registration-statement HTML, linkToTxt for the complete-submission SGML text wrapper, linkToHtml for the EDGAR filing-index page, and linkToXbrl, which is empty for this form because SB-1MEF predates the XBRL requirements that later applied to registration-statement disclosures.
documentFormatFiles[] enumerates every document in the original EDGAR submission, with sequence, size in bytes as a string, documentUrl, description, and type. The canonical SB-1MEF pattern is sequence 1 as the registration-statement HTML carrying type SB-1MEF, an optional sequence 2 image (excluded from the on-disk payload), a PDF rendition typed SB-1MEF at sequence 3, and a trailing entry with blank sequence and type whose description is Complete submission text file, representing the wrapping .txt.
entities[] describes the filer roster as recorded on the EDGAR header. Each entity carries cik, companyName, fileNo (the EDGAR-assigned file number of the current registration), irsNo, stateOfIncorporation, an sic industry code with its label, fiscalYearEnd, act (33 for the Securities Act of 1933), type (SB-1MEF), filmNo, and a tickers[] array. The current filing's fileNo here is distinct from, and should not be confused with, the parent SB-1 file number that appears on the document cover next to the 462(b) checkbox.
seriesAndClassesContractsInformation[] and dataFiles[] are reserved for fund-style series/class metadata and for structured-data attachments respectively. Both are empty for SB-1MEF records.
The registration-statement HTML is wrapped in an EDGAR SGML document envelope of the form:
1
<DOCUMENT>
2
<TYPE>SB-1MEF
3
<SEQUENCE>1
4
<FILENAME>...
5
<DESCRIPTION>REGISTRATION
6
<TEXT>
7
<html>...</html>
8
</TEXT>
9
</DOCUMENT>
Inside the <TEXT> block, the body is a full Form SB-1 registration statement with MEF-specific cover-page elections. In document order the typical components are:
Cover page — rendered with the heading FORM SB-1, not SB-1MEF, because the MEF designation governs how the filing becomes effective rather than the underlying form template. The cover carries the issuer's exact legal name, state or other jurisdiction of incorporation, primary SIC code, IRS Employer Identification Number, address of the principal executive offices, and the name and address of the agent for service of process.
Calculation of Registration Fee table — a load-bearing tabular block on the cover. Columns are the title of each class of securities being registered, the amount to be registered, the proposed maximum offering price per unit, the proposed maximum aggregate offering price, and the registration fee. Because the entire purpose of an MEF filing is to register additional securities of up to 20% of the original offering, this table is what quantifies the incremental registration. It is always present and always populated.
Rule 462(b) reference block — the structural element that makes the filing an SB-1MEF rather than a plain SB-1. The cover explicitly checks the 462(b) box and supplies the file number of the original effective Form SB-1 the new filing augments, typically expressed as File Number 333-XXXXX. This cross-reference is the canonical link back to the parent SB-1 registration; it is a Securities Act file number, not the accession number of the parent filing.
Disclosure-alternative election and prospectus date — Form SB-1 cover-page checkboxes selecting between the Alternative 1 and Alternative 2 disclosure formats permitted under SB-1, plus the prospectus date.
Prospectus body — the bulk of the document. In the SB-1 disclosure framework this typically includes an offering summary, risk factors, use of proceeds, determination of offering price, dilution analysis, plan of distribution, business description, management's discussion and analysis, management and director information, executive compensation, security ownership of certain beneficial owners and management, certain relationships and related transactions, description of securities, and the financial statements with their accompanying notes. SB-1 disclosures are scaled relative to Form S-1, reflecting the small-business issuer regime. Pagination is generally rendered inline in the HTML through <p>Page N</p> markers rather than via PDF-style page breaks.
Exhibit index — an enumerated index of exhibits associated with the registration, such as articles of incorporation, bylaws, opinions of counsel, subscription agreements, advertising agreements, and consents. The index references the exhibits, but the exhibit files themselves are typically incorporated by reference to the parent SB-1 filing rather than re-filed inside the MEF submission.
Signatures page — a SIGNATURES heading, followed by the registrant's certification that it "has reasonable grounds to believe that it meets all the requirements of filing on Form SB-1," followed by the city, state, and date of execution, followed by /s/-style signature blocks for the registrant's authorized officers and directors. Officer signatures typically include the principal executive officer, principal financial officer, principal accounting officer, and a majority of the directors; small issuers commonly satisfy this through a small number of overlapping signatories.
The companion PDF document is a separate EDGAR-submitted rendition of the same registration statement intended for human reading. It is byte-for-byte distinct from the HTML and is not a parseable mirror; the HTML remains the canonical machine-readable source.
Each record includes the structured metadata.json, the primary SB-1MEF registration-statement HTML carrying the EDGAR SGML document envelope, and any non-image rendition documents the filer submitted, most commonly a PDF version of the same registration statement. Document filenames are preserved verbatim from the EDGAR submission: typically lowercase, often issuer- or counsel-derived, and frequently encoding a Rule 462(b) reference in the filename stem. The HTML and PDF for a given filing usually share a base name because they are two renditions of the same document.
Image attachments referenced from the EDGAR submission are excluded by design. Sequence numbers in documentFormatFiles[] will accordingly contain gaps where image files used to sit, and consumers iterating that array should not assume every listed entry has a corresponding file on disk. The wrapping complete-submission .txt SGML file is referenced by URL through linkToTxt and through a trailing entry in documentFormatFiles[], but it is not unpacked into the per-accession folder. Exhibit files that the SB-1MEF cover incorporates by reference to the parent SB-1 registration are not bundled into the MEF record itself; they live with the parent filing's accession.
Form SB-1MEF had an unusually short and stable operational life. It became available on EDGAR in November 2001 and was discontinued, alongside Form SB-1 and the rest of the Regulation S-B form suite, on the effective date of the SEC's 2008 rulemaking that eliminated Regulation S-B and integrated smaller reporting companies into the Regulation S-K disclosure regime, with the last filings landing in August 2008. Within that 2001-11 to 2008-08 window the form's required content did not undergo substantial structural change: the Rule 462(b) checkbox, the Calculation of Registration Fee table, the cross-reference to the parent SB-1 file number, and the executed signatures page were the constant load-bearing elements. After the 2008 elimination, issuers seeking the same 20%-incremental-registration mechanic for a small-business offering migrated to Form S-1MEF under the consolidated Regulation S-K framework. Records in this dataset are therefore confined to a fixed historical window with an essentially fixed content template.
SB-1MEF was filed entirely in the post-ASCII era of EDGAR. Filings are delivered as HTML inside the standard EDGAR SGML <DOCUMENT> envelope, frequently accompanied by a PDF rendition of the same registration statement. The form predates the XBRL and inline-XBRL tagging mandates that later applied to registration-statement disclosures, and linkToXbrl is consistently empty across the dataset. No structured-data attachments accompany these filings, so dataFiles[] is empty as well. Across the 2001-11 to 2008-08 lifespan, the document-format conventions for SB-1MEF — SGML-wrapped HTML for the primary registration statement plus an optional PDF mirror — were stable and did not pass through additional format eras.
Several nuances matter for correctly interpreting an SB-1MEF record:
The cover does not say "SB-1MEF". The document body's cover reads FORM SB-1. The MEF nature is captured exclusively by the 462(b) checkbox election plus the parent file number on the cover, together with the EDGAR submission-level formType and the document-level type fields in metadata.json. Code or readers expecting an "SB-1MEF" heading inside the prospectus will not find one.
Two distinct file numbers coexist in a record. The current filing's own EDGAR file number is surfaced through entities[].fileNo in the metadata. The parent SB-1 file number appears only on the document cover next to the 462(b) checkbox. Linking an MEF back to its parent registration requires the parent file number — not the metadata-level file number, and not the accession number.
The Calculation of Registration Fee table is the canonical source for incremental securities. Consumers extracting offering-size data should parse the registration-fee table from the HTML rather than relying on metadata fields, which do not surface share counts, prices, or fees.
Sequence-number gaps are expected. Both because images are excluded from the on-disk payload and because the trailing complete-submission entry has no corresponding file, documentFormatFiles[] will not be a contiguous run of sequence numbers terminating at a file on disk.
Exhibit content is generally outside the record. Exhibits are typically incorporated by reference from the parent SB-1 and are not bundled into the MEF record; the MEF's exhibit index lists them but does not carry them.
The dataset population is small by construction. Form SB-1 was rarely used, the 462(b) MEF variant rarer still, and the 2008 elimination of Regulation S-B capped the population permanently. A consumer of this dataset is iterating a handful of historical records rather than streaming a high-volume corpus.
The filer is always the small business issuer that already has an effective Form SB-1 registration statement under the Securities Act of 1933. There are no underwriter, selling-shareholder, or third-party filers; the registrant on Form SB-1MEF is the same issuer named on the parent SB-1.
Eligibility flows from Regulation S-B (17 C.F.R. Part 228), the SEC's pre-2008 scaled disclosure regime. To qualify as a "small business issuer" under Item 10 of Reg S-B, the registrant had to:
Form SB-1 added a further ceiling: aggregate cash offerings by the issuer and its affiliates over any rolling 12 months could not exceed $10 million. Issuers above any of these thresholds used Form S-1 or Form SB-2 and, for last-minute upsizing, Form S-1MEF or SB-2MEF rather than SB-1MEF.
Foreign private issuers outside the U.S./Canada window, registered investment companies, asset-backed issuers, and business development companies were not eligible for Form SB-1 and therefore could not file SB-1MEF.
Form SB-1MEF is event-driven, not periodic. It is filed when an issuer with an effective SB-1 decides at or near pricing to register additional securities of the same class, capped at 20 percent of the original maximum aggregate offering price. The cap is measured on dollar value, not on share count, so the incremental share number can differ from a strict 20 percent if the pricing has moved.
Concrete trigger conditions under Rule 462(b):
The filing becomes effective automatically upon filing, without staff review or a separate order. This immediate-effectiveness mechanic is the entire reason the form exists: when book-building reveals demand above the registered amount, the issuer can register the incremental dollars in minutes and proceed to pricing.
The governing statute is Section 5 of the Securities Act of 1933. Rule 462(b), adopted by the SEC in 1996 (Securities Act Release No. 33-7300), authorizes the abbreviated registration statement that "matures effective" on filing; the "MEF" suffix denotes that mechanism. SB-1MEF is the Rule 462(b) companion to Form SB-1.
Form SB-1 itself sat under Regulation S-B, the SEC's integrated small-business disclosure regime adopted in 1992. SB-1MEF inherits the Reg S-B disclosure content by reference: the MEF document is a short cover-page-style filing that incorporates the parent registration statement, identifies the additional securities, and recalculates the fee.
Signature requirements derive from Section 6(a) of the Securities Act and are not relaxed by Rule 462(b). The SB-1MEF must be signed by:
Officers may sign for directors only under a valid power of attorney filed as an exhibit. Underwriters and selling shareholders, though economically central to the upsizing, are not signatories.
There is no pre-EDGAR paper history relevant to this dataset; by the time Rule 462(b) existed, EDGAR was already mandatory for this filer population.
Form SB-1MEF sits at the intersection of three filing concepts: small-business issuer registration under the now-retired Regulation S-B regime, Rule 462(b) immediate-effectiveness upsize filings, and Securities Act registration statements. Its identity is defined by four simultaneous constraints: (1) small-business issuer eligibility under Reg S-B, (2) an SB-1 parent capped at $10M per rolling 12 months, (3) a 20% additional-securities ceiling under Rule 462(b), and (4) a closed November 2001 — August 2008 window. The comparisons below position SB-1MEF against the neighbors most likely to be confused with it.
SB-1 is the long-form small-business registration statement carrying the full prospectus, audited financials, risk factors, and management disclosures. SB-1MEF cannot exist without an effective SB-1 and contains only issuer identification, the prior file number, the additional amount registered, the fee calculation, and signatures. SB-1 is the substantive disclosure record; SB-1MEF is a mechanical 20% upsize that incorporates SB-1 by reference. Not interchangeable.
SB-2 was the other Reg S-B registration form, available to the same small-business issuer population but without the $10M / 12-month ceiling. SB-2MEF is the structurally identical 462(b) sibling to SB-1MEF, sharing filing mechanics, immediate effectiveness, the 20% cap, and the August 2008 sunset. The only distinction is the parent: SB-1MEF rides on a ceilinged SB-1; SB-2MEF rides on an uncapped SB-2. Because SB-2 was the more commonly used parent, any study of small-business 462(b) upsize behavior that relies on SB-1MEF alone will materially undercount the population.
S-1 is the general long-form registration statement with no small-business ceiling; S-1MEF is its 462(b) upsize variant. S-1MEF is mechanically identical to SB-1MEF (20% cap, immediate effectiveness, abbreviated content) but applies to a non-small-business filer population, including IPO issuers registering additional shares on pricing day. After Reg S-B was eliminated in 2008, the SB-1MEF use case migrated into S-1MEF filings made by smaller reporting companies using scaled S-K disclosure. S-1MEF is the natural post-2008 successor for continuity studies, but it is not filterable to the pre-2008 small-business population without external issuer-size data.
Form F-1 / F-1MEF is the foreign private issuer track. Mechanics are identical to SB-1MEF, but the issuer universe is essentially non-overlapping: foreign private issuers rather than domestic small-business issuers. Not a substitute.
Form S-3MEF shares only the Rule 462(b) plumbing and addresses the opposite end of the issuer spectrum: seasoned reporting companies upsizing shelf or primary takedowns. S-3MEF remains active and is far more common; SB-1MEF is closed and rare.
Form 424B filings deliver the prospectus supplements and pricing terms under Rule 424 after effectiveness and frequently follow an MEF on pricing day. They overlap in timing but not in legal function: 424B does not register securities. A complete picture of an upsized small-business offering typically requires the SB-1, the SB-1MEF, and the corresponding 424B.
Post-effective amendments modify or correct disclosure in an existing registration but do not register additional securities under Rule 462(b) and generally require staff action rather than becoming effective on filing. They share the small-business universe and historical window with SB-1MEF but lack both the 20% upsize purpose and the immediate-effectiveness mechanic.
The MEF family — S-1MEF, S-3MEF, Form S-11MEF, F-1MEF, Form F-3MEF, SB-1MEF, SB-2MEF — shares the 20% cap, the requirement of an effective parent, and immediate effectiveness on filing. SB-1MEF is the smallest and rarest member. Research on 462(b) usage broadly requires combining the full family; SB-1MEF alone is insufficient.
In August 2008 the SEC eliminated Reg S-B (Forms SB-1, SB-2, Form 10-KSB, Form 10-QSB) and folded the small-business framework into the smaller-reporting-company category within Regulation S-K. SB-1 issuers migrated to S-1 with scaled SRC disclosure, and their 462(b) upsizes migrated to S-1MEF. SB-1MEF therefore covers a closed window with no active successor under the same form code. Longitudinal studies must bridge the regime change by joining SB-1MEF and SB-2MEF (pre-2008) with the SRC subset of S-1MEF (post-2008).
No other dataset combines all four defining constraints of SB-1MEF: Reg S-B small-business eligibility, an SB-1 parent with the $10M / 12-month cap, the Rule 462(b) 20% upsize ceiling, and the November 2001 — August 2008 window. SB-2MEF lifts the SB-1 size cap; S-1MEF and S-3MEF apply to non-small-business issuers; F-1MEF covers foreign private issuers; post-effective amendments to SB-1 lack the 462(b) mechanic; the post-2008 SRC regime lacks the form code. Because of this narrow definition, SB-1MEF is small, closed, and not substitutable by any single neighbor; it is most useful in combination with SB-1 (substantive disclosure), SB-2MEF (broader Reg S-B 462(b) picture), and 424B (delivered offering terms).
Users of the Form SB-1MEF Files Dataset are concentrated in legal, regulatory-history, audit, diligence, and academic functions where completeness of the EDGAR record matters more than filing volume. The dataset is treated as a closed reference covering the entire November 2001 — August 2008 SB-1MEF window, retired alongside Regulation S-B, rather than as a live feed.
Capital-markets counsel reconstruct how the retired SB-1 / SB-1MEF pairing was used in practice. They mine the cover page, the Rule 462(b) fee calculation table, the title and amount of additional securities, and the parent SB-1 file-number cross-reference to build drafting precedent and internal memos comparing 462(b) usage across SB-1, S-1, and F-1 contexts.
Scholars writing on the evolution of scaled disclosure cite the actual filings rather than summary statistics. They use the full registration statement text, issuer identifiers, parent file number, and effective date as primary-source material for law-review articles and dissertations on small-issuer disclosure.
Analysts documenting Reg S-B's 2008 repeal use the dataset to quantify SB-1MEF uptake. The small filing population over seven years is itself the finding. Filing dates, issuer identifiers, and offering-size fields support policy retrospectives and reference material for ongoing scaled-disclosure rulemaking.
Teams mirroring EDGAR or maintaining form-type catalogs need every code represented, including rare obsolete ones. They consume the metadata file, accession numbers, document manifest, and file-type mix (HTML, PDF, JSON) to populate registries, build parser test fixtures, and validate form-type taxonomies.
Researchers studying post-dot-com micro-cap offerings cross-reference SB-1MEF against the parent SB-1 and subsequent periodic reports to trace capital-raise trajectories. They focus on issuer name, additional securities registered, the fee table, and the immediate effectiveness date.
Registration-tracking staff reconcile historical filing chains for long-tail issuers and successors. They confirm the abbreviated filing references the correct parent SB-1 file number, that the upsize stays within the 20 percent Rule 462(b) limit, and that signatures match authorized officers.
Assurance teams on engagements reaching the pre-2008 period verify share counts and proceeds tied to a 462(b) upsize. The title and amount of additional securities plus the registration fee table feed reconciliation of historical share issuances against capital-raise records and share registers.
Diligence staff reviewing acquisition targets, successor entities, or shells with long histories validate every registration in the target's chain. When an SB-1 was upsized via SB-1MEF, they pull the parent cross-reference, upsize amount, fee calculation, and signature page to confirm the final registered offering size.
Empirical researchers building datasets on abbreviated registration usage and scaled-disclosure outcomes include SB-1MEF as one categorical variable. Inclusion preserves complete coverage of the 462(b) family across issuer-size regimes. They consume the structured metadata and offering-size fields.
The metadata file, registration fee table, parent SB-1 cross-reference, 20 percent upsize amount, and signature page carry most of the dataset's analytical weight across these user groups.
The dataset functions as a citable historical reference for the retired Regulation S-B regime rather than as a live analytics feed. The use cases below reflect that orientation.
Reconstruct the registration chain for a small-business issuer by reading the Rule 462(b) checkbox and the 333-XXXXX parent SB-1 file number from the registration-statement HTML cover, then joining that file number against the SB-1 corpus to recover the substantive prospectus, risk factors, and audited financials. Useful for diligence on legacy issuers, successor entities, and shells whose pre-2008 capital-raise history needs to be reassembled.
Parse the Calculation of Registration Fee table from the primary HTML to extract the title of each class, amount registered, maximum aggregate offering price, and fee paid. Auditors and forensic accountants working back through pre-2008 share registers use these values to reconcile registered share counts against issued-and-outstanding records, and to confirm the upsize stays within the Rule 462(b) 20% ceiling.
Use the filings as worked examples in CLE materials, securities-law courses, and internal training decks covering scaled disclosure before its 2008 repeal. The dataset offers the full primary-source pairing — cover page election, fee table, signatures — that lets students see how a 462(b) upsize layered onto an SB-1 in practice, rather than relying on a textbook summary.
Populate form-type taxonomies, parser test fixtures, and EDGAR mirror catalogs with a real SB-1MEF accession so that rare obsolete codes are represented end-to-end. Engineers consume metadata.json, the dashed accession number, the documentFormatFiles[] manifest with its image-stripped sequence gaps, and the SGML <DOCUMENT> envelope to validate that downstream pipelines accept the form code without error.
Cite specific filings as primary-source evidence in law-review articles, dissertations, and policy retrospectives on the evolution of small-business registration and the 2008 elimination of Regulation S-B. The closed seven-year SB-1MEF population is itself a quantitative finding for analyses of SB-1MEF uptake; the dataset supplies the citable accession numbers, filing dates, issuer identifiers, and document URLs.
When a target's history reaches into the pre-2008 small-business regime, diligence teams pull the SB-1MEF record to verify the additional securities registered, the parent file number, and the executed signature block against the registrant's authorized officers and directors. The output feeds capital-structure schedules, representation letters, and the final registered-offering-size figure attached to the deal data room.
The Form SB-1MEF Files Dataset is available through three access methods: a JSON metadata API, a full dataset archive, and individual container downloads. Authentication is performed with your SEC API key, passed as the token query parameter on the download endpoints.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-sb1mef-files.json
This endpoint returns metadata describing the dataset and the list of available containers. The response includes the dataset name, description, last updated timestamp, earliest sample date, total records and total size, form types covered, container format, and file types included. It also lists every container with its key, size, record count, last updated timestamp, and direct download URL. This endpoint does not require an API key and can be polled to detect which containers were modified during the most recent refresh, so only changed containers need to be re-downloaded.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-6a9d-9ea1-34a596bc07bb",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-sb1mef-files.zip",
4
"name": "Form SB-1MEF Files Dataset",
5
"updatedAt": "2026-04-16T09:05:34.939Z",
6
"earliestSampleDate": "2001-11-01",
7
"totalRecords": 2,
8
"totalSize": 305554,
9
"formTypes": ["SB-1MEF"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["HTML", "PDF", "JSON"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-sb1mef-files/2001/2001-11.zip",
15
"key": "2001/2001-11.zip",
16
"size": 305554,
17
"records": 2,
18
"updatedAt": "2026-04-16T09:05:34.939Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-sb1mef-files.zip?token=YOUR_API_KEY
This endpoint streams the complete dataset as a single ZIP archive containing every monthly container. Because the dataset covers a discontinued form with filings from November 2001 through August 2008, the full archive is small and suitable for a one-time bulk download. This endpoint requires an API key.
Download Single Container: https://api.sec-api.io/datasets/form-sb1mef-files/2001/2001-11.zip?token=YOUR_API_KEY
Individual monthly containers can be downloaded directly using the downloadUrl returned by the index API. Each container is a ZIP archive grouping all filings for a given month, with one folder per accession number containing the filing's metadata JSON and original EDGAR documents. This endpoint requires an API key.
The dataset covers Form SB-1MEF, the abbreviated registration statement filed under Rule 462(b) of the Securities Act of 1933 by small-business issuers to register up to 20% in additional securities on top of an already-effective Form SB-1. The dataset includes only the SB-1MEF form code; SB-1MEF/A and other amendment tags are separate EDGAR form types and are not part of this dataset.
One record is a single EDGAR submission of Form SB-1MEF, identified by its 18-digit accession number and packaged as a per-accession folder inside a year-month ZIP container. Each record bundles a structured metadata.json describing the submission together with the original EDGAR-submitted documents — typically the registration-statement HTML and a PDF rendition — with image attachments stripped.
The filer is always the small-business issuer that already has an effective parent Form SB-1. The issuer must qualify under Regulation S-B as a U.S. or Canadian non-investment-company issuer with annual revenues and public float each below $25 million, and the parent SB-1 itself was capped at $10 million in aggregate cash offerings by the issuer and its affiliates over any rolling 12 months. Underwriters, selling shareholders, and other third parties never file SB-1MEF.
The dataset covers the entire operational life of Form SB-1MEF on EDGAR, from the earliest sample on 2001-11-01 through August 2008, when the SEC's repeal of Regulation S-B (Release No. 33-8876) eliminated the form alongside the rest of the Reg S-B suite. There is no active successor under the same form code; the post-2008 use case migrated to Form S-1MEF under the smaller-reporting-company framework in Regulation S-K.
The dataset is distributed as ZIP containers organized by year-month (for example, 2001/2001-11.zip). Inside each container, every accession is a folder containing a metadata.json plus the original EDGAR documents, with file types limited to HTML, PDF, and JSON. Image attachments referenced from the EDGAR submission are excluded by design, which produces gaps in the documentFormatFiles[] sequence numbers.
SB-2MEF is the structurally identical 462(b) sibling that rides on a Form SB-2 parent rather than an SB-1; SB-2 lacked the SB-1's $10 million 12-month cash-offering ceiling, so SB-2MEF was the more commonly used small-business 462(b) upsize. S-1MEF applies to non-small-business issuers under Form S-1 and remains the post-2008 successor for the small-business use case once Regulation S-B was eliminated, but it cannot be filtered to the pre-2008 small-business population without external issuer-size data.
The link is the parent SB-1 Securities Act file number — typically expressed as File Number 333-XXXXX — that appears on the document cover next to the Rule 462(b) checkbox. This is distinct from entities[].fileNo in metadata.json, which carries the EDGAR-assigned file number of the current SB-1MEF, and from the accession number. Linking an SB-1MEF back to its parent registration requires the parent file number on the cover, not the metadata-level file number.