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:

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

Output

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

{
  "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.