# SEC Form 13F Institutional Holdings Monitor (`apex-nexus/sec-form-13f-monitor`) Actor

Monitors SEC Form 13F filings for institutional managers on a watchlist. Emits one alert per new 13F-HR holdings filing since the last check. Public SEC data only; deterministic; free when nothing changes.

- **URL**: https://apify.com/apex-nexus/sec-form-13f-monitor.md
- **Developed by:** [Valunex](https://apify.com/apex-nexus) (community)
- **Categories:** Automation, Lead generation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 13f-hr 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 Form 13F Institutional Holdings Monitor

Monitors a watchlist of institutional investment managers (SEC CIKs or names that
file Form 13F-HR) and emits one dataset item per newly detected 13F-HR quarterly
holdings filing — what institutions bought, sold, added, or exited — since the
last run.

### Who it is for

Compliance officers, quant/research desks, copy-trade services, RIAs tracking
institutional holdings, M\&A professionals and watchdog analysts who need to
know when institutions file 13F-HR holdings reports, without re-polling SEC
EDGAR manually.

### What it monitors

| Form | What it is | What the Actor emits |
|------|------------|----------------------|
| **13F-HR** | Quarterly institutional investment manager holdings report | Manager name, report period, holdings count, total holdings value |

The Actor scans only `form == "13F-HR"` in each watched manager's SEC recent
filings feed and emits one dataset item per newly detected filing.

### How it differs from sec-form-4-monitor (niche distinction)

The sibling Actor `sec-form-4-monitor` (apex-nexus~sec-form-4-monitor) watches a
watchlist of tickers/CIKs for insider-trading and ownership filings — by default
Form 4 (officers, directors and 10% owners buying or selling the issuer's own
stock, reported within two business days, with transaction codes such as P/S/A
and per-transaction values); it can optionally also scan Forms 3, 5 and 13F via
its `formTypes` input, but its output model is transaction-centric
(insider/issuer, transaction code, transaction value).

This Actor (`sec-form-13f-monitor`) watches institutional investment managers
for Form 13F-HR quarterly holdings reports only: a portfolio-level snapshot of
what each institution holds at quarter-end (issuers, values, holdings count,
total portfolio value), filed roughly 45 days after quarter end under Section 13(f).

They are different regulatory forms, with different data models, cadences and
audiences, so they are complementary rather than near-duplicates:

| | sec-form-4-monitor | sec-form-13f-monitor |
|---|---|---|
| Default form | Form 4 — insider transactions | Form 13F-HR — institutional quarterly holdings |
| Cadence | Event-driven (2 business days after the transaction) | Quarterly (report date = quarter end) |
| Subject | Insider vs. issuer (who trades the stock) | Institution vs. portfolio (what institutions hold) |
| Output model | insiderName/insiderCik, transactionCode, transactionValue | managerName, holdingsCount, totalValueUsd, reportDate |
| Audience | Insider-trading tracking, ownership-change alerts | Quant/research desks, copy-trade services, RIAs tracking institutional holdings |

One dataset item per newly detected filing is emitted by both, but they answer
different questions and serve different buyers — this Actor is not a duplicate
listing of sec-form-4-monitor.

### Data source

Public SEC data only, via official SEC endpoints:

- https://www.sec.gov/files/company_tickers.json (CIK / name -> CIK resolution)
- 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); one erroring
CIK never aborts the whole run.

### State and "free when nothing changes"

A per-CIK checkpoint (highest filingDate seen + seen accession numbers) is kept
in the Actor default key-value store. Repeat runs emit only genuinely new
filings — if nothing changed since the last run, the run emits zero items.

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

- Actor start: $0.0001 per run (one-time)
- New alert (dataset item): $0.005 per 13F-HR alert dataset item
- 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).

This README states pricing exactly as the publishing contract defines it. It
makes no revenue, customer, or adoption claims beyond those evidenced.

### Input

See `actor/input-schema.json`. Required: `ciks` (array of SEC CIKs or manager
names, max 50).

- `ciks`: SEC CIKs (10-digit, e.g. `0000102909`) or names/tickers of
  institutional investment managers (e.g. `BRK.A`, `VANGUARD`). Names are
  resolved to CIKs via the SEC company_tickers.json file. Duplicate entries are
  merged; one erroring CIK never aborts the run.
