https://data.japanagent.dev/screen/ownership-chain
Ownership-chain sanctions screening: resolve a company (by LEI or name), walk its corporate ownership chain via GLEIF Level 2 relationship data (direct parent, ultimate parent), and screen every entity in the chain — including transliterated and alternate names — against OFAC SDN, EU consolidated, and UN Security Council lists. Catches the case where your counterparty is clean but its parent is sanctioned. Unique combination of KYB registry resolution and sanctions screening.
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://data.japanagent.dev/screen/ownership-chain", {
method: "GET",
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Live 402 quote confirmed
GET returned a protocol-valid 402 quote (402). No payment was made.
- Origin reachable
HEAD https://data.japanagent.dev/ returned 200.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
- Observed in 402-index
Discovered through bazaar.
- Registry record checked
Registry health: healthy.
EVIDENCE
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call.