Skip to main content
Risk and Screening includes original-publisher data collected by our OpenSanctions-derived crawler pipeline, alongside other published restricted-party sources. We use the open-source crawler code to collect publisher records; we do not redistribute OpenSanctions’ compiled bulk dataset. Start with GET /api/v2/lists or MCP lists_catalog(). Select rows with ingested: true. Each row gives its source_key, category, current entry count, publisher, source URL and available crawl/coverage dates. Declared sources without ingestion are not evidence of screening coverage. The Arena’s source choices read this live catalog; if discovery fails, its compiled fallback is explicitly labelled.
Use the key returned by the current catalog rather than assuming a particular source is loaded. List Entries searches publisher records; Screening Match resolves name/identifier candidates and returns contributing memberships and identity confidence. Its scope is not restricted to sanctions. Entries can also describe debarment, wanted persons, maritime restrictions, domestic terrorism or combined screening lists. Only sanctions and export-control categories contribute to the sanctions exposure lens. A combined screening list or a debarment entry does not become a sanction by being ingested. Ownership Exposure follows recorded ownership paths to qualifying flagged entities. The assets subject covers the energy-asset projection; it does not promise screening for every facility in the directory. Select the entities subject to inspect entity exposure. Inspect source memberships, ownership evidence, effective stake and available coverage before interpreting a result. A match is an analytical risk signal, not a compliance verdict, and a company parent’s listing is not the subsidiary’s own designation. MCP exposes the same data under Risk and Screening. Call named lists_catalog, list_entries_search, screening_match or exposure_search tools with their advertised parameters. Use get_parameter_options for unfamiliar accepted choices. Source discovery remains live, so the compiled enum snapshot can contain fewer keys than the current catalog. Unloaded or unknown source keys return an availability error rather than a misleading empty screening result.