- `lookbackDays` (1-90, default 60): how far back to look on the first run;
  repeat runs only emit filings newer than the last checked state.
- `maxResultsPerCik` (1-50, default 10): cap on new 13F-HR filings emitted per
  CIK per run.
- `deliveryWebhookUrl` (optional): each new alert is POSTed as JSON to that URL
  as it is detected. Webhook failures are logged and never abort the run.

Example:

```json
{
  "ciks": ["0000102909", "0000136569", "0000056733"],
  "lookbackDays": 60,
  "maxResultsPerCik": 10
}
```

### Output

One dataset item per new 13F-HR filing. Sample output:

```json
{
  "managerName": "Vanguard Group",
  "managerCik": "0000102909",
  "companyName": "The Vanguard Group, Inc.",
  "companyCik": "0000102909",
  "form": "13F-HR",
  "filingDate": "2026-10-28",
  "reportDate": "2026-09-30",
  "accessionNumber": "0000102909-26-000123",
  "primaryDocument": "infoTable.xml",
  "holdingsCount": 2,
  "totalValueUsd": 1250500.0,
  "newSinceLastRun": true
}
```

Every field is `null` when it could not be parsed from the filing document —
the Actor never guesses. `managerCik` falls back to the watched CIK when the
document does not carry a manager CIK.

### Limits

- Max 50 CIKs per run, 50 alerts per CIK per run.
- Only `13F-HR` filings in each manager's recent filings feed are considered;
  older filings outside the SEC's recent feed are not scanned.
- Checkpoints persist per CIK in the Actor key-value store; resetting the store
  re-emits filings within the lookback window.

### Files

- `actor/main.py` — Apify SDK Python Actor
- `actor/input-schema.json` — JSONSchema input definition
- `actor/requirements.txt` — pinned deps (`apify==4.1.0`, `httpx==0.27.2`)
- `actor/tests/test_monitor.py` — unit tests
- `actor/.actor/actor.json`, `.actor/input_schema.json`, `.actor/dataset_schema.json`, `.actor/output_schema.json` — Apify platform metadata

### Verification

Run `pytest actor/tests` before release (builder acceptance criterion). The
suite is deterministic and needs no network.

### Licensing

Only Apify SDK + httpx (MIT-compatible). Original code; no competitor code
copied; no Apex code; no secrets committed.

# Actor input Schema

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

SEC CIKs (10-digit, e.g. 0000102909) or names/tickers of institutional investment managers to monitor for new 13F-HR filings. Names/tickers are resolved to CIKs via the SEC company_tickers.json file using an exact match; entries that cannot be resolved are skipped (use a CIK for reliable resolution). Duplicate entries are merged and one erroring CIK never aborts the run.

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

How far back to look for 13F-HR filings on the first run; repeat runs only emit filings newer than the last checked state. 13F is filed quarterly, so the default window is 60 days.

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

Cap the number of new 13F-HR filings emitted per CIK in a single run.

## `deliveryWebhookUrl` (type: `string`):

Optional HTTPS webhook URL each new alert is POSTed to as JSON as it is detected. Webhook failures are logged and never abort the run.

## Actor input object example

```json
{
  "lookbackDays": 60,
  "maxResultsPerCik": 10,
  "deliveryWebhookUrl": ""
}
```

# 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 13F-HR 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 = {
    "lookbackDays": 60,
    "maxResultsPerCik": 10,
    "deliveryWebhookUrl": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("apex-nexus/sec-form-13f-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 = {
    "lookbackDays": 60,
    "maxResultsPerCik": 10,
    "deliveryWebhookUrl": "",
}

# Run the Actor and wait for it to finish
run = client.actor("apex-nexus/sec-form-13f-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 '{
  "lookbackDays": 60,
  "maxResultsPerCik": 10,
  "deliveryWebhookUrl": ""
}' |
apify call apex-nexus/sec-form-13f-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,apex-nexus/sec-form-13f-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/fzGxCTVLRRkwWIR6y/builds/kf1aFA1LK2NaUhGma/openapi.json