LEI Lookup — Legal Entity Data, Address & Parents

LEI Lookup — Legal Entity Data, Address & Parents ✅ No API Key

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. You pay per completed lookup — matched or not; failed runs are never charged.

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.
• 💸 One row per completed lookup — no run fee and no start fee. An unresolved LEI comes back as one no result row, billed like any other row; a failed run costs $0.00.
• 🔑 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 you still get a row — an explicit no result row that echoes the code you submitted — so nothing disappears silently.

Input

One record per run.

Field	Type	Notes
lei	string	The 20-character Legal Entity Identifier, e.g. 213800MQORWPL582SW82.
recordUrl	string	Advanced: 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.

Lists — legalAddressStreetLines, 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"
    }
  ]
}

When nothing is found

A lookup that runs but matches nothing still returns a row, so a batch never silently loses an LEI:

Column	Value
lei, url	echoed back exactly as submitted
found	false
message	why nothing was returned

Filter these out with found != false (or drop rows where message is set). This row is billed as one result — see Pricing.

Pricing

Pay per event — $0.005 per record ($5 per 1,000) written to the dataset. There is no run fee and no start fee.

Event	Price	Charged
Actor start	free	never
Failed run — invalid input, API error, timeout	free	never
Row written to the dataset	$0.005 ($5 / 1,000)	every row, including the "no result" row

A completed lookup is billed as one record, matched or not. When the source returns nothing, the Actor writes one explicit no-result row — the query you submitted plus found: false and a message explaining it — and that row is charged at the normal per-record price. A run that fails (missing input, bad key, upstream error) writes no row and costs $0.00.

Pricing is on top of your Apify platform usage.

Rate limit

There is a ceiling on how fast one Apify account can pull from the Neuralverge backend: 10 requests per second for this Actor, counted separately from the other Neuralverge Actors. One run is normally one request, so this is about how many runs you start at once, not about the size of a single run — at typical run times that is dozens of runs in flight at once, which is well above ordinary use.

Updated August 2026: this ceiling was doubled from 5 to 10 requests per second. Bulk jobs that used to hit 429s now go through.

Above the ceiling the backend answers HTTP 429. The Actor waits out the Retry-After it asks for and retries a few times before giving up; a run that does give up writes no row and is not charged.

If you need a higher rate for a bulk job, get in touch.

Free plan limits

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

On the Apify Free plan this Actor may be started 5 time(s) per calendar month per user. A run that finds nothing still counts, because the lookup is performed either way. Every Neuralverge Actor carries its own allowance — running one never uses up another's. 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? Yes — a lookup that ran is billed as one record even when it matched nothing, and you get a no result row that says so. A run that fails (missing input, upstream error) writes no row and is not charged.

---

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.