# Invoket LEI Lookup — Company Legal Entity Identifier Resolution

> Invoket LEI Lookup — Company Legal Entity Identifier Resolution is a paid API for AI agents from api.invoket.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Resolves a Legal Entity Identifier (LEI) or related company identifiers (BIC, ISIN, SIREN, name+country) to verified legal entity data from official sources, with provenance included in every response.

## Facts

- Endpoint: GET https://api.invoket.com/company/lei
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/invoket-lei-lookup-company-legal-entity-identifier-resolution-42d8cf1c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DAxOIyS-izyr7hFQeDf1j

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 invoket-lei-lookup-company-legal-entity-identifier-resolution-42d8cf1c
```

Example prompt: Before we wire the payment, can you look up the legal entity registered under LEI 2138002658CPO1PHIZ39 and confirm it's a valid, active entity with its official name and country?

## When to prefer this

Use this endpoint when an AI agent needs to verify or enrich the identity of a legal entity before executing a financial action, onboarding a counterparty, or validating a financial instrument. It supports multiple authoritative identifier types (LEI, BIC, ISIN, SIREN, name+country) in a single endpoint, includes source provenance, and charges only for successful answers — making it ideal for pre-action compliance checks in automated workflows.

## Known failure modes

- 400 INVALID_CHECKSUM — the provided identifier fails its check digit validation (e.g. malformed LEI, ISIN, or SIREN)
- 400 — zero or two lookup keys provided instead of exactly one
- 404 (unbilled) — well-formed identifier not found in the official reference database
- 400 — name provided without country, or country provided without name
- Identifier format mismatch — e.g. providing a 10-character string as a LEI

## How this service works

The checks your agent runs before it acts: verify a bank account, a phone number, a law in force, the weather or a vehicle — computed from official sources, with provenance in every response. You only pay for answers.

## Output

A structured object containing the resolved legal entity's official data — including LEI, registered legal name, jurisdiction, entity status, and provenance metadata indicating the official source. Returns a 404 (unbilled) if the identifier is well-formed but not found in the reference database, and a 400 with INVALID_CHECKSUM if check digits fail.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "lei"
 ],
 "properties": {
  "lei": {
   "type": "string",
   "description": "20-character LEI (ISO 17442, check digits verified). Provide EXACTLY ONE key: 'lei', 'bic' (8 or 11 characters - both forms are looked up, so the BIC-8 of an IBAN resolves), 'isin' (12 characters, Luhn), 'siren' (9 digits, French bridge) or 'name' plus 'country' (ISO 3166-1 alpha-2, exact normalized equality - no fuzzy search). Zero or two keys is a 400; a failed check digit is a 400 INVALID_CHECKSUM; a well-formed key absent from the reference is a 404, unbilled"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/invoket-lei-lookup-company-legal-entity-identifier-resolution-42d8cf1c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.invoket.com](https://www.zero.xyz/host/api.invoket.com/llms.txt)