🆔 Legal Entity Identifier
A 20-character global identifier for a legal entity participating in financial transactions.
Corporate
Sources
3
3 no-auth
Disciplines
3
that use it
Mission domains
4
reach
Workbench
—
native tool
🔗 Analyst pivots
🔌 Sources that yield Legal Entity Identifier (3)
| Source | Category | Auth | Format | |
|---|---|---|---|---|
| GLEIF LEI Legal-entity identifiers. | Identity | NONE | json | home↗ api↗ |
| GLEIF LEI (Golden Copy) Global Legal Entity Identifier records. | Legal Entity | NONE | json | home↗ api↗ |
| GLEIF LEI + OpenCorporates Legal-entity & corporate registry intelligence. | CORPINT | NONE | json | home↗ api↗ |
🧭 Disciplines
🎯 Mission Domains
🔍 Lookup
🔄 Live Datasets & APIs (3 key-free · ingestible)
📜 Playbook — Legal Entity Identifier exploitation
- Direction — frame the requirement for Legal Entity Identifier: what decision does this support, by when?
- Collection — pull the 3 mapped sources (3 free) and the native workbench; capture provenance and observe OPSEC.
- Processing — normalize, de-duplicate and enrich the collected data.
- Analysis — correlate against local holdings; apply ACH; assign confidence.
- Dissemination — open a case, draft a report, share via STIX/MISP.
- Feedback — set an alert rule / watchlist to monitor for change.
⚡ AI Skills & Automation
Automate unattended via the cron pipeline (collect → ingest → resolve → enrich → score → alert).
🧩 Advanced Capabilities
✨ Enrichment pathways
🎫 Legal Entity Identifier
A Legal Entity Identifier is a 20-character ISO 17442 code uniquely identifying a legally distinct entity participating in financial transactions. It provides a global, authoritative key for entity resolution and parent/child ownership disclosure, cutting through inconsistent local registry naming.
Format: 20 alphanumeric chars: 4-char LOU prefix + 2 reserved zeros + 12-char entity part + 2 ISO 7064 MOD 97-10 check digits (e.g. 5493001KJTIIGC8Y1R12)
📡 How it is collected
- GLEIF LEI search by name or ID
- Regulatory filings (MiFID, EMIR, Dodd-Frank)
- Swift/ISO 20022 payment messages
- Trade repository reports
- Company disclosure documents
- Bond prospectuses
📚 Enrichment & validation sources
🔗 Pivot to
🧩 Analysis & hunting techniques
- ISO 7064 checksum validation
- Level-2 parent/child relationship traversal
- LOU (registration authority) provenance check
- Lapsed/retired status monitoring
- Cross-mapping LEI to ISIN/BIC/MIC
- Duplicate-entity reconciliation
🔧 Tools
- GLEIF API
- OpenCorporates
- OpenSanctions Yente
- Python (leidata)
- Neo4j
- Maltego
⚡ Workbench actions
- Validate LEI checksum
- Resolve to registered entity
- Traverse parent ownership tree
- Check registration status
- Map LEI to ISIN/BIC
- Screen entity against sanctions
📊 Dashboard KPIs
Registration status (active/lapsed)Level-2 relationship countDays since last renewalParent chain depthCross-reference match count
Workstation · Copilot · AI Skills · Automation · Playbooks · Lookups · Docs · Reports
🤖 AI Copilot
⚡ AI Skills
🔍 Lookup & Enrich
📚 Docs & Reports
💡 Recommendations
- Explore related tools below
- Automate recurring work via cron