How do I get the parent counts first?

LEI Lookup company returns direct_children_total and ultimate_children_total for one LEI.

Do I pay for lookups that come back empty?

No. You are charged per result, so a request that finds nothing costs nothing. Testing this against a messy list is free to get wrong.

What does a lookup cost?

1 point per returned record, which is $1 per 1,000, and only records that come back are charged. Points come out of your monthly plan allowance, so there is no separate per-country contract.

Corporate registry

LEI Subsidiaries API and MCP — Direct and Ultimate Children by LEI

Send the LEI of a parent entity and get its subsidiaries from the public LEI register at lei-lookup.com, direct and ultimate: each row has the child's LEI, name, the type of relationship and a link to its record. The flags direct_child and ultimate_child say how the child is connected.

Run it in the app Read the API docs

You send: a 20-character LEI code, plus optional max_items and start_page
You get back: Direct and ultimate subsidiaries: LEI, name, type of relationship and link
Coverage: Records on LEI Lookup (lei-lookup.com).
Price: 1 point per returned record — $1 per 1,000; Billed per record actually returned, capped by max_items. A request that returns nothing costs nothing.

Comparison

Ways to get this data

Three approaches teams use today, and where each one runs into trouble.

Approach	What it takes	Cost	Trade-off
LEI Lookup (lei-lookup.com) directly	Open the entity on LEI Lookup (lei-lookup.com) and follow each link	Usually free, sometimes per-document	A different interface, language and data shape for every country you add
Collecting it yourself	Build and host a crawler per register, then keep each one alive	Infrastructure and maintenance	Registers change their pages without warning, and nobody is on the hook when yours breaks
NeuralVerge	One request, the same shape as every other source in the catalog	$1 per 1,000, misses not billed	Covers the register named on this page — other countries are separate sources with the same request format

Response

What you get back

Every field in the example response below.

Field	Type	Description
`total_items`	number	How many records are in this response.
`first_item`	object	The first record, repeated from items for quick access.
`items`	array	The subsidiaries returned.
`total_found`	number	How many matches the register reported for the query.
`page_count`	number	How many result pages were read for this request.
`blocked`	boolean	True if the register could not be read; false on a normal run.
`items[].id`	string	Parent and child LEI joined with a hyphen.
`items[].registration_number, items[].lei`	string	LEI of the subsidiary.
`items[].name`	string	Name of the subsidiary.
`items[].relation`	string	Relationship type, e.g. direct_and_ultimate_child.
`items[].direct_child`	boolean	True if it is a direct child.
`items[].ultimate_child`	boolean	True if it is an ultimate child.
`items[].parent_lei`	string	LEI of the parent you asked about.
`items[].url`	string	Link to the child's record on lei-lookup.com.
`proxy_traffic_bytes`	number	Traffic used by the run, in bytes.
`session_id`	string	Id of this run, for tracing.
`kind`	string	The source that produced the response.
`human`	string	A short readable summary of the result.
`total_points`	number	Points charged for this run.

Response

Example response

A real response, as returned.

{
  "session_id": "11111111-1111-1111-1111-111111111111",
  "kind": "lei_lookup_company_relationships",
  "company": "7LTWFZYICNSX8D621K86",
  "company_id": "7LTWFZYICNSX8D621K86",
  "max_items": 2,
  "start_page": 1,
  "partial": false,
  "human": "# LEI Lookup (lei-lookup.com) — company relationships\n\n- **Company:** 7LTWFZYICNSX8D621K86\n- **Results:** 2 of 479 found\n- **Proxy traffic:** 191.0 KB",
  "machine": {
    "total_items": 2,
    "first_item": {
      "id": "7LTWFZYICNSX8D621K86-2138003FL72FCO53LM68",
      "registration_number": "2138003FL72FCO53LM68",
      "lei": "2138003FL72FCO53LM68",
      "name": "HISTRIA INVERSIONES DESIGNATED ACTIVITY COMPANY",
      "relation": "direct_and_ultimate_child",
      "direct_child": true,
      "ultimate_child": true,
      "parent_lei": "7LTWFZYICNSX8D621K86",
      "url": "https://www.lei-lookup.com/record/2138003FL72FCO53LM68/"
    },
    "items": [
      {
        "id": "7LTWFZYICNSX8D621K86-2138003FL72FCO53LM68",
        "registration_number": "2138003FL72FCO53LM68",
        "lei": "2138003FL72FCO53LM68",
        "name": "HISTRIA INVERSIONES DESIGNATED ACTIVITY COMPANY",
        "relation": "direct_and_ultimate_child",
        "direct_child": true,
        "ultimate_child": true,
        "parent_lei": "7LTWFZYICNSX8D621K86",
        "url": "https://www.lei-lookup.com/record/2138003FL72FCO53LM68/"
      },
      {
        "id": "7LTWFZYICNSX8D621K86-213800D3OXAL3N7T1S19",
        "registration_number": "213800D3OXAL3N7T1S19",
        "lei": "213800D3OXAL3N7T1S19",
        "name": "Tagus - Sociedade de Titularização de Créditos, S.A.",
        "relation": "direct_and_ultimate_child",
        "direct_child": true,
        "ultimate_child": true,
        "parent_lei": "7LTWFZYICNSX8D621K86",
        "url": "https://www.lei-lookup.com/record/213800D3OXAL3N7T1S19/"
      }
    ],
    "total_found": 479,
    "page_count": 1,
    "blocked": false,
    "proxy_traffic_bytes": 195573
  },
  "total_points": 2
}

Integration

How to run it

The same lookup works from the app, the API, or as a tool an agent can call mid-task.

Results come back in the same envelope as every other source: a session id, a readable summary, the structured result and the points charged.

curl -X POST https://api.neuralverge.ai/functions/v1/run-lei-lookup-company-relationships \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"company":"7LTWFZYICNSX8D621K86","max_items":2}'

Use cases

What teams use it for

Where this field shows up in an actual workflow.

Mapping a corporate group

List the subsidiaries of a parent and follow each child's LEI to its record.

Exposure and counterparty reviews

See which entities sit under one ultimate parent.

Group-level screening

Expand one LEI into all of its related entities before a screening run.

Coverage & limits

Coverage, freshness and limits

What this source covers, how fresh it is, and where it stops.

Coverage

Records on LEI Lookup (lei-lookup.com).

Freshness

Read at request time, so the answer reflects the register as it stands when you ask.

Handling

LEI Lookup (lei-lookup.com) is a public register. Every response carries the source URL it was read from and a session id you can trace.

What it will not do

—Only subsidiaries that hold a LEI and are reported to the register appear.
—Rows carry LEI, name and relationship only; use LEI Lookup company for each child's detail.
—Large groups can have hundreds of children, so set max_items and start_page.

FAQ

Questions, answered

A direct child is owned one step below the parent; an ultimate child sits under it at the top of a chain. The flags show which, and a child can be both.

Related sources

LEI Lookup company

Record and subsidiary counts for one LEI.

GLEIF company

Parents and children from the Global LEI Index.

All corporate registries

Company registers across Europe, the Americas and Asia-Pacific, plus global LEI lookup.

Try lei lookup company relationships on your own data

One request format across every source in the catalog.

Get started