TODO_TAGS_REVIEW

LEI Relationship Consistency Checker

Checks four structural invariants over a pasted set of GLEIF Level-2 relationship records for one subject LEI: every startNode and endNode is a syntactically valid LEI (ISO 17442 mod-97, the same check art-246 carries), walking IS_DIRECTLY_CONSOLIDATED_BY edges never revisits a node already on the current path, every reporting-exception code is a published GLEIF category held as a versioned constant rather than inferred, and no two active records share a startNode, endNode and relationshipType triple with overlapping validity periods. A violation flags a possible inconsistency in GLEIF's published Level-2 data for this LEI. It is not an assertion about the entity's actual corporate structure and not a finding about the entity itself; golden-copy data is periodically corrected, so recheck against a fresh pull before treating any violation as durable. An empty record set returns consistent as null rather than a clean pass. Zero network: this never queries GLEIF and is not a re-implementation of GLEIF's own reconciliation service.

Tool URL: https://ainumbers.co/chaingraph/art-600-lei-relationship-consistency.html AP2/Policy Mandate export: yes

post/v1/tools/check_lei_relationship_consistency

Request

  • Base URL: https://ainumbers.co
  • URL: https://ainumbers.co/v1/tools/check_lei_relationship_consistency
  • Auth: none declared

Request body

subject_leiunknown required

Response

Successful tool execution result

consistentboolean
cycle_pathstring
exception_table_sourcestring
exception_table_versionstring
pii_notestring
recognized_exception_codes_currentstring[]
recognized_exception_codes_deprecatedstring[]
record_countinteger
records_assessedboolean
scope_notestring
subject_leistring
subject_lei_validboolean
violation_countinteger

Changes

No recorded changes to this operation across all 1 revision of this API.