# LEI Validator (ISO 17442, Local)

> LEI Validator (ISO 17442, Local) is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-16).

Validates a Legal Entity Identifier (LEI) for correct 20-character format and mod-97 check digits, returning parsed LOU prefix, entity part, and control digits — computed locally without querying GLEIF.

## Facts

- Endpoint: POST https://api.vextorium.com/validar-lei-pago?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lei-validator-iso-17442-local-1755b57b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_41tyvFNtnTnVoUUPXJYxe

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-validator-iso-17442-local-1755b57b -d '<json body>'
```

Example prompt: Can you validate this LEI for me — 5493001KJTIIGC8Y1R12 — and tell me whether the format and check digits are correct, and what the LOU prefix and entity part are?

## When to prefer this

Use this endpoint when you need fast, free-of-network-latency format and checksum validation of an LEI without requiring a live GLEIF database query. Ideal for pre-screening LEIs in bulk data pipelines, onboarding flows, or developer testing where you only need mathematical correctness (not registration status). If you need to confirm whether an LEI is actually registered, active, or linked to a real entity in the GLEIF registry, you need a separate GLEIF API call.

## Known failure modes

- LEI is not exactly 20 characters — validation fails with invalid format
- LEI contains non-alphanumeric characters — format check fails
- Mod-97 check digit does not match — returns valido: false
- Missing 'lei' field in request body — likely returns a 400 or error response
- Correctly formatted but unregistered or expired LEI — returned as valid (limitation: no GLEIF lookup)

## How this service works

Validate a Legal Entity Identifier (LEI, ISO 17442): 20-character format and mod-97 check digits, split into LOU prefix and entity part. Computed locally; does not query GLEIF.

## Output

Returns a JSON object with: the original LEI, a boolean 'valido' indicating whether the LEI passes format and mod-97 check-digit validation, the 'unidad_operativa_local' (4-character LOU prefix), the 'entidad' (14-character entity code), the 2-digit 'digitos_control', and a 'nota' clarifying that this is local mathematical validation only and does not confirm GLEIF registration or expiry status.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "lei": {
   "type": "string",
   "description": "20-character LEI"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "lei": "5493001KJTIIGC8Y1R12",
  "nota": "Validación matemática local. No consulta la base de datos GLEIF (si el LEI está emitido o caducado).",
  "valido": true,
  "entidad": "001KJTIIGC8Y1R",
  "digitos_control": "12",
  "unidad_operativa_local": "5493"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lei-validator-iso-17442-local-1755b57b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)