# Insider Trading Signal Feed (`hereditary_model/insider-trading-signal-feed`) Actor

Pulls SEC Form 4 insider transactions for your tickers and flags cluster buying, scored for signal strength.

- **URL**: https://apify.com/hereditary\_model/insider-trading-signal-feed.md
- **Developed by:** [Aaron Marxsen](https://apify.com/hereditary_model) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 insider transaction returneds

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/platform/actors/running/actors-in-store#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

## Insider Trading Signal Feed

Executives and directors have to disclose every open-market stock purchase within two business days, on SEC Form 4. Most of that signal is buried in raw filings nobody reads. This pulls it straight from EDGAR for the tickers you care about, keeps only real cash purchases (and sales, if you want them), and flags when more than one insider is buying the same stock at once — the pattern that's historically the loudest insider signal there is.

### What it does

1. Resolves each ticker to its SEC CIK number.
2. Pulls Form 4 filings from the lookback window you set.
3. Parses each filing's transactions directly from SEC's XML, no third-party data reseller in between.
4. Keeps open-market purchases (code `P`) by default; sales (code `S`) are opt-in. Grants, option exercises, and gifts are dropped — they're real filings, but not a conviction signal.
5. Scores each ticker 0-100 on buying conviction: how many distinct insiders bought, how much they spent, and whether an officer, director, or 10%+ owner was among them.
6. Flags `clusterBuying: true` once enough distinct insiders bought the same ticker inside your window.
7. Drops anything under your minimum transaction value **before** billing.

### Output

| Field | Notes |
| --- | --- |
| `ticker`, `issuerName` | What was traded |
| `ownerName`, `role` | Who traded it — title if they're an officer, plus director / 10%+ owner flags |
| `kind`, `transactionCode` | `purchase` (P) or `sale` (S) |
| `transactionDate`, `shares`, `pricePerShare`, `transactionValue` | The trade itself |
| `sharesOwnedAfter` | Their resulting stake |
| `distinctBuyers`, `totalBuyValue`, `clusterBuying`, `qualityScore` | Ticker-level signal, repeated on every row for that ticker |
| `filingUrl` | Link to the source Form 4, for verification |

### Input

Only `tickers` is required.

```json
{
  "tickers": ["AAPL", "TSLA"],
  "lookbackDays": 90,
  "minTransactionValue": 25000,
  "minClusterBuyers": 2,
  "includeSales": false
}
```

### A note on SEC access

SEC's fair-access policy asks automated tools to identify a real contact in the `User-Agent` header. Set `requesterEmail` to your own address — it's used only in that header, on every request this run makes, and nowhere else.

### Pricing

Pay per event. You're billed for qualifying transactions returned and for cluster-buying alerts, not for the SEC lookups themselves.

# Actor input Schema

## `tickers` (type: `array`):

Ticker symbols to check for insider Form 4 activity, one per line, for example AAPL or TSLA.

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

How many days of Form 4 filing history to scan per ticker.

## `minTransactionValue` (type: `integer`):

Drop transactions worth less than this, before billing. Set to 0 to keep everything.

## `minClusterBuyers` (type: `integer`):

Number of different insiders who must buy the same ticker within the lookback window to trigger a cluster-buying alert.

## `includeSales` (type: `boolean`):

When enabled, also returns disposal (sale) transactions in addition to open-market purchases.

## `maxFilingsPerTicker` (type: `integer`):

Caps how many recent Form 4 filings are fetched per ticker, so run time and cost stay predictable.

## `requesterEmail` (type: `string`):

SEC's fair-access policy requires a real contact email in the request User-Agent for automated EDGAR access. Used only in that header, never stored or shared.

## Actor input object example

```json
{
  "tickers": [
    "AAPL"
  ],
  "lookbackDays": 90,
  "minTransactionValue": 25000,
  "minClusterBuyers": 2,
  "includeSales": false,
  "maxFilingsPerTicker": 40,
  "requesterEmail": ""
}
```

# Actor output Schema

## `transactions` (type: `string`):

No description

## `summary` (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 = {
    "tickers": [
        "AAPL"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hereditary_model/insider-trading-signal-feed").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 = { "tickers": ["AAPL"] }

# Run the Actor and wait for it to finish
run = client.actor("hereditary_model/insider-trading-signal-feed").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 '{
  "tickers": [
    "AAPL"
  ]
}' |
apify call hereditary_model/insider-trading-signal-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hereditary_model/insider-trading-signal-feed"
        }
    }
}

```

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/f6Syim8NPCnckUNeu/builds/9KJpP0aWBy9Bbg0I1/openapi.json