Global-LEI-Registry
Top drivers
⌁ mcp.call("adw-234") vADW-234-live-1.0 How complex/opaque is a counterparty's legal ownership structure?
Global-LEI-Registry
Top drivers
⌁ mcp.call("adw-234") vADW-234-live-1.0 A KYC/onboarding agent calls ADW-234 at counterparty intake and blocks automated approval whenever complexity_score exceeds 60 or ownership_depth exceeds five levels, routing the entity to a human sanctions analyst instead. The backtest shows the current score is 25.3 (up 172% from 9.3 at launch), meaning the GLEIF relationship graph for the entity has grown meaningfully in complexity; the agent cites source_lineage (GLEIF LEI relationship records) and methodology_version in the escalation ticket so the analyst knows exactly which ownership-graph snapshot was evaluated. This replaces a manual KYC process that typically requires 3–5 business days per complex entity.
A credit risk officer at a corporate bank uses the ownership_depth and relationship_count fields from ADW-234 to score new lending counterparties before credit committee, flagging entities with opaque multi-layer parent structures that increase recovery risk in default scenarios. Because GLEIF is the authoritative global LEI registry, the score is auditable and defensible to regulators — unlike manual KYC reports that rely on inconsistent proprietary data sources and cannot be reproducibly re-run at quarterly counterparty review.
ownership-graph depth + breadth composite from GLEIF relationship records
Version ADW-234-live-1.0 · validated to beat a naive baseline · benchmark: Manual KYC is slow & proprietary; GLEIF is the open global LEI graph