# GLEIF LEI (Legal Entity Identifier) Extractor (`xtracto/gleif-lei`) Actor

Extract Legal Entity Identifier records from GLEIF — one legal entity per row, with legal name, address, registration, BIC/MIC. 3.3M+ entities for KYC/AML and entity resolution. Public data.

- **URL**: https://apify.com/xtracto/gleif-lei.md
- **Developed by:** [Farhan Febrian Nauval](https://apify.com/xtracto) (community)
- **Categories:** Lead generation, Other
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## GLEIF LEI (Legal Entity Identifier) Extractor

Extract **Legal Entity Identifier** records from **GLEIF** — one legal entity per row, with legal name, registered address, registration details, and BIC/MIC codes. The global reference set for **KYC/AML, counterparty/entity resolution, and supply-chain due diligence**.

Built for compliance and onboarding teams, fintech/regtech, data vendors, and analysts who need a clean company master.

***

### Why use this actor

- **3.3M+ entities** (verified) — pull the whole registry, or a slice by country and status.
- **One entity per row**, with a flat header (`lei`, `legal_name`, `country`, `city`, `entity_status`, `registration_status`) plus the **full raw GLEIF attributes** preserved.
- **No login, no key.** Clean JSON:API.

### Input

| Field | Type | Description |
| --- | --- | --- |
| `country` | text | Optional ISO-2 of the legal address (US, GB, DE, ID…). |
| `entityStatus` | **dropdown** | Any / Active / Inactive / Null. |
| `registrationStatus` | **dropdown** | Any / Issued / Lapsed / Merged / Retired / … |
| `pageSize` | int | 1–200 (default 200). |
| `maxItems` | int | 0 = all matching. |

`entityStatus` and `registrationStatus` are **pick-lists**; `country` is a free ISO-2 code (documented) since the full country set is large.

### Output — `LEI_RECORD`

Envelope + `recordType: "LEI_RECORD"` + flat header, then the raw GLEIF `attributes` object:

```json
{
  "_input": "country=US; entity=ACTIVE",
  "_source": "S1-gleif",
  "_scrapedAt": "2026-06-03T10:00:00Z",
  "recordType": "LEI_RECORD",
  "lei": "5493001KJTIIGC8Y1R12",
  "legal_name": "BLOOMBERG L.P.",
  "country": "US", "city": "New York",
  "entity_status": "ACTIVE",
  "registration_status": "ISSUED",
  "entity": { "...": "..." },
  "registration": { "...": "..." },
  "bic": null, "mic": null
}
```

### How it works

1. Your country and status filters are applied to the search.
2. The actor automatically pages through all matching results (up to 200 per request).
3. Each entity streams into the dataset.

### Known limits

- Public data — no account needed, runs from any connection. Backs off on HTTP 429.
- Page size capped at 200 by GLEIF → large unfiltered pulls are many requests; filter by country/status to scope.
- **Verified live 2026-06-03:** total 3,331,178; JSON:API `data[].attributes` with `lei`, `entity`, `registration`, `bic`, `mic`.

# Actor input Schema

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

Optional ISO-2 country code of the entity's legal address, e.g. US, GB, DE, ID. Leave blank for all countries.

## `entityStatus` (type: `string`):

Optional filter on the entity's status.

## `registrationStatus` (type: `string`):

Optional filter on the LEI registration status.

## `pageSize` (type: `integer`):

How many records to fetch per request.

## `maxItems` (type: `integer`):

Maximum records to return (0 = all matching). The example pulls 200; set 0 to page the full result set (e.g. 354k+ for country=US).

## `proxyConfiguration` (type: `object`):

Not required (public API).

## Actor input object example

```json
{
  "country": "US",
  "entityStatus": "",
  "registrationStatus": "",
  "pageSize": 200,
  "maxItems": 200,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# 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 = {
    "country": "US",
    "maxItems": 200
};

// Run the Actor and wait for it to finish
const run = await client.actor("xtracto/gleif-lei").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 = {
    "country": "US",
    "maxItems": 200,
}

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

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

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

```

## CLI example

```bash
echo '{
  "country": "US",
  "maxItems": 200
}' |
apify call xtracto/gleif-lei --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=xtracto/gleif-lei",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/NTeSVZaKUYwkllG4W/builds/R8mmkwmfAFo0cctLI/openapi.json