# SEC EDGAR Regulation A Offerings (`darthdimus/sec-edgar-regulation-a-offerings`) Actor

Structured Regulation A (Form 1-A) offering data from official SEC quarterly Regulation A data sets (submission + issuer + summary joined). Not Form D, Form C, Form ADV, filing lists, ticker maps, company profiles, XBRL company-facts/frames, Form 4, 13F, indexes, or EFTS.

- **URL**: https://apify.com/darthdimus/sec-edgar-regulation-a-offerings.md
- **Developed by:** [Dmitry Ostrovsky](https://apify.com/darthdimus) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## SEC EDGAR Regulation A Offerings

Apify Actor that downloads an official SEC **Regulation A (Form 1-A) quarterly data set** ZIP and returns structured offering rows: submission + issuer info + offering summary joined on accession number.

Data source index: https://www.sec.gov/data-research/sec-markets-data/regulation-data-sets

ZIP paths (tried in order):

- `https://www.sec.gov/files/datastandardsinnovation/data/regulation-data-sets/{yyyy}q{n}_rega.zip`
- `https://www.sec.gov/files/structureddata/data/regulation-data-sets/{yyyy}q{n}_rega.zip`
- `https://www.sec.gov/files/dera/data/regulation-data-sets/{yyyy}q{n}_rega.zip`

Distinct from:

- SEC EDGAR Form D Offerings (Reg D / Form D exempt offerings)
- SEC EDGAR Crowdfunding Offerings (Regulation Crowdfunding / Form C)
- SEC Form ADV Registered Advisers
- SEC EDGAR Recent Filings / Current Filings / Daily Index / Filing Documents
- SEC EDGAR Company Tickers / Mutual Fund Tickers
- SEC EDGAR Company Profile
- SEC EDGAR Company Facts / XBRL Frames
- SEC EDGAR Full-Text Search (EFTS)
- SEC EDGAR Insider Transactions / 13F Holdings

Legal public data only. No Playwright. Limited-permission Actor. Standby is off.

### Input

- `quarter` (string, required): e.g. `2026Q2` or `2026q2`
- `maxOfferings` (integer, default 25, max 200)
- `cik` (optional string): issuer CIK filter
- `nameContains` (optional string): substring on issuer name (from securities-issued name)
- `submissionTypeContains` (optional string): substring on SUBMISSIONTYPE; when omitted, only `1-A` / `1-A/A` / `1-A POS` (excludes `1-K` / `1-Z`)
- `tier` (optional string): exact match on Tier1 / Tier2
- `stateOrCountry` (optional string): exact match on issuer STATEORCOUNTRY

### Output

One dataset item per Form 1-A offering: accessionNumber, submissionType, filingDate, cik, file numbers, issuer address/industry/financial snapshot fields, tier, audit status, offering size/price fields, securitiesOfferedTypes, service-provider names, quarter, sourceUrl.

Jurisdiction, signature, employees, equities/debt detail, and Item K/Z tables are **not** dumped into every row. Issuer display name prefers `REG_A_SECURITIES_ISSUED.SECURITIESISSUERNAME` when present.

### SEC User-Agent

SEC fair-access rules require a User-Agent with a contact. This Actor reads `SEC_USER_AGENT` and defaults to `sec-edgar-regulation-a-offerings (dostrovsky@gmail.com)`.

Docs: https://www.sec.gov/os/accessing-edgar-data

# Actor input Schema

## `quarter` (type: `string`):

Calendar quarter for the Regulation A data set, e.g. 2026Q2 or 2026q2.

## `maxOfferings` (type: `integer`):

Maximum offering rows to push (1–200).

## `cik` (type: `string`):

Optional. Only rows whose issuer CIK matches (digits, with or without leading zeros).

## `nameContains` (type: `string`):

Optional. Case-insensitive substring match on issuer name (from securities-issued name when present).

## `submissionTypeContains` (type: `string`):

Optional. Case-insensitive substring match on SUBMISSIONTYPE (e.g. 1-A, 1-A/A, 1-A POS). When omitted, only Form 1-A offering types (1-A, 1-A/A, 1-A POS) are included; 1-K / 1-Z reports are excluded.

## `tier` (type: `string`):

Optional. Exact match (case-insensitive) on INDICATETIER1TIER2OFFERING (e.g. Tier1, Tier2).

## `stateOrCountry` (type: `string`):

Optional. Exact match (case-insensitive) on issuer STATEORCOUNTRY.

## Actor input object example

```json
{
  "quarter": "2026Q2",
  "maxOfferings": 25
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "quarter": "2026Q2"
};

// Run the Actor and wait for it to finish
const run = await client.actor("darthdimus/sec-edgar-regulation-a-offerings").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "quarter": "2026Q2" }

# Run the Actor and wait for it to finish
run = client.actor("darthdimus/sec-edgar-regulation-a-offerings").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "quarter": "2026Q2"
}' |
apify call darthdimus/sec-edgar-regulation-a-offerings --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,darthdimus/sec-edgar-regulation-a-offerings"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ag9GvNGWegwtpvjlo/builds/8D2FhIauwj3z4afY5/openapi.json