AnswerPool

Insider Buy Clusters API: List issuers where 3+ distinct officers or directors bought within — SEC Form 4

List issuers where 3+ distinct officers or directors bought within a week — returns combined buy USD, insider count and names per issuer. A derived cluster signal no other API sells as one call; use as a high-conviction insider screen.

$0.05 per call — pay with prepaid card credits (Authorization: Bearer ck_live_…, packs from $1) or with USDC over x402: call it, get 402 with the price, retry signed. Failed calls are never charged.

How do you call it?

GET /v1/sec/insider/clusters — product id sec_insider_clusters. Over MCP, call answerpool_get with product_id=sec_insider_clusters.

curl "https://answerpool.io/v1/sec/insider/clusters?days=7"

# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/sec/insider/clusters?days=7"

Live call: https://answerpool.io/v1/sec/insider/clusters?days=7 · JSON sample: /v1/samples/sec_insider_clusters

What does the answer look like?

A representative response, the same static sample served at /v1/samples/sec_insider_clusters.

as_of2026-08-31T14:00:00Z
index_started_at2026-08-27T00:00:00Z
window_days7
count1
refresh_after2026-09-17T11:15:00.000Z

clusters

ciktickercompanyinsidersinsider_namesbuy_usdfilingslatest_at
0000096223JEFJEFFERIES FINANCIAL GROUP INC.3FRIEDMAN BRIAN P, HANDLER RICHARD B, OSBORNE MATT4500000.032026-08-28T21:53:58
The same sample as raw JSON
{
 "as_of": "2026-08-31T14:00:00Z",
 "index_started_at": "2026-08-27T00:00:00Z",
 "window_days": 7,
 "count": 1,
 "clusters": [
  {
   "cik": "0000096223",
   "ticker": "JEF",
   "company": "JEFFERIES FINANCIAL GROUP INC.",
   "insiders": 3,
   "insider_names": [
    "FRIEDMAN BRIAN P",
    "HANDLER RICHARD B",
    "OSBORNE MATT"
   ],
   "buy_usd": 4500000.0,
   "filings": 3,
   "latest_at": "2026-08-28T21:53:58"
  }
 ],
 "refresh_after": "2026-09-17T11:15:00.000Z"
}

How fresh is it, and where does the data come from?

The fastest source behind this answer can change every 15 minutes, so every response carries a refresh_after timestamp — right now it would be 2026-09-17T11:15:00.000Z. Schedule the next call on that value rather than on a guess.

Method version 0.1.0 · serving cache 1 day · every response carries a result_id you can resolve at /v1/provenance.

When should you use it?

Screening for the strongest insider-buying setups.

What you skip building

When should you not use it?

Per-line detail or single-issuer history — use the other insider views.

Where else can you find this?