GLEIF LEI API

Name: GLEIF LEI API
Brand: GLEIF LEI API
Availability: InStock

✓ Official Vendor SpecData EnrichmentCompany Datanone8 EndpointsREST

For Agents

Validate and enrich legal entity records by looking up Legal Entity Identifiers (LEI), parent relationships, and issuing LOUs from the GLEIF reference dataset.

Connect the GLEIF LEI API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GLEIF LEI API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with GLEIF LEI API.

Look up the LEI record for a legal entity by exact LEI code via /lei-records/{lei}

Search for entities by name, country, or status across the global LEI registry

Resolve the managing Local Operating Unit (LOU) for a given LEI

Resolve the LEI issuer record for a given LEI

GET STARTED

Start building with GLEIF LEI API

Explore with Jentic

View OpenAPI Document

The GLEIF LEI API exposes the Global Legal Entity Identifier Foundation's reference dataset — every issued Legal Entity Identifier (LEI), the legal entity record behind it, the relationships to ultimate and direct parents, the managing Local Operating Unit (LOU), and field-level modification history. Agents can validate counterparties, enrich KYC and KYB workflows, and trace ownership relationships across the global LEI registry. The API is open, requires no authentication, and is served from api.gleif.org.

Use Cases

Patterns agents use GLEIF LEI API for, with concrete tasks.

★ Counterparty KYB Verification

Verify a corporate counterparty during onboarding by resolving its LEI to the GLEIF reference record. GET /lei-records/{lei} returns the legal name, registration jurisdiction, status, and the next renewal date — enough to confirm the entity exists, is current, and matches the data the customer supplied.

Fetch /lei-records/5493001KJTIIGC8Y1R12 and return legalName, jurisdiction, registrationStatus, and nextRenewalDate

Beneficial Ownership Tracing

Trace a legal entity's parent and ultimate parent for AML or sanctions screening. The relationship endpoints under /lei-records/{lei} expose direct and ultimate parent LEIs, which an agent can recursively resolve through GLEIF until it reaches the top of the ownership chain.

Starting from LEI X, fetch the ultimate parent LEI, resolve it via /lei-records/{lei}, and return the parent's legalName

Counterparty Search Autocomplete

Power an autocomplete dropdown when a user is typing a legal entity name into a counterparty form. /autocompletions returns matching candidates by name fragment with their LEIs, so the agent can return a structured list rather than a free-text guess.

Call /autocompletions with field=fulltext and q='Goldman' and return up to 5 (legalName, lei) pairs

AI Agent KYC Enrichment

Use Jentic to let an AI agent enrich freshly added counterparty rows in a CRM. The agent issues an intent like 'look up an LEI by company name', Jentic resolves the GLEIF /autocompletions and /lei-records/{lei} calls, and the agent writes the legal name, jurisdiction, and parent LEI back to the CRM record.

Through Jentic, autocomplete 'Acme Corp', resolve the top LEI via /lei-records/{lei}, and return jurisdiction and registrationStatus

Key Endpoints

8 endpoints — the gleif lei api exposes the global legal entity identifier foundation's reference dataset — every issued legal entity identifier (lei), the legal entity record behind it, the relationships to ultimate and direct parents, the managing local operating unit (lou), and field-level modification history.

METHOD

PATH

DESCRIPTION

GET

/lei-records

Search LEI records with filters

GET

/lei-records/{lei}

Fetch a single LEI record

GET

/lei-records/{lei}/managing-lou

Get the managing LOU for an LEI

GET

/lei-records/{lei}/lei-issuer

Get the issuer of an LEI

GET

/lei-records/{lei}/field-modifications

Field-level modification history

GET

/autocompletions

Autocomplete entity names

GET

/lei-issuers

List accredited LEI issuers

GET

/lei-records

Search LEI records with filters

GET

/lei-records/{lei}

Fetch a single LEI record

GET

/lei-records/{lei}/managing-lou

Get the managing LOU for an LEI

GET

/lei-records/{lei}/lei-issuer

Get the issuer of an LEI

GET

/lei-records/{lei}/field-modifications

Field-level modification history

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The GLEIF LEI API requires no credential, so Jentic simply orchestrates the call without storing a secret. For agents that mix GLEIF with credentialed APIs (CRM, sanctions feeds), the other secrets are still held in the encrypted MAXsystem vault.

Intent-based discovery

Agents search by intent (e.g. 'look up an LEI') and Jentic returns the matching GLEIF operation with its query parameter schema, so the agent can call /lei-records/{lei} or /autocompletions without reading docs.

Time to first call

Direct GLEIF integration: a few hours to wire up the JSON:API-style envelopes and pagination. Through Jentic: under 15 minutes — search, load, execute.

FAQs

Specific to using GLEIF LEI API through Jentic.

What authentication does the GLEIF LEI API use?

The GLEIF LEI API is open and requires no API key or token; the spec defines no security scheme. Through Jentic the API can still be called via the standard search/load/execute flow without provisioning a credential, which is useful when wiring up KYC enrichment for an agent.

Can I look up a Legal Entity Identifier with the GLEIF API?

Yes. GET /lei-records/{lei} returns the canonical record for a single LEI, including legal name, registration jurisdiction, status (ISSUED, LAPSED, etc.), and the next renewal date. Use it as the source of truth for validating that an LEI on a counterparty form is real and current.

What are the rate limits for the GLEIF LEI API?

GLEIF asks integrators to be considerate and avoid sustained bursts above a few requests per second from a single source. There is no documented numeric cap; if you receive HTTP 429 or 503 in batch enrichment, back off and process more slowly or distribute work across IPs.

How do I autocomplete a company name through Jentic with GLEIF?

Search Jentic for 'autocomplete legal entity name', load GET /autocompletions, and execute with field=fulltext and q set to the partial name. The response returns matching LEIs and legal names that an agent can present to the user before resolving the full record via /lei-records/{lei}.

Can the GLEIF API return parent and ultimate-parent relationships?

Yes. The /lei-records/{lei} response embeds direct-parent and ultimate-parent relationship links, and the related-records endpoints under that path return the full relationship records. An agent can recurse upward to build the ownership chain for AML or sanctions checks.

Is the GLEIF LEI API free?

Yes. GLEIF publishes the LEI dataset as an open data product under a CC0-style licence, and the v1 API at api.gleif.org is freely accessible. There is no commercial paywall on read endpoints; the cost is in obtaining and renewing the LEIs themselves through accredited LOUs.