GLEIF LEI Lookup & Entity Change Monitor

Assess official GLEIF Legal Entity Identifier records with identity-match evidence, renewal posture, human-readable reference codes, published parent context, source-data quality, and an explainable review priority. Search by company or LEI, export a bounded country registry, and use the same Actor to track verified company, renewal, status, relationship, successor, and predecessor changes over time.

Enter one exact LEI for the strongest match or search registered company names in a batch. Every signal is derived from official GLEIF data; the Actor does not add sanctions, adverse-media, beneficial-ownership, or black-box risk claims.

🚀 Start in 60 seconds

1. Choose Assess current companies.
2. Enter one exact LEI or one or more registered company names.
3. Keep the Standard result for the complete entity assessment.
4. Click Start and open the Dataset and Portfolio review summary.

{
  "mode": "baseline",
  "leis": ["529900T8BM49AURSDO55"]
}

The default returns up to 5 company records, includes published direct/ultimate parent context and resolved legal-form/registration-authority names, limits separate relationship records to 20, and stops before a projected $0.25 Actor charge.

🎯 Choose the right workflow

Workflow	Use it for	Result
Assess current companies	Vendor onboarding input, counterparty review, entity resolution, renewal checks, or portfolio triage	Current enriched company rows, optional relationship rows, and a portfolio summary
Track verified changes	Repeat checks for status, renewal, entity facts, published parents, successors, predecessors, and other relationships	Deterministic NEW, UPDATED, or safely confirmed ENDED records plus typed business events

For a country registry export, leave LEIs and company names empty and add one or more ISO two-letter codes in countries. The Actor pages through official GLEIF results up to maxEntities; reaching that limit is reported as CAPPED, never as complete country coverage.

The first run in Track verified changes creates the comparison snapshot and normally returns no change records. For repeat runs, keep the same targets, filters and enrichment options, and finish one same-scope run before starting the next. Use maxTrackedItems to cap the combined company and relationship snapshot and the changes delivered by one run; the Actor accepts up to 200 tracked items.

📦 What you get

Each Standard company result contains:

• LEI, legal and other names, status, category, jurisdiction, addresses, registration dates, managing LOU, BICs, and local registry number.
• Human-readable legal-form and registration-authority names resolved through official GLEIF reference endpoints.
• identityConfidence, identityVerdict, and matchingEvidence for an exact LEI, company name, country, and optional expected registration number.
• renewalStatus, daysUntilRenewal, recordFreshness, official conformity evidence, and source-data quality.
• Published direct/ultimate parent basics or official reporting exceptions, with an explicit relationship-evidence state that never infers beneficial ownership.
• reviewPriority, recommendedNextStep, reviewFlags, and a complete decisionPath derived only from the returned GLEIF facts.
• Optional subsidiary counts, raw relationship edges, successors/predecessors, legal-entity events, and mapped ISIN securities.

Synthetic fixture (identifiers and names below are intentionally not live GLEIF records):

{
  "recordType": "entity",
  "stableId": "entity:00000000000000000000",
  "lei": "00000000000000000000",
  "legalName": "Synthetic Demo Entity GmbH",
  "identityVerdict": "EXACT_LEI_MATCH",
  "renewalStatus": "CURRENT",
  "reviewPolicy": "balanced",
  "reviewPriority": "LOW",
  "recommendedNextStep": "USE_AS_CURRENT_GLEIF_REFERENCE",
  "parentContext": {
    "requested": true,
    "directParent": { "lei": "11111111111111111111", "legalName": "Synthetic Demo Parent SE" }
  }
}

The separate PORTFOLIO_SUMMARY output includes status, renewal, country and review-priority distributions; renewal and high-priority queues; shared published parents; and change counts.

🎛️ Input guide

Companies and identity evidence

• leis — up to 200 exact 20-character LEIs; each receives EXACT_LEI_MATCH.
• companyNames — up to 100 registered-name searches, with up to 200 matches per name.
• countries — up to 20 ISO two-letter filters. With company names they narrow each search; without LEIs or names they become bounded country-registry targets.
• country — hidden backward-compatible single-country alias for existing API inputs.
• registrationNumber — optional expected home-registry number used as positive identity evidence when it matches.
• entityStatus, registrationStatus, entityCategory — optional GLEIF filters for company-name searches.

Result and review detail

• outputProfile — Essential for compact automation, Decision for review fields, Standard for the complete normalized result, or Full to retain the official source record as well.
• reviewPolicy — Balanced, renewal-strict, or identity-strict source-backed review weights. None is an approval, legal, sanctions, credit, or compliance verdict.
• includeParentContext — official direct/ultimate parent basics or reporting exceptions; on by default and included in the company-record charge.
• resolveReferenceData — official legal-form and registration-authority names; on by default and included in the company-record charge.

