← LiveDataLink Blog

Resolve any US company to its canonical IDs (CIK, LEI, EIN)

Last updated: May 21, 2026

Company names are ambiguous, but identifiers are not. To turn a name like "Acme Robotics" into the canonical IDs that other tools and datasets join on, call the LiveDataLink resolve_entity tool. It fans out across the public sources that carry a strong identifier and returns a compact canonical-IDs block: SEC EDGAR CIK and ticker, GLEIF LEI with its ownership chain, IRS EIN, USAspending recipient, EPA facility registry id, and an organizational NPI for healthcare entities, each with a per-source confidence.

Resolve a name to its IDs

The only required argument is name. Optional hints (ticker, cik, ein, state) sharpen the match when a name is common.

{
  "method": "tools/call",
  "params": {
    "name": "resolve_entity",
    "arguments": { "name": "Lockheed Martin", "ticker": "LMT" }
  }
}

You get back the best-matched canonical identity, the IDs it resolves to, an entity-type guess, and an overall match confidence. A source that fails is noted, not fatal, so a missing leg never sinks the whole call.

Ownership comes with the LEI

The GLEIF leg does more than return a Legal Entity Identifier. It carries the reported ownership chain: the direct parent LEI, the ultimate parent LEI, and the reported subsidiary count. That means one call answers not just "what is this company's LEI" but "who owns it and how big is the group," which matters for KYB, beneficial-ownership checks, and rolling up a corporate family before you screen or score it.

Why resolve before you do anything else

Resolution is a join-key primitive: run it first, then feed the canonical IDs to everything downstream. A name like "Acme" can match dozens of SEC filers; resolving to a CIK, LEI, or EIN first means your trust check, sanctions screen, or risk score runs against the right company instead of fuzzy-matching the name again on every leg. That cuts false matches across the whole workflow. The one-call decision tools at /decisions use exactly this pattern internally, and /compliance-pack packages the full KYB flow.

FAQ

What identifiers can it return?

SEC CIK and ticker, GLEIF LEI plus direct and ultimate parent LEI and subsidiary count, IRS EIN, USAspending recipient name, EPA facility registry id, and an organizational NPI for healthcare entities, plus a sanctions match flag, each with its own confidence.

What if the name is ambiguous?

Pass a hint. A ticker, cik, ein, or state pins the match. The response also carries per-source confidence so you can gate on it before trusting a join.

Are UEI or SAM.gov IDs included?

No. UEI/SAM.gov and domain-owner (RDAP) identifiers are not wired sources, so they are omitted rather than guessed. Verify any identifier against the primary source before relying on a join.

Last updated: May 21, 2026 · LiveDataLink home