# ChainVerdict LEI Validation API

> ChainVerdict LEI Validation API is a paid API for AI agents from chainverdict.xyz, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Validates a Legal Entity Identifier (LEI) code and returns verification data about the associated legal entity

## Facts

- Endpoint: GET https://chainverdict.xyz/v1/validate/lei/%7Blei%7D
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chainverdict-lei-validation-api-e7000c80
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_npF1UISbO_FRFn7X7pQh-

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 chainverdict-lei-validation-api-e7000c80
```

Example prompt: Can you validate the LEI code 7H6GLXDRUGQFU57RNE97 and tell me if it's active and which legal entity it belongs to?

## When to prefer this

Choose this endpoint when you need programmatic, pay-per-call LEI validation without a subscription, particularly in compliance workflows, KYB/KYC pipelines, pre-trade checks, or regulatory reporting automation. It is well-suited for low-volume or sporadic LEI lookups where a subscription-based LEI data provider would be overkill. Prefer this over manual GLEIF portal lookups when automation is needed.

## Known failure modes

- Invalid or malformed LEI (not 20 characters or wrong format) returns an error response
- LEI not found in GLEIF registry returns a not-found or invalid status
- HTTP 402 returned if payment via x402 protocol is not provided or fails
- Network timeout if the upstream LEI registry is slow to respond
- Rate limiting if too many requests are made in a short period

## How this service works

x402 v2 pay-per-call. Unpaid requests receive HTTP 402 with payment requirements.

## Output

Returns validation status and details for the given 20-character LEI code, including whether the LEI is active, lapsed, or invalid, and associated legal entity information such as registered entity name, jurisdiction, and registration authority data.

## 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"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "lei"
     ],
     "properties": {
      "lei": {
       "type": "string",
       "description": "20-character LEI (ISO 17442)"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chainverdict-lei-validation-api-e7000c80/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chainverdict.xyz](https://www.zero.xyz/host/chainverdict.xyz/llms.txt)
