Northeast Asia 5% disclosures, as one English graph.

Ownership API unifies 5%-rule and acquisition filings from Korea, Japan, China, Hong Kong, Taiwan, and US ADRs into one cross-lingual ownership graph. Same entity in 한국어 / 日本語 / 中文 / English collapses to one canonical node, automatically.

What it is

Most ownership data vendors are either expensive enterprise platforms with limited Northeast Asia depth, or local databases that only cover one country in one language. Ownership API sits in the gap.

  • Six primary sources, polled daily: OpenDART (Korea), EDINET (Japan), CNINFO (China), HKEX (Hong Kong), TWSE (Taiwan), SEC EDGAR (US ADRs).
  • Cross-lingual Entity Resolution: "삼성전자" in a Korean 5% filing, "サムスン電子" in a Japanese filing, and "Samsung Electronics" in a US filing resolve to one canonical ID.
  • Every relation cites the original disclosure sentence (evidence_quote). Built for audit, not for vibes.
  • Ownership state plus full history. Same shareholder pair across multiple filings keeps the latest percentage and records every change.

How it compares

The benchmarks below are who we measure against, and where Ownership API differs.

ProviderCoveragePricingWhat we do differently
Sayari Graph
Moody's-adjacent peer
500M+ companies, 250+ jurisdictions, beneficial-ownership chains. API Credits + Pro/Enterprise tiers. Indicative Pro pricing $499-2,000/mo. We are narrower (Northeast Asia first) and an order of magnitude cheaper at the Developer tier.
Moody's Orbis (BvD) 625M companies, 170+ sources, corporate trees. Enterprise contracts, often $10K-200K+ per year. Developer-friendly REST, transparent pricing, no procurement cycle.
LSEG / Refinitiv PermID-anchored institutional and insider ownership. Enterprise contracts via account managers. Our canonical IDs are public, our endpoints are documented, sign-up is self-service.
NICE D&B KIS-LINE (Korea) Korean shareholders, executives, credit. BizAPI metered. We add Japan, China, Hong Kong, Taiwan, and US ADRs in the same graph and same language.
Teikoku Databank / TSR (Japan) Japanese credit reports, partial ownership. Per-report ¥3,000-30,000+, Japanese only. Programmatic, English output, cross-lingual joins.
Tianyancha / Qichacha / Qixin (China) GSXT-based shareholders, relationships, litigation. Subscription ¥30-300/mo, separate API. Chinese filings join with HKEX listings and Korean / Japanese filings on the same canonical IDs.
Webb-site (Hong Kong) HK-listed company directors and stats since 1990s. Free. Primary server shut down 2025-10; mirrors remain. We keep a live HK feed inside the same graph as the rest of Northeast Asia.

A single call

Ownership trees are one HTTP GET. Depth 1-4. Direction owners, owns, or both.

curl "https://api.hannune.ai/ownership/v1/companies/company_xxx/ownership-tree?depth=3&direction=owners" \
     -H "Authorization: Bearer YOUR_KEY"

The response is a node plus a list of edges. Every edge carries the percentage, the effective date, the originating filing, and the evidence sentence. Identifiers across countries are the same canonical IDs you already use from the Hannune Entity Resolution API.

Pricing

Four self-service tiers plus Enterprise. The Developer tier is roughly one tenth of comparable enterprise alternatives. Payments via Polar, sales tax handled.

Free

$0/mo
  • 100 calls / month
  • Depth 2
  • Tree visualization
  • 60-min response cache

Professional

$199/mo
  • 50,000 calls / month
  • Depth 4
  • Unlimited history
  • Monthly JSONL bulk export
  • On-demand new-entity ingest

Business

$999/mo
  • 500,000 calls / month
  • Depth 4
  • Daily JSONL bulk export
  • Webhook alerts on ownership changes
  • Priority new-source requests

Enterprise

Talk to us
  • Unlimited calls
  • SLA, on-premise option
  • Custom polling cadence
  • Priority custom sources

Ownership API and Entity Resolution API share one Hannune account and one API key. If you already use ER API, your canonical IDs work here on day one.

How it is built

  • Daily polling: every business day at 03:30 UTC the pipeline pulls new filings, extracts ownership relations with structured output, runs them through Entity Resolution, and commits to a dedicated graph database.
  • Evidence guard: every relation must carry a verbatim quote from the source filing. Percentages must appear in that quote. If they don't, the relation is dropped, not fabricated.
  • Effective-date replace policy: when a later filing arrives, the percentage and date are updated only if the new filing's effective date is at least as recent. Out-of-order arrivals stay correct.
  • Cross-lingual ER: the same registry that powers the Hannune Entity Resolution API resolves Korean / Japanese / Chinese / English filer names to one canonical ID.

What is next

  • Risk and sanctions overlays on top of the ownership graph (modeled on Sayari's 4-hour sanctions refresh).
  • Webhook push notifications on ownership-percentage changes for Business tier.
  • On-premise deployment package for Enterprise.