# Vextorium LEI Validator

> Vextorium LEI Validator 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-19).

Validates a 20-character Legal Entity Identifier (LEI) using local mathematical checksum verification, returning validity status and parsed LEI components.

## Facts

- Endpoint: POST https://api.vextorium.com/v1/lei-validate?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-lei-validator-ed89e077
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_s4mzp6CE0ypTKjzt723BF

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 vextorium-lei-validator-ed89e077 -d '<json body>'
```

Example prompt: Can you validate this LEI code for me: 5493001KJTIIGC8Y1R12? I need to know if the format and checksum are correct and what the component parts are.

## When to prefer this

Use this endpoint when you need fast, cheap, offline-style structural validation of an LEI code (checksum and format) without needing to confirm live GLEIF registry status. It costs only $0.003 per call and requires no external registry lookup, making it ideal for bulk pre-validation, data quality pipelines, or quick sanity checks before querying a live LEI registry. If you need to confirm whether an LEI is actually issued and active, you will need to additionally query GLEIF directly.

## Known failure modes

- LEI string is not exactly 20 characters — validation will fail or return invalid
- Non-alphanumeric characters in LEI — will fail format check
- Valid checksum LEI that is actually unissued or lapsed — endpoint will return valid:true because it does not query GLEIF
- Missing or empty 'lei' field in request body — request rejected
- Network timeout or service unavailability returning non-200 response

## 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 containing: the original LEI string, a boolean indicating whether it passes local mathematical (checksum) validation, the parsed local operating unit (first 4 chars), entity identifier (chars 5–18), control digits (last 2 chars), and a note clarifying that this is local validation only and does not query the GLEIF registry to confirm issuance or active 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",
  "note": "Local mathematical validation. Does not query the GLEIF database (whether the LEI is issued or lapsed).",
  "valid": true,
  "entity": "001KJTIIGC8Y1R",
  "control_digits": "12",
  "local_operating_unit": "5493"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vextorium-lei-validator-ed89e077/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)