# Eckari LEI Entity Lookup

> Eckari LEI Entity Lookup is a paid API for AI agents from api.eckari.com, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-11).

Fetches the full GLEIF-authoritative record for a given Legal Entity Identifier (LEI), including legal names, addresses, jurisdiction, entity status, renewal dates, and BIC codes, after validating the LEI checksum.

## Facts

- Endpoint: GET https://api.eckari.com/v1/entities/lei/:lei?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/eckari-lei-entity-lookup-5549230a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_o-Us73P-rHLld3c9x77TO

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 eckari-lei-entity-lookup-5549230a
```

Example prompt: Can you pull the full GLEIF record for LEI 7H6GLXDRUGQFU57RNE97 — I need the legal name, registered address, entity status, and when it's due for renewal?

## When to prefer this

Use this endpoint when you need the canonical, registry-authoritative GLEIF record for a known LEI — specifically when you require legal names, addresses, jurisdiction, entity/registration status, renewal timing, BIC codes, or managing LOU details in a single call. It is preferable to manual GLEIF portal lookups or web scraping because it validates the LEI checksum before charging, returns structured data ready for downstream processing, and is priced per-call at $0.004 USDC via x402.

## Known failure modes

- Malformed LEI (wrong length or character set) — rejected at input validation before payment is charged
- Invalid ISO 7064 MOD 97-10 checksum — rejected with INVALID_INPUT before any upstream call and before settlement
- LEI not found in GLEIF registry — returns a not-found error
- GLEIF upstream unavailable — service may return a 5xx or timeout
- Lapsed or retired LEI — record may be returned but with a non-active entity status

## How this service works

Return the registry-authoritative GLEIF record for a Legal Entity Identifier — legal and previous names, legal and headquarters addresses, jurisdiction, legal form, entity and registration status, renewal dates (with days until renewal), managing LOU, corroboration level, BIC codes and the named local registry. The LEI checksum is validated before any lookup. Use when: Look up everything the LEI register holds for this identifier.

## Output

A structured record containing the entity's legal and previous names, legal and headquarters addresses, jurisdiction, legal form, entity status, registration status, renewal date with days until renewal, the managing LOU name, corroboration level, any associated BIC codes, and the named local registry — all sourced from the GLEIF authoritative register.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "lei"
     ],
     "properties": {
      "lei": {
       "type": "string",
       "pattern": "^[A-Za-z0-9]{18}[0-9]{2}$",
       "maxLength": 20,
       "minLength": 20,
       "description": "20-character ISO 17442 Legal Entity Identifier (18 alphanumerics + 2 check digits). Case-insensitive. The structure is checked before payment, so a wrong-shaped LEI is rejected on the 402 (details.input_validation). The ISO 7064 MOD 97-10 checksum cannot be expressed as a schema pattern and is verified at execution: it fails with INVALID_INPUT before any upstream call and before settlement, so a bad checksum is never charged for."
      }
     },
     "additionalProperties": false
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "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/eckari-lei-entity-lookup-5549230a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.eckari.com](https://www.zero.xyz/host/api.eckari.com/llms.txt)