# fittings LEI Ownership Hierarchy

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

Returns the GLEIF-sourced ownership hierarchy for a given LEI: direct parent, ultimate parent, reporting exceptions, and known direct subsidiaries.

## Facts

- Endpoint: GET https://fittings.sh/v1/lei/hierarchy
- Price: $0.0074/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fittings-lei-ownership-hierarchy-d625ac60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KU44KheqITnTjZRR9yJ8l

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-ownership-hierarchy-d625ac60
```

Example prompt: Can you pull the full ownership hierarchy for LEI 529900T8BM49AURSDO55 — I need the direct parent, ultimate parent, and up to 15 direct subsidiaries?

## When to prefer this

Choose this endpoint when you need authoritative GLEIF-sourced corporate ownership data for a specific LEI, particularly for KYB/KYC workflows, regulatory compliance, due diligence, or counterparty risk assessment. It is preferred over general corporate registry lookups when the ISO 17442 LEI is known and GLEIF relationship data is the required authoritative source. It is not suitable for searching entities by name without a known LEI.

## Known failure modes

- Invalid or malformed LEI (not 20 characters, bad checksum) returns a validation error
- LEI exists but has no registered parent (orphan entity) returns null parent fields
- GLEIF relationship data not yet published for entity returns empty hierarchy
- limit parameter out of range (below 1 or above 25) returns a 400 error
- GLEIF upstream data lag may mean recently registered LEIs have no hierarchy data yet

## How this service works

GLEIF 'who owns whom' for an LEI: direct and ultimate accounting parent, any reporting exception, and known direct subsidiaries.

## Output

Returns a structured JSON object containing the entity's direct accounting parent (with LEI and name), ultimate accounting parent (with LEI and name), any GLEIF reporting exception with reason, and a paginated list of known direct subsidiaries (each with LEI, name, and relationship type), all sourced from GLEIF relationship records.

## 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",
       "description": "20-character ISO 17442 identifier"
      },
      "limit": {
       "type": "number",
       "description": "Direct children to return, 1-25, default 10"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fittings-lei-ownership-hierarchy-d625ac60/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)