# GLEIF LEI Lookup

> GLEIF LEI Lookup is a paid API for AI agents from pyfile-agent.taile3ff35.ts.net:10000, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Looks up Legal Entity Identifier (LEI) records from the GLEIF registry by company name or LEI code

## Facts

- Endpoint: GET https://pyfile-agent.taile3ff35.ts.net:10000/data/lei
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gleif-lei-lookup-0f0fa5d7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yALbQYc2y0VLG2voyF0Ft

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-lookup-0f0fa5d7
```

Example prompt: Can you look up the GLEIF LEI record for Goldman Sachs and tell me its LEI code, registration status, and country?

## When to prefer this

Use this endpoint when you need authoritative legal entity identification data from the official GLEIF registry — particularly for KYC/AML compliance, counterparty verification, regulatory reporting, or financial due diligence. Prefer this over general web search when you need structured, standardized LEI data. For combined OFAC + LEI + SEC due diligence in a single call, use the composite counterparty endpoint instead.

## Known failure modes

- Company name too generic returns many results with low precision
- LEI code not found returns empty results array
- Misspelled company name may return no results
- GLEIF registry temporarily unavailable causes request failure
- Non-existent or invalid LEI code returns empty results

## How this service works

GLEIF Legal Entity Identifier lookup by company name or LEI code. ?name=Apple or ?lei=<code>

## Output

Returns a list of matching legal entities from the GLEIF registry, each containing the LEI code, legal name, city, country, and entity status (e.g. ACTIVE, LAPSED). Includes a total count of matches and the original query string.

## 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",
     "properties": {
      "name": {
       "type": "string"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "query": {
     "type": "string"
    },
    "total": {
     "type": "integer"
    },
    "results": {
     "type": "array",
     "items": {
      "type": "object",
      "properties": {
       "lei": {
        "type": "string"
       },
       "city": {
        "type": "string"
       },
       "status": {
        "type": "string"
       },
       "country": {
        "type": "string"
       },
       "legal_name": {
        "type": "string"
       }
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gleif-lei-lookup-0f0fa5d7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pyfile-agent.taile3ff35.ts.net:10000](https://www.zero.xyz/host/pyfile-agent.taile3ff35.ts.net%3A10000/llms.txt)