# GLEIF LEI Company Registry Lookup — official Access Service, no (`pappy-dev/gleif-lei-registry`) Actor

Look up any company's Legal Entity Identifier (LEI) record via GLEIF's official public Access Service: legal name, status, jurisdiction, legal form, HQ country/city, managing LOU, registration/renewal dates. CC0 licensed open data, no login. Useful for KYB / due-diligence.

- **URL**: https://apify.com/pappy-dev/gleif-lei-registry.md
- **Developed by:** [Backyard Tools](https://apify.com/pappy-dev) (community)
- **Categories:** Business, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 lei record scrapeds

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?

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 Company Registry Lookup — official Access Service, no login

Search the full Global LEI Index — every company that has ever registered a **Legal Entity
Identifier (LEI)** — through GLEIF's own public Access Service. No login, no proxies: this is
the same API GLEIF documents and publishes for exactly this kind of lookup.

Open data, CC0 1.0 licensed: free to use commercially, no permission or attribution required
(source: GLEIF LEI Data Terms of Use). This actor is not affiliated with or endorsed by GLEIF —
it's an independent client of their public API.

### Tested (2026-09-02)

| Search | Records found | Time |
|---|---:|---:|
| `OpenAI` | 19 | 1.56s |
| `Tesla` | 87 | 2.43s |
| `Shopify` | 9 | 1.23s |

A search matches on legal name (partial match), so one query can return every registered
entity carrying that name — parent companies, subsidiaries, and unrelated companies that
happen to share a word.

### GLEIF LEI API — input

```json
{
  "targets": ["OpenAI", "Tesla"],
  "maxItems": 2000
}
```

Each target is a company legal name (or part of one). A name with no LEI registrations
simply returns 0 items (no charge).

### GLEIF LEI API — output fields

One dataset item per LEI record:

| Field | |
|---|---|
| `lei` | the 20-character Legal Entity Identifier |
| `legal_name` | registered legal name |
| `entity_status` | `ACTIVE` / `INACTIVE` |
| `category` | e.g. `FUND`, `GENERAL` |
| `jurisdiction` | ISO country/region code of incorporation |
| `legal_form_id` | ISO 20275 legal form code |
| `hq_country` / `hq_city` | headquarters country and city (no street address — company-identifying fields only, no personal data) |
| `registration_status` | `ISSUED` / `LAPSED` / `RETIRED` / etc. |
| `managing_lou` | the Local Operating Unit (issuer) managing this LEI |
| `initial_registration_date` / `last_update_date` / `next_renewal_date` | LEI lifecycle dates |

No personal data: LEI records identify companies and funds, not individuals.

### Use Cases

- **KYB (Know Your Business) onboarding**: verify a counterparty's legal entity status
  and jurisdiction before onboarding
- **Counterparty / trade-finance risk screening**: check LEI status (`ACTIVE` /
  `LAPSED` / `RETIRED`) before extending credit
- **Regulatory compliance**: confirm a vendor holds the ACTIVE LEI required by
  regulations such as EU SFTR or MiFID II
- **Corporate structure research**: map legal names to jurisdictions and registration
  history for due diligence

### Why this over GLEIF's own website

gleif.org's search is built for one lookup at a time. This actor runs a batch of company
names in one call and hands back structured rows — for KYB checks, counterparty screening,
or due-diligence pipelines that need this in a dataset, not a web page.

### Pricing

Pay per event: **$2.00 per 1,000 LEI records** collected. Nothing else.

# Actor input Schema

## `targets` (type: `array`):

検索したい会社の正式名称、または部分一致する名前（例: OpenAI, Tesla）。GLEIF の登録名でマッチする全レコードを返す

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

1 run で取得する最大件数

## Actor input object example

```json
{
  "targets": [
    "OpenAI"
  ],
  "maxItems": 2000
}
```

# Actor output Schema

## `items` (type: `string`):

取得した各件（type=item）と、選択した分析の結果（type=analysis）

## `overview` (type: `string`):

件数・平均評点・期間・ネガティブ比率（下側信頼限界つき）

# 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 = {
    "targets": [
        "OpenAI"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("pappy-dev/gleif-lei-registry").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 = { "targets": ["OpenAI"] }

# Run the Actor and wait for it to finish
run = client.actor("pappy-dev/gleif-lei-registry").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 '{
  "targets": [
    "OpenAI"
  ]
}' |
apify call pappy-dev/gleif-lei-registry --silent --output-dataset

```

## MCP server setup

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

```

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/8NBt2Skwc3YLTTfQm/builds/wJJeYjdd2dsTRUxpT/openapi.json