LEI Lookup — Legal Entity Data, Address & Parents avatar

LEI Lookup — Legal Entity Data, Address & Parents

Pricing

$5.00 / 1,000 results

Go to Apify Store
LEI Lookup — Legal Entity Data, Address & Parents

LEI Lookup — Legal Entity Data, Address & Parents

Look up any GLEIF Legal Entity Identifier (LEI) — legal name, status, legal & HQ address, jurisdiction, registration authority, renewal dates and parent/child relationships. Structured JSON, no API key. A miss costs only the small run fee.

Pricing

$5.00 / 1,000 results

Rating

0.0

(0)

Developer

NeuralVerge

NeuralVerge

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Share

Look up any Legal Entity Identifier (LEI) record — legal name, legal & headquarters addresses, registration authority, jurisdiction, entity status, registration/renewal dates, managing LOU and parent (consolidation) relationships. Powered by the Neuralverge API. No API key or account required, and you only pay for records we actually find.

Ideal for KYC/KYB, counterparty and beneficial-ownership checks, compliance and feeding entity data to AI agents.

✨ Why this Actor

  • 🌍 Full LEI record — identity, addresses, registration authority, dates and parent relationships in one structured object.
  • 💸 Pay per the records you get — unresolved LEIs are skipped and never billed. A miss costs only the $0.005 lookup fee — no empty, billable result rows.
  • 🔑 No API key or account — extraction runs on the Neuralverge backend.
  • Real-time & structured — fresh data each run and one predictable JSON schema.

🔧 How it works

  1. Provide a 20-character LEI code (e.g. 213800MQORWPL582SW82) — or an advanced full lei-lookup.com record URL.
  2. Run the Actor. Fetching and AI-structuring the record happens on the Neuralverge backend.
  3. Get one flat dataset row per record — 23 columns, all at the top level (url, lei, legalName, legalAddressStreetLines, legalAddressCity, legalAddressRegion, …). Export to CSV, JSON or Excel, or pull it over the Apify API.

If the LEI can't be resolved, it's logged and skipped without charge.

Input

One record per run.

FieldTypeNotes
leistringThe 20-character Legal Entity Identifier, e.g. 213800MQORWPL582SW82.
recordUrlstringAdvanced: a full lei-lookup.com record URL to use instead of the LEI.
{
"lei": "213800MQORWPL582SW82"
}

What you'll receive

One flat row per LEI record. Every field sits at the top level of the row, so the Output tab shows a single table with all 23 columns — there are no views to switch between. Exports (CSV, JSON, XML, Excel) contain exactly the same fields.

Columns: url, lei, legalName, legalAddressCity, legalAddressRegion, legalAddressPostalCode, legalAddressCountry, headquartersAddressCity, headquartersAddressRegion, headquartersAddressPostalCode, headquartersAddressCountry, registrationAuthorityId, registrationAuthorityName, legalJurisdiction, entityCategory, entityStatus, initialRegistrationDate, lastUpdateDate, nextRenewalDate, managingLou.

ListslegalAddressStreetLines, headquartersAddressStreetLines, relationships — come back as arrays. The table renders each as an expandable "N items" cell; a CSV/JSON/Excel export carries them in full.

Nulls are normal. The column set is the same on every run, so a field the source does not expose for this LEI record comes back null rather than disappearing — a spreadsheet or CRM mapping built on one run keeps working on the next.

Example output (real run)

A real dataset row, shown in full.

{
"url": "https://www.lei-lookup.com/record/213800MQORWPL582SW82",
"lei": "213800MQORWPL582SW82",
"legalName": "REVOLUT LTD",
"legalAddressStreetLines": [
"30 SOUTH COLONNADE"
],
"legalAddressCity": "LONDON",
"legalAddressRegion": "GB-LND",
"legalAddressPostalCode": "E14 5HX",
"legalAddressCountry": "GB",
"headquartersAddressStreetLines": [
"30 SOUTH COLONNADE"
],
"headquartersAddressCity": "LONDON",
"headquartersAddressRegion": "GB-LND",
"headquartersAddressPostalCode": "E14 5HX",
"headquartersAddressCountry": "GB",
"registrationAuthorityId": "08804411",
"registrationAuthorityName": "Companies Register (Companies House)\n\nUnited Kingdom, England and Wales",
"legalJurisdiction": "GB",
"entityCategory": "GENERAL",
"entityStatus": "ACTIVE",
"initialRegistrationDate": "2018-01-25",
"lastUpdateDate": "2026-04-08",
"nextRenewalDate": "2027-04-25",
"managingLou": "LONDON STOCK EXCHANGE LEI LIMITED",
"relationships": [
{
"relationshipType": "IS_DIRECTLY_CONSOLIDATED_BY",
"parentLei": "213800UIKMYZWWQS5E02",
"parentName": "REVOLUT GROUP HOLDINGS LTD"
},
{
"relationshipType": "IS_ULTIMATELY_CONSOLIDATED_BY",
"parentLei": "213800UIKMYZWWQS5E02",
"parentName": "REVOLUT GROUP HOLDINGS LTD"
}
]
}

Pricing

Pay per event — $0.005 per run, plus $0.005 per record ($5 per 1,000) returned to the dataset. A miss costs only the $0.005 lookup fee — you are never charged the per-result price for a row you did not get.

EventPrice
Lookup (per run)$0.005
Record returned (per dataset row)$0.005

LEIs that can't be resolved are not charged the per-result price — only the $0.005 lookup fee applies. Pricing is on top of your Apify platform usage.

Free plan limits

Users on any paid Apify plan are not affected by anything in this section.

On the Apify Free plan all Neuralverge Actors share one budget, per user and per calendar month: 15 runs in total, at most 5 of them on this Actor, and 35 returned rows. A run that finds nothing still counts, because the lookup is performed either way. LinkedIn People Search is metered differently — one run there uses 25 of the 35 rows, because a full page of 25 profiles is bought upstream whether or not all of them are returned. When a limit is reached the Actor stops gracefully with a status message naming it; everything resets on the 1st of every month, and any paid Apify plan removes all of it.

Integrations & API

Results are stored in a standard Apify dataset — export as CSV, JSON, XML or Excel, or fetch on demand through the Apify API. The Actor also plugs into Apify's integrations (Make, Zapier, n8n, webhooks) and can be called from any MCP client.

FAQ

Do I need an account or API key? No. Extraction runs on the Neuralverge backend.

What identifier do I use? The 20-character LEI code, e.g. 213800MQORWPL582SW82. You can also pass a full lei-lookup.com record URL.

Am I charged if a record isn't found? No. You're billed only for rows returned to the dataset.


Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by GLEIF or any LEI issuer. LEI data originates from the public Global LEI System.