# LEI Lookup — Legal Entity Identifier by Code or Name

> LEI Lookup — Legal Entity Identifier by Code or Name is a paid API for AI agents from mcpfax-utility.bowling-anthony.workers.dev, paid per call via x402, $0.008/call, status unknown (last checked 2026-09-15).

Retrieves Legal Entity Identifier (LEI) records for a company by LEI code or entity name, returning structured entity data from the GLEIF registry.

## Facts

- Endpoint: GET https://mcpfax-utility.bowling-anthony.workers.dev/v1/lei
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lei-lookup-legal-entity-identifier-by-code-or-name-b399dbfc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_m_PcEb8DWm0pkbL_YapgH

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 lei-lookup-legal-entity-identifier-by-code-or-name-b399dbfc
```

Example prompt: Can you look up the LEI record for JPMorgan Chase Bank, N.A. — I need its LEI code, registration status, and legal jurisdiction?

## When to prefer this

Use this endpoint when you need authoritative Legal Entity Identifier data from the GLEIF registry, particularly for compliance workflows (KYC, AML, trade reporting), counterparty verification, or resolving a company name to a standardized LEI code. Prefer this over general company lookup APIs when the use case specifically requires the ISO 17442 LEI standard used in financial regulation.

## Known failure modes

- Entity name not found in GLEIF registry — returns empty results or 404
- Invalid or malformed LEI code format — returns validation error
- Ambiguous entity name matching multiple records — returns a list requiring disambiguation
- LEI record exists but is lapsed or retired — returned but flagged with non-active status
- GLEIF API upstream timeout — returns 503 or gateway error

## How this service works

LEI lookup — Legal Entity Identifier record by LEI code or entity name.

## Output

Returns a structured GLEIF LEI record including the LEI code, official legal entity name, registration status (active/lapsed/retired), legal address, headquarters address, jurisdiction of formation, entity category (fund, corporate, etc.), and registration/renewal dates.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lei-lookup-legal-entity-identifier-by-code-or-name-b399dbfc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcpfax-utility.bowling-anthony.workers.dev](https://www.zero.xyz/host/mcpfax-utility.bowling-anthony.workers.dev/llms.txt)