# GLEIF LEI Registry Lookup

> GLEIF LEI Registry Lookup is a paid API for AI agents from agent402.tools, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-13).

Look up a legal entity in the official GLEIF registry by LEI code or company name, returning full entity details including legal name, jurisdiction, legal form, addresses, registration status, and parent entities.

## Facts

- Endpoint: POST https://agent402.tools/api/lei-lookup
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gleif-lei-registry-lookup-8aa21c97
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_x9VafP_AJQLKEm-XmC4QK

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability gleif-lei-registry-lookup-8aa21c97 -d '<json body>'
```

Example prompt: Can you look up the legal entity details for LEI code 7H6GLXDRUGQFU57RNE97 in the GLEIF registry — I need the company's legal name, jurisdiction, registration status, and who its ultimate parent is?

## When to prefer this

Use this endpoint when you need authoritative, official legal entity data from the global GLEIF registry — especially for KYC/KYB workflows, compliance checks, corporate ownership research, or verifying LEI codes. Prefer this over commercial company databases when you need the canonical LEI record, including parent entity linkage, or when working with regulated financial entities required to have LEIs.

## Known failure modes

- Invalid LEI format (not 20 alphanumeric characters) — validation error
- LEI not found in GLEIF registry — empty or 404 result
- Company name search returns no candidates — empty ranked list
- Ambiguous company name returns large candidate list requiring disambiguation
- Network or upstream GLEIF API unavailability — service error
- Payment failure (insufficient USDC) — 402 Payment Required

## How this service works

Look up a legal entity in the official GLEIF registry. Pass a 20-character LEI for the full record - legal name, jurisdiction, legal form, addresses, registration status, and the reported direct + ultimate parent entities - or pass a company name to fulltext-search the registry and get ranked candidate LEIs. Unknown LEIs return {found:false}; parents that aren't reported return null. Official registry data, keyless.

## Output

Returns the full GLEIF record for the entity: legal name, jurisdiction, legal form, registered and headquarters addresses, registration status (active/lapsed/etc.), and reported direct and ultimate parent entity identifiers and names.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "lei": {
   "type": "string",
   "description": "20-character alphanumeric Legal Entity Identifier (exact record lookup)."
  },
  "name": {
   "type": "string",
   "description": "Company name to fulltext-search instead (ranked candidate list). Provide lei OR name."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "found": true,
  "record": {
   "lei": "HWUPKR0MPOU8FGXBT394",
   "legalName": "APPLE INC.",
   "entityStatus": "ACTIVE",
   "jurisdiction": "US-CA",
   "legalAddress": {
    "city": "Cupertino",
    "region": "US-CA",
    "country": "US"
   },
   "registration": {
    "status": "ISSUED",
    "nextRenewal": "2026-10-13T00:31:58Z"
   }
  },
  "source": "api.gleif.org",
  "parents": {
   "direct": null,
   "ultimate": null
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gleif-lei-registry-lookup-8aa21c97/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent402.tools](https://www.zero.xyz/host/agent402.tools/llms.txt)