# LEI Lookup & Validator - Legal Entity Identifier Data (`kdhan/gleif-lei-lookup`) Actor

Look up and validate LEI codes (ISO 17442 check digits) or search legal entities by name in the public GLEIF database: status, legal form, parent companies, renewal dates and lapsed/overdue signals with evidence. No API key, no personal data.

- **URL**: https://apify.com/kdhan/gleif-lei-lookup.md
- **Developed by:** [Doohan Kim](https://apify.com/kdhan) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 lei records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## LEI Lookup & Validator - Legal Entity Identifier Data

Look up and validate **LEI codes** (Legal Entity Identifiers, ISO 17442) or search legal entities by
**name**, using the official public GLEIF Global LEI Index. One row per legal entity with its status,
legal form, parent companies, renewal dates and plain signals (lapsed, renewal overdue, inactive)
that each show the field and value behind them. No scraping, no API key.

This is a verification tool, not a lead list: **only the city and country of the registered and
headquarters address are returned** - no street, postal code or address lines.

### What you get (one row per LEI)

| Section | Fields |
|---|---|
| Identity | `lei`, `legalName`, `otherNames[]` (name + type), `category`, `legalForm.code`, `jurisdiction`, `registrationNumber`, `registeredAt` (registration authority), `creationDate` |
| Status | `entityStatus` (ACTIVE / INACTIVE), `registrationStatus` (ISSUED / LAPSED / RETIRED / MERGED ...), `entityExpirationDate`, `successors[]` |
| Addresses | `registeredAddress` and `headquartersAddress`: city and country only |
| Dates | `registrationDate`, `lastUpdate`, `nextRenewalDate`, `managingLou`, `corroborationLevel` |
| Parents | `parents.directParent`, `parents.ultimateParent`: `status` = `reported` (parent LEI, name, country, status), `exception` (the entity says why it does not report a parent, e.g. `NATURAL_PERSONS`), `not_reported`, or `unknown` (the request failed) |
| Signals | `signals` (codes), `signalLevel`, `signalDetails[]` - every signal lists source, field, value and an explanation |
| Freshness | `dataAsOf.gleifPublishDate` (GLEIF daily file the answer comes from), `dataAsOf.queriedAt`, `source`, `disclaimer` |

#### Signals

| Signal | Severity | Rule (evidence field) |
|---|---|---|
| `LEI_LAPSED` | medium | `registration.status` is LAPSED: the LEI was not renewed on time. |
| `RENEWAL_OVERDUE` | medium | Status is still ISSUED but `registration.nextRenewalDate` is in the past. |
| `ENTITY_INACTIVE` | high | `entity.status` is INACTIVE. |
| `ENTITY_EXPIRED` | high | An `entity.expiration` date or reason is recorded. |
| `SUCCESSOR_ENTITY` | medium | A successor entity is recorded (merger / takeover). |
| `LEI_RETIRED`, `LEI_ANNULLED`, `LEI_CANCELLED`, `LEI_MERGED`, `LEI_DUPLICATE`, `LEI_TRANSFERRED` | medium | `registration.status` has that value. |
| `LEI_PENDING`, `LEI_STATUS_OTHER` | low | Pending or unusual registration status. |
| `NOT_FULLY_CORROBORATED` | low | `registration.corroborationLevel` is not FULLY_CORROBORATED. |

A signal is a reason to look closer, not a verdict. `signalLevel` is the highest severity found;
`none` means **no signal was found in these fields** - it is not a guarantee about the company -
and it becomes `unknown` if a request failed.

#### Sole proprietors

For records of category `SOLE_PROPRIETOR` (an individual trading under their own name) the legal
name is kept because it is the registered entity name, but the city, other names and registration
number are not returned.

#### No silent failures

- An input that matches nothing is returned as `found: false` with a `reason` (not charged).
- A LEI with a wrong format or wrong ISO 17442 check digits is returned as `found: false` without a lookup.
- If GLEIF could not be reached, the row has `found: null` and an `error` - it does **not** claim the
  entity does not exist.
- If only the parent lookup failed, the LEI data is still returned, the parent `status` is `unknown`,
  `sectionErrors.parents` explains why and `signalLevel` is not reported as `none`.

### Input

```json
{
  "leis": ["HWUPKR0MPOU8FGXBT394"],
  "companyNames": ["Bloomberg Finance L.P."],
  "country": "US",
  "maxResultsPerName": 5,
  "includeParents": true
}
```

All fields are optional. With an empty input the Actor looks up an example LEI (Apple Inc.).
LEIs may contain spaces or hyphens and any letter case. Name search lists exact name matches
(case and punctuation ignored, also against other and alternative-language names) first, then partial
matches, up to `maxResultsPerName` (1-20); `country` (two letters) filters on the legal address
country for name searches. Entities registered in a local script (for example Japanese companies) are
found through their English alternative name via a second, full-text search. A malformed input fails
the run with an English error message.

### Pricing

Pay-per-event, event name `lei-record` (one LEI record returned). Inputs that are not found, or that
fail, are not charged. Each LEI also costs about 2 to 4 extra requests when `includeParents` is on.

### Data source and terms

- **GLEIF Global LEI Index** public API (`api.gleif.org/api/v1`), queried live with a pause between
  requests and exponential back-off on throttling or server errors. GLEIF publishes the data daily
  (`dataAsOf.gleifPublishDate`).
- GLEIF states: "The data on GLEIF's website is provided under a Creative Commons (CC0) license"
  (gleif.org/en/about/open-data) and, in its LEI Data Terms of Use, "The data available through the
  Access Service are provided under the CC0 licence". Those terms ask users not to create the
  impression that this product is provided or supported by GLEIF or any LOU, and the data is provided
  "as is" without warranty. **This Actor is not provided, endorsed or authorized by GLEIF.**
- Not legal or financial advice. Confirm important findings with the official GLEIF record.

# Actor input Schema

## `leis` (type: `array`):

20-character Legal Entity Identifiers, for example HWUPKR0MPOU8FGXBT394. The ISO 17442 check digits are verified.

## `companyNames` (type: `array`):

Legal entity names to search. Exact name matches are listed first, then partial matches.

## `country` (type: `string`):

Optional two-letter country code (ISO 3166-1), for example US. Applies to name searches (legal address country).

## `maxResultsPerName` (type: `integer`):

Upper limit of LEI records returned for each name. You are charged per LEI record returned.

## `includeParents` (type: `boolean`):

Also look up the direct and ultimate parent (2 to 4 extra requests per LEI).

## Actor input object example

```json
{
  "leis": [
    "HWUPKR0MPOU8FGXBT394"
  ],
  "maxResultsPerName": 5,
  "includeParents": true
}
```

# Actor output Schema

## `records` (type: `string`):

Entity identity, LEI registration status, dates, parents, signals with evidence, data freshness and disclaimer.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "leis": [
        "HWUPKR0MPOU8FGXBT394"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("kdhan/gleif-lei-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "leis": ["HWUPKR0MPOU8FGXBT394"] }

# Run the Actor and wait for it to finish
run = client.actor("kdhan/gleif-lei-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "leis": [
    "HWUPKR0MPOU8FGXBT394"
  ]
}' |
apify call kdhan/gleif-lei-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kdhan/gleif-lei-lookup"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/GWFJL6gT6VxcjDeJK/builds/5LunVFEcMsoUrl5on/openapi.json