LEI Subsidiaries Lookup

List reported direct and ultimate child entities for an LEI in GLEIF, returning names, LEIs and available relationship details.

gleif-l2-children-lookup

Example

Input

{
  "lei": "549300B4X0JHWV0DTD60"
}

Answer

{
  "level": "direct",
  "children": [
    {
      "lei": "335800LYVN89V3RVI889",
      "country": "IN",
      "legal_name": "SPOTIFY INDIA LLP",
      "jurisdiction": "IN"
    }
  ],
  "input_lei": "549300B4X0JHWV0DTD60",
  "paginated": false,
  "legal_name": "SPOTIFY TECHNOLOGY S.A.",
  "data_source": "GLEIF Level 2 (Who Owns Whom)",
  "has_children": true,
  "jurisdiction": "LU",
  "total_children": 2,
  "is_holding_entity": true
}

Inputs

Field	Type	Required	What it is
`lei`	string	No	20-character LEI of the entity to look up children for. Canonical input.
`level`	string	No	Optional. Either "direct" (immediate children) or "ultimate" (full descendant tree). Default direct.
`limit`	integer	No	Optional max number of children to return per page (default 20, max 200).
`company_name`	string	No	Optional fallback input — company name to search GLEIF for if no LEI is known. Resolves to an LEI internally.
`jurisdiction`	string	No	Optional ISO country code (e.g. "LU") to disambiguate name search.

Output fields

How reliably each field appears in a successful answer.

Field	Type	Appears
`level`	string	Always (present in every successful answer)
`children`	array	Always (present in every successful answer)
`input_lei`	string	Always (present in every successful answer)
`paginated`	boolean	Always (present in every successful answer)
`legal_name`	string	Always (present in every successful answer)
`data_source`	string	Always (present in every successful answer)
`has_children`	boolean	Always (present in every successful answer)
`jurisdiction`	string or null	Always (present in every successful answer)
`total_children`	integer	Always (present in every successful answer)
`is_holding_entity`	boolean	Always (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "gleif-l2-children-lookup",
    "inputs": {
      "lei": "549300B4X0JHWV0DTD60"
    },
    "max_price_cents": 5
  }'

{
  "tool": "strale_execute",
  "arguments": {
    "slug": "gleif-l2-children-lookup",
    "inputs": {
      "lei": "549300B4X0JHWV0DTD60"
    },
    "max_price_cents": 5
  }
}

import { Strale } from "straleio";

const strale = new Strale({ apiKey: process.env.STRALE_API_KEY! });
const result = await strale.do({
  capability_slug: "gleif-l2-children-lookup",
  inputs: {
    "lei": "549300B4X0JHWV0DTD60"
  },
  max_price_cents: 5,
});

import os
from straleio import Strale, DoRequest

strale = Strale(api_key=os.environ["STRALE_API_KEY"])
result = strale.do(DoRequest(
    capability_slug="gleif-l2-children-lookup",
    inputs={
        "lei": "549300B4X0JHWV0DTD60",
    },
    max_price_cents=5,
))

Limitations

Coverage is limited to entities that have an LEI
GLEIF L2 only lists children whose LEIs themselves are registered in the GLEIF system. A subsidiary that has not registered for an LEI will not appear in the children list, even if its parent relationship is real and reported elsewhere. Pair with country-registry subsidiary lookups for SMEs.
Direct vs ultimate is the explicit knob
Default is `level=direct` — only immediate children are returned. Pass `level=ultimate` to return the full descendant tree (entities reporting this LEI as their ultimate parent transitively). Ultimate-children pages can be very large for top-of-tree multinationals; use `limit` to bound.
Pagination not yet exposed in output
First page of children is returned with total_children indicating the full count. When total_children > children.length, the `paginated: true` flag signals more results available upstream but the executor returns only the first page. To retrieve subsequent pages a new capability call would be needed (next-page support is a future enhancement).