The Form 10SB12G Files Dataset is a complete, bounded corpus of every Form 10-SB registration statement and amendment filed on EDGAR under the form-type codes 10SB12G and 10SB12G/A — the initial general registration of a class of equity securities by a small business issuer under Section 12(g) of the Securities Exchange Act of 1934. Each record is one EDGAR submission, identified by its 18-digit SEC accession number and packaged as a folder containing a metadata.json manifest plus every document the registrant attached to the original submission, with the sole exclusion of binary image attachments. The legal filer is always the issuer itself, acting as registrant under Regulation S-B (17 CFR 228). The dataset spans the full life of the form on EDGAR — from May 1996 through the SEC's discontinuation of Form 10-SB on February 4, 2008 — and is distributed as a single dataset-level ZIP plus a parallel set of monthly ZIP archives organized by year. File payloads inside each record include TXT, JSON, HTML, PDF, and XFD content.
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 EDGAR submissions whose form-type code is 10SB12G (an initial Section 12(g) class registration filed by a small business issuer) or 10SB12G/A (an amendment to such a registration). Form 10-SB itself was the general form for the registration of a class of securities under Section 12(g) of the Exchange Act, restricted to issuers qualifying as "small business issuers" under Regulation S-B. Filing it caused the issuer to become a reporting company subject to the Exchange Act's periodic disclosure regime (Forms 10-KSB, 10-QSB, 8-K). The form-type code 10SB12G denotes a Section 12(g) registration, distinct from 10SB12B, which was used for registrations tied to listing on a national securities exchange. The 10SB12G/A code is reserved for amendments, commonly filed to respond to SEC staff comments, correct deficiencies in financial statements or business descriptions, or add late-arriving exhibits.
The body of the registration statement is governed by the items of Regulation S-B and is organized around: a description of the issuer's business; properties; legal proceedings; market for and security holders of the registrant's common equity; management's discussion and analysis of financial condition and plan of operations (MD&A or, for issuers with fewer than two fiscal years of operating revenue, a "plan of operation"); audited financial statements (balance sheets and statements of operations, cash flows, and stockholders' equity, with notes); directors, executive officers, promoters, and control persons; executive compensation; security ownership of certain beneficial owners and management; certain relationships and related transactions; description of securities; and recent sales of unregistered securities. The form closes with an index to exhibits and a signature page executed by the registrant and a majority of the board of directors.
The dataset is distributed as a single dataset-level ZIP (form-10sb12g-files.zip) and a parallel set of monthly ZIP archives organized by year, e.g. 2008/2008-02.zip, 2007/2007-11.zip. Within each monthly ZIP, every record is a sub-folder whose name is the accession number rendered as 18 contiguous digits with the dashes removed (for example, accession 0001185185-08-000067 appears as a folder named 000118518508000067). The folder boundary is the record boundary: everything that belongs to one EDGAR submission lives inside that one folder, and nothing else does. The file types found across the dataset are TXT, JSON, HTML, PDF, and XFD. From roughly 2002 onward HTML predominates for the primary form and exhibits; JSON is the manifest; PDF, XFD, and plain text persist in earlier filings or for individual exhibits the filer chose to submit in those formats.
Each accession folder contains exactly one metadata.json plus the original EDGAR documents that constituted the submission, minus images. Component documents preserve their original EDGAR filenames and retain the SGML <DOCUMENT> wrapper that EDGAR adds in complete-submission bundles. A typical operating-company 10SB12G filing contains a primary registration document (e.g. vemics10sb12g-1182008.htm), a charter exhibit (ex3-1.htm), a bylaws exhibit (ex3-2.htm), one or more material-contract exhibits (ex10-1.htm through ex10-9.htm), and a subsidiaries-list exhibit (ex21-1.htm). Shell-company registrations often consist of nothing more than the primary form, the certificate of incorporation, and the bylaws.
metadata.json fieldsThe manifest is a single JSON object describing the submission at three levels: the filing as a whole, the filer entity (or entities), and each component document. Principal fields:
formType — one of 10SB12G or 10SB12G/A.accessionNo — the canonical SEC accession number with dashes (NNNNNNNNNN-YY-NNNNNN).filedAt — ISO-8601 acceptance timestamp with timezone offset (e.g. 2008-02-01T16:48:07-05:00).description — human-readable form title, e.g. Form 10SB12G - Registration of securities for small business [Section 12(g)], with [Amend] appended for 10SB12G/A records.linkToFilingDetails — absolute URL on sec.gov/Archives/edgar/... pointing at the primary filing document.linkToTxt — absolute URL of the consolidated complete-submission .txt bundle on EDGAR.linkToHtml — absolute URL of the EDGAR filing-index page.linkToXbrl — empty across this form; the XBRL/iXBRL mandate did not extend to small business issuers using Form 10-SB before the form was discontinued.id — 32-character hexadecimal identifier used to deduplicate records.documentFormatFiles — array describing every document attached to the submission. Each element carries sequence (1-based ordinal as a string), documentUrl (absolute EDGAR URL), type (SEC document-type code such as 10SB12G, EX-3.1, EX-10.1, EX-21, CORRESP, GRAPHIC), size (byte size as a string), and an optional free-form description (e.g., FORM 10-SB, BY-LAWS, Complete submission text file). A trailing pseudo-entry whose sequence is a single space and whose description is Complete submission text file always points at the consolidated .txt bundle on EDGAR; no on-disk file inside the record folder corresponds to it.dataFiles — array reserved for structured data files (XBRL); empty for 10SB12G filings.entities — array of one or more filer entity objects. Each entity carries companyName (with a role suffix such as (Filer)), cik (10-digit zero-padded Central Index Key), irsNo (IRS Employer Identification Number, often 000000000 when not disclosed), fileNo (SEC-assigned file number), filmNo (EDGAR film/document control number), type (mirroring the top-level form type), act (34 for the Exchange Act), sic (Standard Industrial Classification code with descriptive label, e.g. 4899 Communications Services, NEC), stateOfIncorporation (two-letter US state or country code), fiscalYearEnd (four-digit MMDD), and tickers (array of ticker symbols when the issuer has any; many 10-SB filers are pre-listing shells with none).Every component document is preserved exactly as EDGAR delivered it inside the complete-submission bundle, retaining the SGML <DOCUMENT> wrapper. The wrapper opens with <DOCUMENT> followed by header tags — <TYPE> (the SEC document-type code), <SEQUENCE> (matching the ordinal in the manifest), <FILENAME> (original on-disk name), and an optional <DESCRIPTION> line — then a <TEXT> block containing the payload, terminated by </TEXT> and </DOCUMENT>. Inside <TEXT> the payload is one of:
These header tags are line-oriented and are not closed individually; only <TEXT> and <DOCUMENT> carry explicit closing tags. Consumers that want pure HTML or pure text payloads must strip the wrapper and, for binary types, base64-decode the body. Image attachments referenced via GRAPHIC document-type entries are listed in metadata.json but their binary payload is not stored on disk; the EDGAR URLs in documentUrl remain reachable for retrieval.
Within documentFormatFiles, the SEC document-type vocabulary that recurs across 10SB12G submissions is concrete and limited. The primary document carries type: 10SB12G (or 10SB12G/A on amendments) and is the body of the Form 10-SB registration statement. Recurring exhibits, drawn from the Regulation S-B exhibit table at 17 CFR 228.601, include:
EX-2, EX-2.1 — plan of acquisition, reorganization, arrangement, liquidation, or succession.EX-3.1 — articles or certificate of incorporation (or charter).EX-3.2 — bylaws.EX-4 — instruments defining the rights of security holders, including specimens of stock certificates and warrant agreements.EX-10, EX-10.1 ... EX-10.n — material contracts: employment agreements, joint-venture and licensing agreements, leases, lock-up agreements, promissory notes, share-exchange agreements.EX-21 — subsidiaries of the registrant.EX-23 — consent of independent accountants/auditors to the inclusion of audited financial statements.EX-27 — the Financial Data Schedule, a structured tag-value numeric summary required of small business issuers in the late 1990s and rescinded in 2001.EX-99 — additional exhibits, frequently used for press releases, supplemental risk factors, or financial statements of acquired businesses.CORRESP — correspondence to or from the SEC staff, typically cover letters and responses to comment letters.GRAPHIC — image attachments referenced from the body or exhibits; manifest-only in this dataset.The primary 10SB12G document follows the item-based structure prescribed by Regulation S-B and offers two alternative disclosure models on the cover page (Alternative 1, modeled on Form 10; Alternative 2, modeled on Form S-1/SB-2 narrative). The body is organized as Part I (registrant information) and Part II (exhibits and signatures). Substantive items include: business description (operations, products and services, competition, employees, government regulation, history); plan of operation or MD&A (depending on whether the issuer has had revenues from operations for fewer than two fiscal years); description of property; security ownership of beneficial owners and management; directors, executive officers, promoters, and control persons; executive compensation; certain relationships and related transactions; description of securities; market for common equity and related stockholder matters; legal proceedings; recent sales of unregistered securities; indemnification of directors and officers; the audited financial statements (balance sheets as of the end of the two most recent fiscal years and statements of operations, cash flows, and stockholders' equity for each of the two most recent fiscal years), with notes; changes in and disagreements with accountants; the index to exhibits; and signatures. Smaller filings present these as continuous narrative under item headers; larger filings paginate the body with a table of contents and embed tabular financial schedules.
Included in the on-disk folder: the metadata.json manifest, the primary registration document, every exhibit attached to the submission (charter, bylaws, material contracts, subsidiaries list, auditor consents, Financial Data Schedules in older years, EX-99 attachments), correspondence (CORRESP) when present, and any plain-text, PDF, or XFD variants the filer attached.
Excluded from the on-disk folder: binary image files (GRAPHIC payloads such as .jpg and .gif). Their entries continue to appear inside metadata.json so the document inventory remains complete and the SEC URLs to the original images remain reachable. The consolidated .txt complete-submission bundle is referenced by URL in linkToTxt and as the trailing pseudo-entry in documentFormatFiles but is not duplicated as a separate file inside the record folder, since its content is already represented by the individual unwrapped documents.
Form 10-SB and Regulation S-B were adopted by the SEC in 1992 to create a streamlined disclosure regime for small business issuers; the EDGAR record for 10SB12G filings begins in May 1996. Several substantive changes shaped the content and exhibit set across the form's life:
EX-27) was a required machine-readable numeric summary embedded in nearly every 10-SB filing through the late 1990s. The SEC rescinded the FDS requirement in 2001, after which EX-27 disappears from the exhibit set and is not replaced with any analogous structured exhibit for small business filers.EX-23) became standard practice as audit firms registered with the PCAOB after 2003 and as comment-letter practice tightened around the inclusion of consents tied to the audited financial statements.10-12G) while applying scaled disclosure under the new "smaller reporting company" definition in Item 10(f) of Regulation S-K. February 2008 is therefore the final month in which 10SB12G and 10SB12G/A records appear on EDGAR.Early 10-SB filings on EDGAR are predominantly plain ASCII text. The form body, financial statements, and most exhibits are delivered as wrapped .txt payloads with tabular content rendered using fixed-width column alignment and dollar-sign columns; binary attachments such as signed contracts appear as base64-encoded PDF or XFD inside the SGML wrapper. HTML adoption accelerated through 1999 and 2000, and from roughly 2002 onward most primary documents and exhibits are filed as .htm files, frequently with embedded inline styling and images referenced as separate GRAPHIC documents. PDF appears throughout the period for scanned exhibits and older signed documents; XFD (FormFlow) is rare and concentrated in early filings.
Several practical points matter when working with these records.
<DOCUMENT> wrapper is part of every on-disk component document. Consumers that want pure HTML or pure text payloads must strip it; for PDF and XFD document types the inner <TEXT> block is base64-encoded and must be decoded.metadata.json entities (for example when a co-registrant is included), but the form type and the body of the registration statement remain singular.10SB12G/A amendments do not necessarily restate the entire registration statement. Some amend only specific items, attach a new auditor consent, or add a previously omitted exhibit, so amendment records can be substantially smaller than the initial filing they amend. Reconstructing the complete amended registration statement requires joining /A records back to the original accession by registrant CIK and SEC file number.documentFormatFiles array always carries one trailing pseudo-entry pointing at the consolidated .txt complete-submission bundle on EDGAR; this is a manifest convention, not an on-disk file in the record folder.GRAPHIC entries are listed in the manifest but their binary payloads are not stored on disk; processes that need image bytes must fetch them from the EDGAR URL in documentUrl.EX-27 Financial Data Schedules in pre-2001 records contain a structured tag-value financial summary that can be parsed independently of the narrative financial statements and is often the cleanest source of headline numbers for that vintage.000- prefix used for Section 12(g) registrations, allowing programmatic separation from 001- exchange-listed filers when the dataset is joined with later periodic reports of the same issuer.Each record in the dataset is a Form 10-SB registration statement, or an amendment to one (10SB12G/A), filed by a small business issuer to register a class of equity securities under Section 12(g) of the Securities Exchange Act of 1934. The legal filer is the issuer itself, acting as registrant. Officers, directors, promoters, control persons, and selling security holders may be described inside the filing but are never the filing party.
Eligibility was limited to issuers meeting the "small business issuer" definition in Item 10(a)(1) of Regulation S-B (17 CFR 228.10(a)(1)), which during 1996 to 2008 required the issuer to:
Issuers above the S-B thresholds used Form 10. Foreign private issuers (other than eligible Canadian issuers) used Form 20-F or, under the MJDS, Form 40-F. Investment companies used the Investment Company Act registration regime, not Form 10-SB.
The trigger is registration of a class of equity securities under Section 12(g) of the Exchange Act. The "12G" suffix in the EDGAR form code identifies the Section 12(g) basis (as opposed to Section 12(b) exchange-listing registration, which used Form 10SB12B).
Section 12(g) registration arose two ways during the dataset period:
Mandatory registration under Rule 12g-1. Section 12(g)(1) requires registration once an issuer crosses statutory size and holder thresholds. The statute set a $1 million asset / 500 record-holder threshold, but Rule 12g-1 (17 CFR 240.12g-1) raised the asset prong administratively. From 1996 through 2008, registration was required when, on the last day of the issuer's fiscal year, total assets exceeded $10 million and a class of equity securities was held of record by 500 or more persons. The issuer then had 120 days after fiscal year end to file the Section 12(g) registration statement.
Voluntary registration. Many filers were below the Rule 12g-1 thresholds and registered voluntarily, typically to enable OTC Bulletin Board quotation (which required current Exchange Act reporting status), satisfy market-maker due diligence under Rule 15c2-11, position the issuer for a future capital raise, or create a reporting shell available for a later reverse merger.
In both cases the trigger is registration of a class of securities, not a sale. Form 10-SB is not an offering document; small business offerings were registered on Form SB-2 under the Securities Act of 1933.
A Form 10-SB becomes effective automatically by operation of Section 12(g)(1) on the 60th day after filing. The SEC does not "declare" Form 10-SB effective. Unless withdrawn, the registration matures into an effective Section 12(g) registration on day 60, after which the issuer is subject to the full Exchange Act regime: annual reports on Form 10-KSB, quarterly reports on Form 10-QSB, current reports on Form 8-K, proxy disclosure under Section 14(a) and Regulation 14A, Section 16 reporting by officers, directors, and 10% holders, and beneficial-ownership reporting under Sections 13(d) and 13(g) by outside holders.
Form 10SB12G/A amendments modify a previously filed Form 10-SB and are not new registrations. They are typically filed before the 60-day mark to respond to SEC staff comments or update disclosure (for example, to refresh financial statements that have aged across a fiscal-period boundary), and occasionally after effectiveness to correct material defects. Amendments do not formally reset the 60-day clock, but issuers commonly time amendments so that the version reaching effectiveness is the staff-reviewed one.
Pre-effectiveness, an issuer may withdraw a Form 10-SB by filing Form RW. Post-effectiveness, the resulting Section 12(g) registration may be suspended under Rule 12g-4 (when holders of record fall below the specified thresholds) or terminated by filing Form 15. Those events are recorded in other filing types and are outside this dataset.
The SEC adopted SEC Release No. 33-8876, "Smaller Reporting Company Regulatory Relief and Simplification," on November 15, 2007, effective February 4, 2008. The release rescinded Regulation S-B and eliminated the SB form set, including Form 10-SB, Form 10-KSB, Form 10-QSB, and Form SB-2. In their place, the Commission created a unified "smaller reporting company" category in Regulation S-K (Item 10(f)) and Rule 12b-2, using a $75 million public float test (with a revenue alternative). After February 4, 2008, small business issuers registering under Section 12(g) used Form 10 (EDGAR code 10-12G). The dataset therefore has a hard right boundary at that effective date; the left boundary reflects the May 1996 EDGAR cutover for Exchange Act registration filings.
Form 10SB12G occupies a narrow intersection: Exchange Act class registration under Section 12(g), filed by small business issuers under the now-defunct Regulation S-B, during the May 1996 to February 2008 window. Adjacent forms either share the trigger, the eligible filer population, or the successor lineage, and are easy to confuse with this dataset.
The non-small-business contemporary of 10SB12G during 1996-2008, and its unified successor after February 2008 when Regulation S-B was eliminated. Same statutory trigger (Section 12(g) class registration: assets and holders of record above threshold, or voluntary entry into reporting). Difference: Form 10 follows Regulation S-K, with fuller risk factors, segment data, and audited financials lacking the S-B accommodations. Post-February 2008, all 12(g) registrations migrate here, with smaller reporting companies receiving scaled S-K disclosure rather than a separate S-B regime. Full historical coverage of 12(g) entries requires both datasets, with the February 2008 cutover.
The listing-track counterparts. The "12B" suffix means the class is registered in connection with listing on a national securities exchange (NYSE, AMEX, post-2006 NASDAQ); "12G" means the class is not exchange-listed but meets the holder/asset thresholds. Disclosure content of 10SB12B and 10SB12G is nearly identical; the only substantive distinction is whether exchange listing accompanies registration. 10SB12B is the small business variant; 10-12B is the general variant. Filers that change listing plans mid-process sometimes re-file across the 12B/12G boundary.
A short-form Section 12 registration (available as 8-A12B or 8-A12G) for issuers that already have an effective Securities Act registration on file. It incorporates the S-1 or SB-2 by reference and contains almost no standalone disclosure. Same registration obligation as 10SB12G, but 8-A is the path for issuers entering Exchange Act reporting on the heels of a registered offering, while 10SB12G is the path for issuers registering a class without a contemporaneous offering. As data, 8-A filings are short reference documents; 10SB12G filings are full narrative and financial disclosures.
The 1933 Act offering-registration statement for small business issuers. Same eligible filer population (Regulation S-B) and same lifecycle (discontinued February 2008), so issuer universe and time window overlap heavily. The legal effect is fundamentally different: SB-2 registers an offering of securities for sale; 10SB12G registers a class of securities to trigger Exchange Act reporting. SB-2 controls what can be sold; 10SB12G controls whether the issuer becomes a reporting company. The same issuer often files both, with overlapping business, financial, and management disclosure but distinct legal effects.
The general-purpose 1933 Act registration statement, not size-restricted, and the post-2008 home for what had been SB-2. Relationship to 10SB12G mirrors SB-2's: different Act (1934 Act vs. 1933), different trigger (offering vs. class registration), broader filer population, fuller S-K disclosure. Pre-2008 small business onset typically pairs SB-2 with 10SB12G; post-2008 onset pairs Form S-1 with Form 10.
The periodic annual reports that follow effective 12(g) registration. 10-KSB was the small business annual report under Regulation S-B, on the same May 1996 to February 2008 lifecycle as 10SB12G; afterward, all annual reports moved to a unified Form 10-K with smaller reporting company scaling. The relationship is sequential, not substitutive: 10SB12G is the one-time entry point, 10-KSB then 10-K is the recurring obligation. Disclosure overlaps in the first annual report after registration, but 10SB12G never recurs.
Form 10SB12G is distinct on four simultaneous axes that no neighboring dataset shares:
Adjacent datasets complement but cannot substitute: 10SB12B for the listing-track variant, SB-2 for the offering side of the same issuer cohort, 8-A for issuers already inside the 1933 Act system, 10-KSB for the periodic disclosures that follow, and Form 10 / 10-12G for both the non-SB peer during the same period and the unified successor afterward.
The dataset captures the full historical population of small-business Section 12(g) registrations from May 1996 through the form's February 2008 discontinuation, a corpus heavily populated by shells, reverse-merger vehicles, and early-stage micro-caps. Different professions read the same record through different lenses: filer metadata (CIK, IRS number, state, SIC, fiscal-year end, address history), 10-SB items (business description, plan of operations, MD&A, officers, compensation, ownership, related-party transactions), exhibits (EX-3 charter, EX-10 contracts, EX-21 subsidiaries, EX-99 schedules), and Regulation S-B audited financials.
Used to reconstruct the early registration history of suspect issuers. Investigators trace CIK continuity, name-change history, IRS employer numbers, and SIC reclassifications in metadata.json to detect pivots from shell to operating status. Within the 10-SB they target "no operations" or "blank check" language in the business description, recurring promoter and nominee names in the directors-and-officers section, concentrated stakes in security-ownership tables, and consulting or stock-purchase agreements in EX-10. Nominal cash-only balance sheets and EX-3 charter amendments serve as core evidence in fraud reconstructions, expert reports, and restitution work.
Treat the corpus as a closed historical population for studies on Regulation S-B disclosure quality, micro-cap going-concern opinions, the 2008 smaller reporting company transition, and shell-company lifecycles. Structured metadata fields (filing date, state, SIC, fiscal-year end) drive sample construction; 10-SB MD&A and risk-factor text supports tone and length analysis; Regulation S-B financials feed small-cap panel datasets; and 10SB12G/A amendment trails support studies of disclosure revision and staff review.
Pull historical registrations relevant to current fraud actions, blue-sky filings, and M&A involving predecessor entities. They rely on EX-3 as originally filed for capital structure baselines, EX-10 for agreements that may still be in force, executive-compensation and related-party items for fiduciary claims, and the audited financials as a baseline for later restatement disputes. Records are produced as litigation exhibits and in document review.
Used when a target, parent, or public-vehicle counterparty has a pre-2008 10-SB history, common in reverse-merger and listing-shell evaluations. Diligence focuses on metadata for CIK and name-change continuity, the original plan of operations for pre-transaction activity, directors-and-officers and ownership sections for legacy control persons, EX-21 for subsidiary perimeter at registration, EX-10 for inherited contractual obligations, and audited financials as a historical anchor for reps-and-warranties scoping.
Extend small-cap fundamentals coverage further back than commercial databases reach for sub-threshold issuers. Analysts parse Regulation S-B statements for revenue, asset, and equity time series, link them through CIK to later 10-KSB and 10-K filings, and use SIC and plan-of-operations text for industry tagging. Ownership and related-party sections feed insider-concentration and governance factors used in micro-cap backtests and screens.
Satisfy historical Rule 15c2-11 information-review obligations on OTC issuers whose initial reporting status came from Form 10-SB. Reviewers verify that metadata, business description, officers list, and audited financials form a complete historical record, that name and SIC changes are documented, and that material-contract and related-party disclosures align with later filings. Output feeds quotation-eligibility files and watch lists for shell-derived tickers.
Study the practical operation of Regulation S-B, the prevalence of blank-check registrants, and the lead-up to the 2008 reforms. They use aggregate metadata distributions (filings per year, state, SIC mix), the textual evolution of disclosure conventions across 1996-2008, and 10SB12G/A amendment patterns to document how the form was used.
Use the dataset as a bounded, complete corpus for the 10-SB form type. metadata.json provides clean identifiers for indexing and entity resolution; primary documents and exhibits supply HTML and TXT content for full-text search and section extraction; and the heterogeneous file-type mix (TXT, HTML, PDF, XFD) stresses parsers against pre-2008 EDGAR formats. Supports exhibit-level extraction, entity graphs linking shells to successor operating companies, and retrieval-augmented generation over historical small-business registrations.
Forensic and legal users mine the dataset for shell and reverse-merger histories; academics and historians treat it as a closed regulatory population; quants and diligence teams extract historical fundamentals and corporate-history anchors; compliance teams build OTC due-diligence files; engineers use it as a bounded corpus. The same components — filer metadata, 10-SB items, EX-3/EX-10/EX-21 exhibits, and Regulation S-B financials — serve each function differently.
The May 1996 to February 2008 small-business 12(g) registration corpus supports a number of concrete workflows that turn the structured manifest, primary 10-SB document, and exhibit set into derived datasets and case files.
Build a chain from a present-day operating company back to its registration as a blank-check or shell company vehicle. Pull all 10SB12G and 10SB12G/A records for a CIK, extract companyName history, prior sic codes, stateOfIncorporation, and fiscalYearEnd shifts from metadata.json, then mine the primary 10-SB business description for "no operations," "shell company," or "seeking suitable acquisition" phrasing and EX-3 charter amendments for share-authorization changes. Output is a per-CIK reverse-merger timeline used in fraud cases, OTC due-diligence files, and reps-and-warranties scoping.
Identify recurring control persons across multiple shell registrations. Parse the directors-and-officers, executive compensation, and security-ownership tables in the primary 10-SB, plus signature blocks, across the full 1996-2008 corpus, normalize names and addresses, and join on CIK. Output is a graph of individuals tied to multiple 10-SB filings, with the per-issuer ownership percentage and tenure attached, used by enforcement attorneys and forensic accountants to flag serial promoter activity.
Recover headline numbers for sub-threshold issuers that pre-date most commercial micro-cap databases. Iterate over pre-2001 records, pull the EX-27 document, parse its tag-value Financial Data Schedule (cash, total assets, total liabilities, revenues, net income, EPS), and key by cik and fiscalYearEnd. Output is a clean panel of small-business issuer fundamentals at registration, linkable to later 10-KSB and 10-K filings for long-horizon micro-cap research.
Capture the corporate-group structure each issuer disclosed at the moment it became a reporting company. Filter documentFormatFiles for type: EX-21, extract subsidiary names and jurisdictions from the exhibit text, and pair with the filer's stateOfIncorporation and sic. Output is a registration-time subsidiary table used in M&A diligence on reverse-merger targets and in academic studies of small-business group structures.
Quantify how small business issuers revised their registration statements in response to SEC staff comments. Group 10SB12G/A records back to their parent 10SB12G by CIK and SEC fileNo, diff the primary document and exhibit set across versions, and join with any CORRESP documents present. Output is a per-issuer revision log (items changed, exhibits added, time between filings) used in research on staff review intensity and in legal work that turns on what was disclosed when.
Assemble a topical contract dataset from the EX-10 series. Walk every record, collect documents whose type matches EX-10 or EX-10.n, strip the SGML <DOCUMENT> wrapper, and classify by description (employment agreement, consulting agreement, stock purchase agreement, promissory note, lock-up). Output is a labeled contract corpus used to train clause-extraction models, to benchmark micro-cap compensation and financing terms, and to surface agreements that may still bind a successor operating company.
Satisfy historical Rule 15c2-11 information review for OTC tickers whose reporting status originated in Form 10-SB. For each in-scope CIK, package the metadata.json, primary 10-SB, EX-3 charter and bylaws, audited financial statements, and EX-23 auditor consent into a per-issuer review file, and flag records with irsNo: 000000000, missing tickers, or shell-language business descriptions. Output is a dossier set that broker-dealer compliance teams attach to quotation files and watch lists for shell-derived securities.
Dataset Index JSON API: https://api.sec-api.io/datasets/form-10sb12g-files.json
This endpoint returns dataset-level metadata together with the list of all monthly containers. The response includes the dataset name, description, last updated timestamp, earliest sample date, total record count, total size, the form types covered (10SB12G and 10SB12G/A), the container format (ZIP), and the file types found inside each container (TXT, JSON, HTML, PDF, XFD). It also includes the full dataset download URL and a containers array, where each entry provides the per-container key, size, records, updatedAt, and downloadUrl. Use this index to enumerate all available monthly containers and to monitor updatedAt values across daily refresh runs to determine which containers have changed and need to be re-downloaded. This endpoint does not require an API key.
Example response:
1
{
2
"datasetId": "1f13365b-9ae0-6932-8987-81a9e98e1dd7",
3
"datasetDownloadUrl": "https://api.sec-api.io/datasets/form-10sb12g-files.zip",
4
"name": "Form 10SB12G Files Dataset",
5
"updatedAt": "2026-04-15T06:10:28.043Z",
6
"earliestSampleDate": "1996-05-01",
7
"totalRecords": 47867,
8
"totalSize": 671205813,
9
"formTypes": ["10SB12G", "10SB12G/A"],
10
"containerFormat": "ZIP",
11
"fileTypes": ["TXT", "JSON", "HTML", "PDF", "XFD"],
12
"containers": [
13
{
14
"downloadUrl": "https://api.sec-api.io/datasets/form-10sb12g-files/2008/2008-02.zip",
15
"key": "2008/2008-02.zip",
16
"size": 4521897,
17
"records": 38,
18
"updatedAt": "2026-04-15T06:10:28.043Z"
19
}
20
]
21
}
Download Entire Dataset: https://api.sec-api.io/datasets/form-10sb12g-files.zip?token=YOUR_API_KEY
Downloads the complete dataset as a single ZIP archive containing every monthly container from May 1996 through February 2008. This endpoint requires authentication via an Authorization header carrying your sec-api.io API key.
Download Single Container: https://api.sec-api.io/datasets/form-10sb12g-files/2008/2008-02.zip?token=YOUR_API_KEY
Downloads one individual monthly container instead of the full archive. Each monthly ZIP contains one subfolder per accession number, holding a metadata.json file and the original EDGAR submission documents for that filing. Container URLs are taken directly from the downloadUrl field of each entry in the dataset index. This endpoint requires authentication via an Authorization header carrying your sec-api.io API key.
The dataset covers Form 10-SB filings on EDGAR under the form-type codes 10SB12G (the initial general registration of a class of equity securities by a small business issuer under Section 12(g) of the Securities Exchange Act of 1934) and 10SB12G/A (amendments to such registrations). It does not include the listing-track variant 10SB12B or the non-small-business 10-12G.
One record is one EDGAR submission, identified by its 18-digit SEC accession number and packaged on disk as a folder containing one metadata.json manifest plus every document the registrant attached to the original submission, with the sole exclusion of binary image attachments (GRAPHIC payloads). Folder names are the accession number with dashes removed (for example, accession 0001185185-08-000067 becomes folder 000118518508000067).
The legal filer is the issuer itself, acting as registrant. Eligibility was limited to "small business issuers" as defined in Item 10(a)(1) of Regulation S-B — broadly, US or Canadian issuers with revenues under $25 million and a public float under $25 million, that are not investment companies and not majority-owned subsidiaries of non-S-B parents. Filings were either mandatory under Rule 12g-1 (total assets over $10 million plus 500 or more record holders at fiscal year end) or voluntary, often to enable OTC Bulletin Board quotation or to position a reporting shell for a later reverse merger.
The dataset spans the full life of the form on EDGAR. The left boundary is May 1996, the EDGAR cutover for Exchange Act registration filings; the right boundary is February 4, 2008, the effective date of SEC Release No. 33-8876, which rescinded Regulation S-B and discontinued Form 10-SB. No new 10SB12G or 10SB12G/A filings exist outside this window.
The dataset is distributed as a single dataset-level ZIP (form-10sb12g-files.zip) and a parallel set of monthly ZIP archives organized by year (e.g. 2008/2008-02.zip). Inside each container, payloads include TXT, JSON, HTML, PDF, and XFD; HTML predominates for primary documents and exhibits from roughly 2002 onward, while plain text dominates earlier filings. Component documents retain the SGML <DOCUMENT> wrapper that EDGAR adds in complete-submission bundles.
Both cover Section 12(g) class registrations, but 10SB12G was reserved for issuers qualifying as small business issuers under Regulation S-B and used scaled S-B disclosure, while 10-12G was used by issuers above the S-B thresholds under Regulation S-K. After February 4, 2008, Regulation S-B was eliminated and all Section 12(g) registrations migrated to Form 10 (10-12G), with smaller reporting companies receiving scaled S-K disclosure rather than a separate S-B regime. Full historical coverage of 12(g) entries therefore requires both datasets, with the February 2008 cutover.
No. The linkToXbrl field in metadata.json is empty across this dataset and the dataFiles array is empty for 10SB12G filings, because the XBRL/iXBRL mandate did not extend to small business issuers using Form 10-SB before the form was discontinued. The closest structured numeric exhibit is EX-27, the Financial Data Schedule, which appears in pre-2001 records and was rescinded in 2001.