AnswerPool

Subsidiary Tree API: Subsidiary names and jurisdictions extracted from any public company's — SEC EDGAR

Subsidiary names and jurisdictions extracted from any public company's latest annual-report Exhibit 21, with the source exhibit URL for verification. One call replaces locating and parsing EX-21 filings.

$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/graph/subsidiaries — product id graph_subsidiaries. Over MCP, call answerpool_get with product_id=graph_subsidiaries.

curl "https://answerpool.io/v1/graph/subsidiaries?ticker=AAPL"

# with a prepaid credit key
curl -H "Authorization: Bearer ck_live_..." "https://answerpool.io/v1/graph/subsidiaries?ticker=AAPL"

Live call: https://answerpool.io/v1/graph/subsidiaries?ticker=AAPL · JSON sample: /v1/samples/graph_subsidiaries

What does the answer look like?

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

as_of2026-09-02T22:00:00Z
cik0000320193
nameApple Inc.
accession0000320193-25-000123
filed2025-11-01
source_urlhttps://www.sec.gov/Archives/edgar/data/320193/000032019325000123/ex21.htm
note—
count1
refresh_after2026-09-17T11:15:00.000Z

subsidiaries

namejurisdiction
Apple Operations International Ltd.Ireland
The same sample as raw JSON
{
 "as_of": "2026-09-02T22:00:00Z",
 "cik": "0000320193",
 "name": "Apple Inc.",
 "accession": "0000320193-25-000123",
 "filed": "2025-11-01",
 "source_url": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000123/ex21.htm",
 "note": null,
 "count": 1,
 "subsidiaries": [
  {
   "name": "Apple Operations International Ltd.",
   "jurisdiction": "Ireland"
  }
 ],
 "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 7 days · every response carries a result_id you can resolve at /v1/provenance.

When should you use it?

You need the registrant's disclosed subsidiary list and jurisdictions.

What you skip building

When should you not use it?

Complete ownership structures — issuers may omit minor subsidiaries, and parsing is best-effort (source_url is always included).

Where else can you find this?