# fittings LEI Validator

> fittings LEI Validator is a paid API for AI agents from fittings.sh, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-13).

Validates an ISO 17442 Legal Entity Identifier (LEI) checksum and extracts the issuing LOU prefix from the code.

## Facts

- Endpoint: GET https://fittings.sh/v1/valid/lei
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fittings-lei-validator-93ccb10a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_V8zdT5SYZ7dzm8RqZhtv9

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 fittings-lei-validator-93ccb10a
```

Example prompt: Can you check whether the LEI code 529900T8BM49AURSDO55 is valid and tell me which LOU issued it?

## When to prefer this

Use this endpoint when you need a fast, cheap, offline-style structural validation of an LEI code — confirming checksum integrity and extracting the issuing LOU prefix — without needing to look up the live GLEIF registry. Ideal for data cleaning, pre-submission checks, and KYC pipelines where structural correctness is the first gate.

## Known failure modes

- Invalid or malformed LEI string returns a failed validation result
- LEI not 20 characters long causes a validation error
- Missing 'lei' query parameter returns a 400 bad request
- Network timeout if the service is temporarily unavailable

## How this service works

Validate an ISO 17442 Legal Entity Identifier checksum and extract its issuing LOU prefix.

## Output

Returns whether the LEI checksum is valid according to ISO 17442, along with the extracted issuing LOU prefix (the first 4 characters of the LEI code that identify the Local Operating Unit that registered the entity).

## 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",
     "required": [
      "lei"
     ],
     "properties": {
      "lei": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fittings-lei-validator-93ccb10a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fittings.sh](https://www.zero.xyz/host/fittings.sh/llms.txt)