Optional relationships and identifiers

• includeRelationships — adds official requests and runtime for separate parent, head-office, branch and fund rows. They are bundled in Assess current companies; only delivered verified relationship changes use the change event in Track verified changes.
• includeChildren — adds official requests and runtime for direct/ultimate subsidiary counts and rows, with the same Baseline-bundled/Changes-event rule.
• expandHierarchy and maxHierarchyDepth — walk the published direct-parent chain for up to 10 levels. The chain is included in the company row; a verified chain update is a change event only in Track verified changes.
• includeSuccessorsPredecessors — adds official requests and runtime for published links and legal-entity events, included in Baseline and charged only when a verified change is delivered in Changes.
• includeSecurities — adds official requests and runtime for mapped ISINs, included in Baseline and charged only when the mapped set produces a delivered entity change.

Monitoring and safeguards

• deltaWindow selects the official Golden Copy change window used by Track verified changes.
• includeUnchanged optionally adds unchanged audit records without charging them as changes.
• watchlistName gives a monitored portfolio a stable label and keeps its state history separate.
• maxEntities bounds Baseline company results from 1 to 5,000. maxTrackedItems independently bounds the combined Changes state and delivered changes from 1 to 200; the preflight reserves room for as many as 400 simultaneous current and safely confirmed ended candidates. maxRelationships, maxSecurities, and maxBuyerChargeUsd bound enrichment and projected charges. For large country exports, turn off optional parent/relationship enrichment unless it is required.

💰 Pricing

run charge = verified run start + delivered company records, or, in Track verified changes, verified run start + delivered changes. Separate Baseline relationship rows are bundled with their delivered company records.

Result event	Free	Bronze	Silver	Gold
Verified run start	$0.001	$0.001	$0.001	$0.001
Enriched company record	$0.00170	$0.00168	$0.00166	$0.00164
Verified change	$0.00170	$0.00168	$0.00166	$0.00164

On the Free plan, one enriched company result with included parent context is $0.0027; five enriched company results are $0.0095; one company plus two separately delivered relationship records remains $0.0027; a valid Track verified changes run with no delivered changes is $0.001; and one delivered change is $0.0027. The fixed start protects reliable empty and zero-change work, so this Actor does not claim to be cheapest for every tiny run. Against the current selected same-job Baseline reference, this Actor is scoped cheaper from four delivered enriched company results on Free and from three on Bronze, Silver, and Gold, with the compared Standard profile and included parent context. Parent basics, resolved reference labels, Baseline relationship rows, the portfolio summary, failed/blocked inputs, duplicates, first-run seeds, unchanged audit rows, and suppressed records do not add result events. Apify platform compute and storage charges can still apply under your account plan.

✅ Coverage you can trust

Every run writes one explicit coverage state:

• COMPLETE — every requested exact scope was reached within the declared limits.
• FILTERED — company-name matching, a country registry, or another explicit filter bounds what was visible.
• CAPPED — a record, request, byte, runtime, delta, or charge allowance stopped the run.
• PARTIAL — usable official records exist but some requested source targets failed.
• EMPTY_CONFIRMED — the official source positively returned no records for the requested exact scope.
• BLOCKED — official source access was blocked and no trustworthy result was produced.
• FAILED — the input, source contract, parser, or run failed without trustworthy output.

ENDED is never inferred from FILTERED, CAPPED, PARTIAL, BLOCKED, or FAILED. An entity or relationship must remain absent through two consecutive comparable COMPLETE or EMPTY_CONFIRMED snapshots before it can become ENDED.

🔌 API and automation

Send the same JSON through the Apify API, then read the default Dataset, PORTFOLIO_SUMMARY, and OUTPUT records. Route downstream workflows on identityVerdict, renewalStatus, reviewPriority, recommendedNextStep, or verified change flags while retaining OUTPUT.coverage.state with every decision.

An empty Dataset alone is not proof that a run succeeded. Check the run status and coverage state; an empty first Track verified changes result commonly means the comparison snapshot was created successfully.

❓ FAQ and support

Does LOW review priority approve a counterparty?
No. It means the returned GLEIF record has no configured source-based review trigger. It is not sanctions, PEP, adverse-media, legal, or regulatory approval.

Why did a company-name result receive POSSIBLE_MATCH?
Name searches can be ambiguous. Add a country and expected registration number, or switch to the confirmed exact LEI.

Why is there no parent company?
GLEIF may publish a parent, a reporting exception, or neither. The Actor reports which evidence state was reached and never invents a parent or beneficial owner.

Why did the first Track verified changes run return no records?
It creates the comparison snapshot. Later successful same-scope runs can report verified changes.

For support, include the run ID, input without secrets, coverage state, and the resourceBudget section from OUTPUT. Never send account tokens or private credentials.