# SEC 424B2 Prospectus Supplements Daily Feed (`sourcesauce/sec-424b2-supplements`) Actor

Full-market daily feed of SEC 424B2 prospectus supplements from EDGAR - every shelf-takedown pricing supplement, one deduped record per filing with issuer, co-registrants and document links. Unofficial; not affiliated with the SEC.

- **URL**: https://apify.com/sourcesauce/sec-424b2-supplements.md
- **Developed by:** [Source Sauce](https://apify.com/sourcesauce) (community)
- **Categories:** News, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 424b2 records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## SEC 424B2 Prospectus Supplements Daily Feed

Every **424B2 prospectus supplement** filed with the SEC, the day it lands. Straight from EDGAR
— no third-party data source, no API key, no login.

424B2 is the pricing supplement filed when an issuer takes securities down off an effective shelf
registration. It is the highest-volume person-free filing class on EDGAR: **roughly 600–900
filings every business day**, dominated by structured notes and bank medium-term note programs
(Morgan Stanley, JPMorgan, UBS, Goldman Sachs, Bank of America), plus corporate debt takedowns.
This actor turns that whole daily flow into structured records.

### Sample output

| company\_name | form | filing\_date | primary\_document | co\_registrants |
|---|---|---|---|---|
| MORGAN STANLEY | 424B2 | 2026-08-03 | `msfl6099_424b2.htm` | — |
| BANK OF MONTREAL /CAN/ | 424B2 | 2026-08-03 | `b730261424b2.htm` | — |
| BANK OF AMERICA CORP /DE/ | 424B2 | 2026-08-03 | `form424b2.htm` | BofA Finance LLC |
| B.A.T Capital Corp | 424B2 | 2026-08-03 | `bat-prelim424bxaugust2026.htm` | 4 issuers |

```json
{
  "accession": "0001214659-26-009420",
  "cik": "0000927971",
  "company_name": "BANK OF MONTREAL /CAN/",
  "form": "424B2",
  "filing_date": "2026-08-03",
  "primary_document": "b730261424b2.htm",
  "primary_document_url": "https://www.sec.gov/Archives/edgar/data/927971/000121465926009420/b730261424b2.htm",
  "source_url": "https://www.sec.gov/Archives/edgar/data/927971/000121465926009420/0001214659-26-009420-index.htm",
  "co_registrants": []
}
```

**One filing is one record, even when five companies file it together.** Shelf programs routinely
file a single supplement under a parent guarantor and its finance subsidiaries, and SEC's index
lists every registrant separately — on a measured day, **38% of index rows were repeats of a
filing already listed.** You get one record and one charge, with the others named:

```json
"company_name": "B.A.T Capital Corp",
"cik": "0001750721",
"co_registrants": [
  {"cik": "0001750625", "company_name": "B.A.T. International Finance p.l.c."},
  {"cik": "0001750736", "company_name": "B.A.T. Netherlands Finance B.V."},
  {"cik": "0001303523", "company_name": "British American Tobacco p.l.c."},
  {"cik": "0001275283", "company_name": "REYNOLDS AMERICAN INC"}
]
```

### What you can use this for

- **Structured-notes and MTN issuance tracking** — the daily takedown flow across every bank
  program, in one feed.
- **New-issue debt monitoring** — corporate shelf takedowns as they price.
- **Filing-document pipelines** — every record carries a direct link to the actual 424B2
  document, so you can feed your own parser or LLM without crawling EDGAR yourself.
- **Issuer-activity histories** — which entities are taking down shelf capacity, and how often.

### Output fields

| field | type | description |
|---|---|---|
| `accession` | string | SEC accession number — the unique id of the filing |
| `cik` | string | Filer CIK, zero-padded to 10 digits |
| `company_name` | string | Issuer as EDGAR lists it |
| `form` | string | Always `424B2` |
| `filing_date` | string | EDGAR index date, `YYYY-MM-DD` |
| `primary_document` | string | Filename of the document SEC types as the 424B2 |
| `primary_document_url` | string | Direct link to that document on sec.gov |
| `source_url` | string | Link to the filing-index page |
| `co_registrants` | array | Other registrants on the same filing (`cik`, `company_name`) |

### Input

| field | required | prefill | description |
|---|---|---|---|
| `contactEmail` | **yes** | `smazing.actors@gmail.com` | The SEC requires every EDGAR request to carry a contact email. Replace with your own for production use — it is sent only to the SEC. |
| `days` | no | `1` | How many recent index days to pull (1–5). Weekends and holidays are skipped automatically. |
| `startDate` / `endDate` | no | — | Explicit `YYYY-MM-DD` range; overrides `days`. |
| `maxRecords` | no | `25` | Stop after N records — a cheap preview. `0` = no cap. |

### Common questions

**How many records will a full day cost me?** A business day is roughly 600–900 records after
deduplication. Set `maxRecords` to cap a preview run.

**Do I get the prospectus text?** You get a direct link to the document. The actor reads only
EDGAR's index surfaces, which is what keeps it fast and cheap; fetching and parsing several
hundred multi-hundred-KB prospectuses per day is a different product.

**Is 424B3 / 424B5 included?** No. This actor ships exactly form type `424B2` — those are
different Securities Act rule paragraphs, and matching them by prefix would bill you for records
this listing does not promise.

**Why does a record sometimes name other companies?** See the co-registrant note above: it is one
document filed by several related entities, billed once.

### Pricing

Pay per delivered record. Runs that fail return an **uncharged** error row — you pay for data,
not for our failures.

***

This is an **unofficial** tool and is **not affiliated** with, endorsed by, or sponsored by the
U.S. Securities and Exchange Commission. All data comes from public EDGAR filings. Requests are
made with a declared contact User-Agent and rate-limited well inside the SEC's published access
policy.

# Actor input Schema

## `days` (type: `integer`):

How many most-recent EDGAR index days to pull, walking back from today (weekends and holidays are skipped automatically — running on a Sunday returns Friday's filings). A full business day is roughly 400-900 deduped filings and takes 2-3 minutes.

## `startDate` (type: `string`):

Explicit range start, YYYY-MM-DD. Use together with endDate; overrides 'days'.

## `endDate` (type: `string`):

Explicit range end, YYYY-MM-DD. Use together with startDate.

## `maxRecords` (type: `integer`):

Stop after this many records — handy for a cheap preview. 0 = no cap.

## `contactEmail` (type: `string`):

Required by the SEC: EDGAR requests must carry a User-Agent identifying the requester with a contact email. Your email is sent only to the SEC, never stored or shared otherwise. Replace the prefilled address with your own for production use.

## Actor input object example

```json
{
  "days": 1,
  "maxRecords": 25,
  "contactEmail": "smazing.actors@gmail.com"
}
```

# 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 = {
    "days": 1,
    "maxRecords": 25,
    "contactEmail": "smazing.actors@gmail.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("sourcesauce/sec-424b2-supplements").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 = {
    "days": 1,
    "maxRecords": 25,
    "contactEmail": "smazing.actors@gmail.com",
}

# Run the Actor and wait for it to finish
run = client.actor("sourcesauce/sec-424b2-supplements").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 '{
  "days": 1,
  "maxRecords": 25,
  "contactEmail": "smazing.actors@gmail.com"
}' |
apify call sourcesauce/sec-424b2-supplements --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,sourcesauce/sec-424b2-supplements"
        }
    }
}

```

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/GLGfeQnrpUPEF4NJM/builds/4AkqN8FTV6719ffXO/openapi.json