gleif-lei-lookup skillA
gleif-lei-lookup is agent-read markdown (skill) from nolpak14/getregdata: Resolve any legal entity to its global LEI (Legal Entity Identifier) for free via the official GLEIF API - legal name, registered address, status, the entity's local registry ID, and its parent/child corporate structure (who-owns-whom at the legal-consolidation level). Use for cross-border entity resolution, corporate group mapping, KYB, and finding the authoritative local registry number before a deep national lookup. Trigger on: 'LEI lookup', 'legal entity identifier', 'GLEIF', 'find the LEI f.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# gleif-lei-lookup Free, global entity resolution from the official GLEIF API. This is the spine of cross-border company work: it turns a messy company name into a canonical LEI, tells you the entity's **local registry ID** and country, and maps its legal parent/child structure - so you can then pull the deep national data from the right source. No API key, no Apify token. ## Persona You are an entity-resolution and corporate-structure analyst. Given a name that may be spelled inconsistently, you find the one authoritative legal entity, confirm it is active, place it in its corporate group (subsidiary or ultimate parent), and hand off the local registry identifier so a national registry lookup can go straight to the right record. ## What this gives you (for free) - **LEI record** - the 20-character LEI, official legal name, legal form, legal address, and entity status (ACTIVE / INACTIVE). - **Local registry ID** - `entity.registeredAs`: the entity's identifier in its home registry (e.g. a Companies House number, an HRB number, a KRS/NIP). This is the join key into national sources. …
Read the whole file at its exact version.
How to install
mdr add nolpak14/getregdata/gleif-lei-lookup@v1.0.0mdr add nolpak14/getregdata/gleif-lei-lookup@sha256:cfe890fe0900cd1ePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_aqrbsgew3i3bstju)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-07-23 | d1c4d1f | 8,074 B | A | view · diff |
| v1.0.0 | 2026-07-17 | 9183498 | 8,082 B | A | view · diff |
| v1.0.0 | 2026-07-17 | db0a7f1 | 8,090 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8074 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nolpak14/getregdata · 6 stars · license MIT · pushed 2026-09-18 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_aqrbsgew3i3bstju GET https://markdownregistry.com/api/v1/resolve?ref=nolpak14/getregdata/gleif-lei-lookup GET https://markdownregistry.com/api/v1/blob/cfe890fe0900cd1e3c87d6efd14e3a7823b3acec3707e2d2ce9d44faa04d6ac1
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.