LEI Entity Lifecycle Watch Report

Entity-reference, procurement, treasury, and research teams provide LEI codes, legal names, or country filters; this actor reads the public GLEIF LEI API. It returns a source-linked portfolio report first, followed by lifecycle alerts, normalized entity rows, and an optional export manifest. No API key or login is required.

Store Quickstart

1. Run the first example with initialRunMode: "baseline_only"; the first run stores a snapshot and intentionally produces zero rows and zero charges.
2. Run the same monitorKey again with generateReport: true and emitUnchanged: false; only changed records produce a report and alerts.
3. Set generateExport: true when a changed portfolio should also produce the normalized export manifest. maxChargeUsd is checked before any billable row is delivered.

Run the next report

• For as-filed corporate disclosure facts, use SEC EDGAR Material Disclosure Watch Scraper.
• For public procurement opportunity alerts, use Government Tender & Grants Monitor.
• For domain, DNS, and public security signals, use Company Domain Tech DNS Security Audit.

Input Examples

1. Baseline a known LEI portfolio

{
  "leis": [
    "INR2EJN1ERAN0W5ZP974"
  ],
  "monitorKey": "treasury-portfolio",
  "initialRunMode": "baseline_only",
  "generateReport": true,
  "generateExport": false,
  "emitRawRows": false,
  "emitUnchanged": false,
  "maxChargeUsd": 25,
  "dryRun": false
}

2. Generate a changed portfolio report and export

{
  "leis": [
    "INR2EJN1ERAN0W5ZP974"
  ],
  "monitorKey": "treasury-portfolio",
  "initialRunMode": "baseline_only",
  "generateReport": true,
  "generateExport": true,
  "emitRawRows": true,
  "emitUnchanged": false,
  "maxChargeUsd": 25,
  "dryRun": false
}

3. Search by legal name or country

{
  "leis": [],
  "legalNames": [
    "MICROSOFT CORPORATION"
  ],
  "countries": [
    "US"
  ],
  "pageSize": 10,
  "monitorKey": "us-issuer-reference-watch",
  "initialRunMode": "emit_backfill",
  "generateReport": true,
  "generateExport": true,
  "emitRawRows": false,
  "emitUnchanged": false,
  "maxChargeUsd": 25,
  "dryRun": false
}

4. Inspect all billing event shapes without a live call

{
  "dryRun": true,
  "generateReport": true,
  "generateExport": true,
  "emitRawRows": true,
  "maxChargeUsd": 25
}

Sample Output

The first row of a changed run is lei-portfolio-report. It is followed by lei-lifecycle-change-alert rows, optional lei-entity-row rows, and an optional lei-export manifest. Each row contains sourceUrl, retrieval time, GLEIF attribution, limitations, and prohibited interpretations. See docs/sample-output.json for a complete example.

Output Fields

• lei, legalName, entityStatus, registrationStatus, and address summaries describe the observed GLEIF record.
• changeTypes, previous, and current explain lifecycle field differences from the saved portfolio snapshot.
• sourceUrl, sourceMethod, authorizationBasis, and cc0Attribution preserve provenance.
• billingEventName identifies the configured PAY_PER_EVENT event.
• limitations and prohibitedInterpretations prevent the output from being presented as certification or advice.

Pricing

• lei-entity-row: $0.005
• lei-lifecycle-change-alert: $0.20
• lei-portfolio-report: $10
• lei-export: $6

The actor checks the estimated total against maxChargeUsd before delivery and fails closed if the limit would be exceeded. The first baseline_only run and an unchanged monitoring run emit zero dataset rows and zero billable events. dryRun emits one sample of each billable type but skips charging.

Compliance Guardrails

• Source access is limited to the official public GLEIF API. No key, login, private data, or access bypass is used.
• GLEIF attribution and source links are retained. Public-data availability or CC0 terms do not imply GLEIF affiliation or endorsement.
• An LEI record is a reference-data observation. This actor does not provide identity or KYC certification, sanctions clearance, credit assessment, legal advice, investment advice, or a guarantee about an entity.
• The actor does not extract contacts or create outreach lists. Users remain responsible for their own review of source records and applicable data-use rules.