# SEC Schedule 13D/13G Beneficial Ownership Monitor (`apex-nexus/sec-13d-13g-monitor`) Actor

Monitors a watchlist of SEC tickers/CIKs for new Schedule 13D/13G beneficial-ownership filings and emits one dataset item per newly detected filing. Public SEC data only; deterministic; no inference.

- **URL**: https://apify.com/apex-nexus/sec-13d-13g-monitor.md
- **Developed by:** [Valunex](https://apify.com/apex-nexus) (community)
- **Categories:** Business, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 new 13d/13g alerts

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?

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 Schedule 13D/13G Beneficial Ownership Monitor

Monitors a watchlist of SEC issuer tickers/CIKs for new Schedule 13D /
13D/A / 13G / 13G/A filings (5%+ beneficial-ownership stakes — new filings,
amendments, reporting-person changes) and emits one dataset item per newly
detected filing since the last run.

### Who it is for

Activist-investment monitors, event-driven funds, M\&A practitioners and
corporate-governance researchers who need the earliest public signal of a new
large holder: a Schedule 13D must be filed within 10 days of crossing a 5%
beneficial-ownership stake, making it one of the fastest public ownership
signals available. This Actor watches issuers you choose and remembers what it
already reported, so repeat runs emit only genuinely new filings — free when
nothing changes.

### Forms monitored

| Form | What it is | What the Actor emits |
|------|------------|----------------------|
| **SC 13D** | Initial statement of beneficial ownership (5%+ stake) | Filer name/CIK, issuer name/CIK, filing/report dates, accession, document link |
| **SC 13D/A** | Amendment to a Schedule 13D | Same fields as SC 13D |
| **SC 13G** | Initial statement (passive/qualified institutional investor, 5%+) | Same fields as SC 13D |
| **SC 13G/A** | Amendment to a Schedule 13G | Same fields as SC 13G |

### What makes it different

Existing Apify Store actors for SEC filings (e.g. ryanclinton/sec-insider-trading at $0.02 per trade fetched, ryanclinton/edgar-filing-search covering 13D/G under paid "pay per record") are on-demand fetchers: you run them, get a batch, and run again when you want an update. This Actor keeps a watchlist and remembers what it already reported, so repeat runs emit only newly detected filings — free when nothing changes.

### Data source

Public SEC data only, via official SEC endpoints:

- https://www.sec.gov/files/company_tickers.json (ticker -> CIK)
- https://data.sec.gov/submissions/CIK{CIK}.json (company recent filings)
- https://www.sec.gov/Archives/edgar/data/... (filing document text)

No credentials, no proxies, no scraping of rate-limited or anti-bot pages, no commercial inference (no LLMs) inside the product. SEC rate guidance (~10 requests/s) is respected (~8 req/s via a 0.12s inter-request delay); a failing watchlist entry never aborts the whole run.

### Pricing (pay-per-event, Apify Store)

- Actor start: $0.0001 per run (one-time)
- New alert (dataset item): $0.005 per new Schedule 13D/13G filing detected
- Price changes are limited to no more than once per month, with at least 14 days' notice before they take effect (per Apify Terms).

Apify retains a 20% commission on revenue; payouts are monthly and require completed identity verification (KYC). See knowledge/decisions.md for the full margin model and kill test.

### Input

See actor/.actor/input_schema.json. Required: `ciks` (array of SEC tickers or CIKs, max 50).

- `formTypes`: array of `"SC 13D"`, `"SC 13D/A"`, `"SC 13G"`, `"SC 13G/A"`, default monitors all four.
- `lookbackDays` (1-365, default 90): how far back to look on the first run.
- `maxResultsPerCik` (1-100, default 10): cap the number of new filings emitted per watched issuer per run.

Example:

```json
{ "ciks": ["BRK.A", "BRK.B", "AAPL", "MSFT", "TSLA"], "lookbackDays": 90, "maxResultsPerCik": 10 }
```

### Output

One dataset item per newly detected filing. Common fields are always present;
form-type-specific fields are `null` when not parseable or not applicable:

```json
{
  "ticker": "BRK.A",
  "cik": "0001067983",
  "issuerName": "Berkshire Hathaway Inc.",
  "issuerCik": "0001067983",
  "form": "SC 13G",
  "filingDate": "2026-02-13",
  "reportDate": "2026-02-13",
  "accessionNumber": "0001193125-26-048901",
  "primaryDocument": "a8-k20260213.htm",
  "documentUrl": "https://www.sec.gov/Archives/edgar/data/1067983/000119312526048901/a8-k20260213.htm",
  "newSinceLastRun": true,
  "filerName": "Berkshire Hathaway Inc.",
  "filerCik": "0001067983"
}
```

Every field is `null` when it could not be parsed from the filing document — the Actor never guesses.

### Limits

- Max 50 watchlist entries per run, 100 alerts per entry per run.
- Only forms listed in `formTypes` in the company's recent filings feed are considered; older filings outside the SEC's recent feed are not scanned.
- Checkpoints persist per watched issuer in the Actor key-value store; resetting the store re-emits filings within the lookback window.

### Verification

Run `pytest actor/tests` before release (builder acceptance criterion).

# Actor input Schema

## `ciks` (type: `array`):

SEC tickers (e.g. BRK.A) or CIKs of issuers to monitor for new Schedule 13D/13G filings. Duplicate entries are merged and one erroring entry never aborts the run.

## `formTypes` (type: `array`):

Filing types to scan for each watched issuer: SC 13D, SC 13D/A, SC 13G, SC 13G/A. Default monitors all four.

## `lookbackDays` (type: `integer`):

How far back to look for filings on the first run; repeat runs only emit filings newer than the last checked state.

## `maxResultsPerCik` (type: `integer`):

Cap the number of new filings emitted per watched issuer in a single run.

## Actor input object example

```json
{
  "ciks": [
    "BRK.A",
    "BRK.B",
    "AAPL",
    "MSFT",
    "TSLA"
  ],
  "formTypes": [
    "SC 13D",
    "SC 13D/A",
    "SC 13G",
    "SC 13G/A"
  ],
  "lookbackDays": 90,
  "maxResultsPerCik": 10
}
```

# Actor output Schema

## `overview` (type: `string`):

Dataset items filtered by the overview view defined in the dataset schema.

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

All dataset items emitted by the Actor run (newly detected Schedule 13D/13G filings).

# 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 = {
    "ciks": [
        "BRK.A",
        "BRK.B",
        "AAPL",
        "MSFT",
        "TSLA"
    ],
    "formTypes": [
        "SC 13D",
        "SC 13D/A",
        "SC 13G",
        "SC 13G/A"
    ],
    "lookbackDays": 90,
    "maxResultsPerCik": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("apex-nexus/sec-13d-13g-monitor").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 = {
    "ciks": [
        "BRK.A",
        "BRK.B",
        "AAPL",
        "MSFT",
        "TSLA",
    ],
    "formTypes": [
        "SC 13D",
        "SC 13D/A",
        "SC 13G",
        "SC 13G/A",
    ],
    "lookbackDays": 90,
    "maxResultsPerCik": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("apex-nexus/sec-13d-13g-monitor").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 '{
  "ciks": [
    "BRK.A",
    "BRK.B",
    "AAPL",
    "MSFT",
    "TSLA"
  ],
  "formTypes": [
    "SC 13D",
    "SC 13D/A",
    "SC 13G",
    "SC 13G/A"
  ],
  "lookbackDays": 90,
  "maxResultsPerCik": 10
}' |
apify call apex-nexus/sec-13d-13g-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,apex-nexus/sec-13d-13g-monitor"
        }
    }
}
```

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/Ml5Mi3PxGNk4qa8kr/builds/dc1kAreYkOxDPvC8C/openapi.json