LEI Search API — Find a Legal Entity Identifier
You usually have a name and need the code. This source searches the global LEI system and returns the matching entities as structured data, so you can go from a company name to the identifier that works across jurisdictions.
- You send
- A company name
- You get back
- Matching entities with their identifiers
- Coverage
- Worldwide — entities on the global LEI system.
- Price
- 5 pts — $5 per 1,000
- Charged only when the record resolves. A lookup that finds nothing is not billed.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| the global LEI system directly | Search the global index and read the results by hand | 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 | $5 per 1,000, misses not billed | Covers Worldwide — other countries are separate sources with the same request format |
What you get back
Every field the response returns.
| Field | Type | Description |
|---|---|---|
search_results | array | Matching entities from the search. |
search_results[].legal_name | string | Registered legal name. |
search_results[].lei | string | The 20-character identifier. |
search_results[].country | string | Country of the entity. |
search_results[].entity_status | string | Whether the entity is active. |
search_results[].lei_status | string | Whether the identifier itself is current or lapsed. |
Every source answers in the same shape: a session id, a readable human summary, a structured machine object and the points the call consumed. Learn it once and it holds across every source in the catalog.
How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
A JSON schema passed as extract_schema_json pins the response shape, which is why one endpoint serves every register in the catalog — only the URL and the schema change. The Get API Code button in the app hands you the complete command with the schema already filled in.
curl -X POST https://api.neuralverge.ai/functions/v1/run-extract \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://lei.info/search?q=example",
"instructions": "Extract data from the global LEI system",
"settings": {
"country_code": "us",
"extract_schema_json": "{ ... }"
}
}'What teams use it for
Where this field shows up in an actual workflow.
Resolve a company name to the code the rest of your pipeline needs.
Attach identifiers to a list that only has names.
See the candidate entities before you commit to one of them.
Check whether a counterparty holds an identifier at all before you ask them for it.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
Worldwide — entities on the global LEI system.
Read at request time, so the answer reflects the register as it stands when you ask.
the global LEI system is a public register. Every response carries the source URL it was read from and a session id you can trace.
- —A search returns candidates, not a decision — you still pick the right entity.
- —Entities without an identifier will not appear, however large they are locally.
- —Legal names differ from trading names, and the search works on the legal name.
Questions, answered
The system indexes legal names, so a trading name may not match. If a search comes back empty, try the registered legal name.
Related sources
Try lei lookup search on your own data
One request format across every source in the catalog.