Sugra Entity direction

The full entity picture - KYB, sanctions, PEP - a screening signal, not a determination.

Sugra Entity is the compliance and know-your-business direction: a composed KYB envelope keyed by entity anchor (lei, vat, siren, or siret), sanctions screening for names, crypto wallet addresses and document identifiers, a PEP layer, and the GLEIF plus INSEE Sirene corporate registry surfaces. The direction carries zero commercial upstreams, so every source is named openly: OFAC SDN, the EU consolidated list, the UN Security Council consolidated list, UK OFSI, Canada OSFI, Australia DFAT, Switzerland SECO, the World Bank listing of ineligible firms, a Wikidata-derived PEP layer, GLEIF LEI data (CC0), and INSEE Sirene (Etalab). Every screening response carries meta.disclaimer: a screening signal, not a compliance determination, and not legal advice.

What data lives here

API Reference category	Endpoints	Coverage
Sugra Entity	9	Composed KYB envelope by anchor with `profile`, `screening` and `ownership` slices, single and batch name screening, entity resolution, wallet and document-identifier screening, and the screening sources manifest with per-list freshness
Corporate Registry	14	GLEIF LEI records: search, fuzzy name match, full record, direct and ultimate parent, relationship graph, ISIN mapping, managed funds, field-level audit log, plus registration-authority, LEI-issuer, country and region catalogs

Counts reflect the live catalog as of 2026-07-18. Adjacent identifier surfaces live in other directions: OpenFIGI instrument mapping (Finance), CIK-keyed SEC EDGAR filings (SEC EDGAR) and EDINET Japan filings (Fundamentals).

Flagship endpoints

Sanctions and PEP name screening

POST /api/v1/entity/screen screens one name against the full sanctions corpus; POST /api/v1/entity/screen/batch takes a list. Optional country, dob and nationality sharpen matching; as_of scopes the check to a dated list snapshot.

Response (truncated):

{
  "data": {
    "screening": {
      "status": "hit",
      "matches": [
        {
          "list": "au_dfat",
          "program": "Autonomous (Russia)",
          "restriction_type": "block",
          "matched_name": "Open Joint Stock Company Rosneft Oil Company",
          "score": 1.0,
          "match_type": "name_fuzzy",
          "list_published": "2026-07-11"
        }
      ]
    }
  }
}

status is hit, review or clear, driven by threshold_hit (default 0.9) and threshold_review (default 0.7). Each match carries a rationale array explaining the score.

Composed KYB envelope

GET /api/v1/entity/{anchor}/{value} composes identity, screening and ownership into one envelope from a single anchor. include selects slices; /{slice_name} and /adverse-media fetch a single slice.

Response (truncated):

{
  "data": {
    "entity": {
      "id": "sugra-ent:lei:7LTWFZYICNSX8D621K86",
      "anchor": {"lei": "7LTWFZYICNSX8D621K86"},
      "name": "DEUTSCHE BANK AKTIENGESELLSCHAFT",
      "country": "DE",
      "type": "company",
      "status": "ACTIVE",
      "field_provenance": {"name": "gleif", "country": "gleif", "status": "gleif", "type": "gleif"}
    },
    "screening": {"status": "review"}
  },
  "meta": {
    "product": "Sugra Entity",
    "screening_id": "9171755b-00e7-4592-abc4-96c3debf8bdd",
    "disclaimer": "Screening signal, not a compliance determination. Sugra is a technology provider, not a consumer reporting agency or sanctions authority."
  }
}

Every field in the envelope names its upstream in field_provenance, and meta.screening_id gives each check a stable identifier for audit trails.

Russian regulatory watchlists

POST /api/v1/entity/rf-watchlists/screen screens a name or a Russian registry identifier against the domestic lists of the Russian Ministry of Justice (Minjust) that are currently loaded. The lists this surface covers are extremist organizations, foreign agents and undesirable organizations, and GET /api/v1/entity/rf-watchlists/sources shows which of them are loaded and how fresh each one is. This is not a Western sanctions screen - use POST /api/v1/entity/screen for OFAC, EU and UN lists. Provide name or identifier, not both. By default only active listings match; set include_excluded: true to also match entries that have been removed from a list.

Response match for identifier mode uses match_type: "identifier_exact" and score: 1.0. Coverage note on RF matches states that a Minjust designation is not a Western sanctions determination.

Crypto wallet screening

GET /api/v1/entity/wallet/{address}/screen matches an address against sanctioned wallets; GET /api/v1/entity/id/{id_type}/{value}/screen does the same for document identifiers such as passports (OFAC SDN - not RF INN/OGRN).

Response (truncated):

{
  "data": {
    "screening": {
      "status": "hit",
      "matches": [
        {
          "list": "ofac_sdn",
          "restriction_type": "block",
          "matched_name": "Lazarus Group",
          "score": 1.0,
          "match_type": "wallet",
          "rationale": ["exact wallet match", "symbol=ETH"],
          "list_published": "2026-07-17"
        }
      ],
      "fifty_percent_rule": {"triggered": false, "ambiguous": false}
    }
  }
}

The fifty_percent_rule block flags exposure through sanctioned ownership, not just direct listings.

GLEIF LEI records

GET /api/v1/gleif/lei-records/{lei} returns the full ISO 17442 registry record; /direct-parent, /ultimate-parent and /relationships/{lei} walk the ownership chain, and /lei-search plus /fuzzy-search find the LEI from a legal name.

The record carries legal name, legal and headquarters addresses, jurisdiction, national registry number (registeredAs), legal form, status and the full event history for the entity - here Siemens Aktiengesellschaft, HRB 6684, jurisdiction DE.

Typical workflows

KYB onboarding: resolve a counterparty name via POST /api/v1/entity/resolve or GLEIF search, compose the envelope from the anchor, and store meta.screening_id with the case file.

Payment and transaction pipelines: batch name screening plus wallet and identifier checks before settlement, with as_of replays for point-in-time evidence.

Agents and compliance dashboards: read GET /api/v1/entity/sources for per-list staleness before relying on a result; every response repeats list_freshness and stale_screening so degraded coverage is never silent.

Where to go next

Sources: the Sugra Entity sources page lists every sanctions regime, the PEP layer and GLEIF with tier and license.

API Reference: the sidebar categories Sugra Entity and Corporate Registry document every endpoint with parameters and schemas.

Quickstart covers authentication, the response envelope and rate-limit headers.

Sugra Entity direction

What data lives here#

Flagship endpoints#

Sanctions and PEP name screening#

Composed KYB envelope#

Russian regulatory watchlists#

Crypto wallet screening#

GLEIF LEI records#

Typical workflows#

Where to go next#

What data lives here

Flagship endpoints

Sanctions and PEP name screening

Composed KYB envelope

Russian regulatory watchlists

Crypto wallet screening

GLEIF LEI records

Typical workflows

Where to go next