# LEI Renewal & Registration Brief — GLEIF (`jpmarketdata/gleif-lei-renewal-brief`) Actor

Check exact corporate LEIs with GLEIF registration status, renewal dates and source freshness. Receive one complete, validated brief per identifier for recurring renewal and onboarding workflows. Unofficial.

- **URL**: https://apify.com/jpmarketdata/gleif-lei-renewal-brief.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 lei brief createds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## LEI Renewal & Registration Brief — GLEIF

> **Unofficial** — independent tool, **not affiliated with, endorsed by, or sponsored by GLEIF**. It reads only publicly visible pages. Support, reliability guarantees and the full disclaimer are at the bottom of this page.

Check exact Legal Entity Identifiers against GLEIF and receive registration status, renewal dates and source freshness. Useful for treasury and counterparty onboarding workflows asking “Which of my known corporate LEIs need renewal attention?” These are registration facts and Actor-calculated date categories, not creditworthiness, sanctions, AML or legal-compliance verdicts.

### Input

`leis` is required: 1–10 uppercase 20-character LEIs passing ISO 17442 / MOD 97-10 checksum validation. Duplicates are removed in input order. `renewalWarningDays` is an integer 1–180, default 30. `maxItems` is an integer 1–10, default 5, and must be at least the number of distinct requested LEIs. Invalid input, inadequate maxItems or insufficient event budget fails before source requests. The exact requested set is never silently truncated.

Example: `{"leis":["5493001KJTIIGC8Y1R12"],"renewalWarningDays":30,"maxItems":1}`.

### Output

One `gleif_lei_renewal_brief` row per distinct LEI in input order. All source responses validate before any dataset writes or charges. A missing or malformed record fails the run, with no partial source result. Dataset write failures may still leave already delivered rows.

`lei`, `legalName`, `jurisdiction`, `entityStatus` and `registrationStatus` describe the registered entity. Source status tokens are preserved. `lastUpdateDate`, optional `nextRenewalDate`, and `goldenCopyPublishedAt` are source UTC timestamps. `daysUntilRenewal` is an optional integer UTC calendar-date difference. When source renewal is explicitly null, `renewalDateAvailable` is false and `nextRenewalDate` / `daysUntilRenewal` are omitted. Otherwise `renewalDateAvailable` is true. `sourceAgeHours` is the Actor-calculated age of the golden copy. `sourceUrl` and `fetchedAt` provide provenance.

`renewalWindow` and `reason` are Actor-calculated: source LAPSED takes precedence as `lapsed`; any registration status other than ISSUED or an unknown entity status or missing renewal date gives `unknown`; a past renewal date gives `overdue`; today through renewalWarningDays gives `due-soon`; later dates give `later`. An overdue ISSUED record is not claimed to be legally invalid. Unknown future status tokens are preserved but not interpreted. No row means no successful result.

### Limits

Lightweight HTTPS only, fixed api.gleif.org host and exact record endpoint, at most 10 requests, one-second interval, 1 MiB response cap, 30-second request timeout, 180-second run cap and 256 MB memory. No retries, browser, proxy, paid API, relationship traversal or pagination. 403 and 429 stop immediately. Failure kinds: invalid-input, not-found, auth-block, rate-limit, timeout, structure-change and upstream-error. Source freshness is measured; data is not guaranteed current.

### Privacy

Output uses an explicit field allowlist. Addresses, contact persons, phone numbers, email, ownership relationships, BIC data and raw response bodies are not stored. Only source categories GENERAL, FUND and BRANCH are supported; sole proprietors and unknown categories fail closed before output. Only registered legal entity name, jurisdiction and lifecycle metadata are retained. Never provide personal contact data as input.

### Data source and terms

[GLEIF LEI API](https://api.gleif.org/api/v1/lei-records/5493001KJTIIGC8Y1R12) provides public LEI data under [GLEIF LEI Data Terms of Use](https://www.gleif.org/en/meta/lei-data-terms-of-use), including CC0 for the data access service. API robots.txt permits this path. This Actor is independent of GLEIF and makes no source warranty.

### Pricing

$0.01 per delivered exact-LEI brief through the primary `lei-brief-created` event, with no actor-start or secondary event. Every delivered row uses exactly one charged dataset event. Source failures before delivery and empty runs have no event charge. Already delivered rows remain billable if a later dataset write fails.

### If something goes wrong

- **Wrong number or a failed run?** Open a ticket on the **Issues** tab. I read every one and reply within 2 business days (Japan time).
- **You never get a fake "empty" result.** If the site can't be read, the run fails and says so.
  One validated and delivered LEI brief is one billable event. Source failures before delivery and empty runs have no event charge; already delivered rows remain billable if a later dataset write fails.
- **Checked every week.** An automatic test runs this tool weekly; if the site changes, I fix it.
- **Public pages only.** No login, no personal data, and it goes easy on the site.

### More tools by the same author

- [Mercari Japan Sold Prices — What Items Really Sell For](https://apify.com/jpmarketdata/mercari-japan-price-checker)
- [Yahoo! Auctions Japan Sold Prices — Median, Range, Bids](https://apify.com/jpmarketdata/yahoo-auction-sold-comps)

All tools (Japan marketplaces, real estate, jobs, racing, prediction markets): <https://apify.com/jpmarketdata>

### Disclaimer

Unofficial, independent tool — **not affiliated with, endorsed by, or sponsored by GLEIF**. Product names and logos belong to their owners and only say where the data comes from. Data is read from public pages, for market research; check before you act on it.

# Actor input Schema

## `leis` (type: `array`):

1–10 uppercase 20-character LEIs with valid checksum. Duplicates are removed; maxItems must cover all distinct LEIs.

## `renewalWarningDays` (type: `integer`):

UTC calendar days ahead counted as due-soon, inclusive of today.

## `maxItems` (type: `integer`):

Must cover every distinct requested LEI; smaller values fail before source requests or charges.

## Actor input object example

```json
{
  "leis": [
    "5493001KJTIIGC8Y1R12"
  ],
  "renewalWarningDays": 30,
  "maxItems": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Validated exact LEI registration, renewal and source freshness evidence.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "leis": [
        "5493001KJTIIGC8Y1R12"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("jpmarketdata/gleif-lei-renewal-brief").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "leis": ["5493001KJTIIGC8Y1R12"] }

# Run the Actor and wait for it to finish
run = client.actor("jpmarketdata/gleif-lei-renewal-brief").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "leis": [
    "5493001KJTIIGC8Y1R12"
  ]
}' |
apify call jpmarketdata/gleif-lei-renewal-brief --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,jpmarketdata/gleif-lei-renewal-brief"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/saW9Zqb8BoqVxLJH6/builds/bgj7atFvzjNHQPVZP/openapi.json