Sanctions Check

Screen a person or company against published sanctions lists, returning potential name matches with their source lists and countries.

Pay by wallet (x402) sanctions-check

Example

Example answer
{
  "query": "Vladimir Putin",
  "schema": "Person",
  "source": "dilisense",
  "matches": [
    {
      "name": "Vladimir Vladimirovich Putin",
      "datasets": [
        "us_ofac_sdn"
      ],
      "countries": [
        "ru"
      ],
      "entity_id": "us_ofac_sdn",
      "last_updated_at": null,
      "sanction_details": [
        "Executive Order 14024"
      ]
    }
  ],
  "queried_at": "2026-04-27T13:00:00.000Z",
  "match_count": 14,
  "is_sanctioned": true,
  "lists_queried": {
    "version": null,
    "collection": "dilisense/consolidated-sanctions",
    "major_lists": [
      "OFAC — Specially Designated Nationals (SDN)",
      "European Commission — Consolidated List of Financial Sanctions",
      "UN Security Council — Consolidated List",
      "HMT OFSI — Financial Sanctions",
      "SECO — Switzerland Sanctions",
      "BIS — Entity List",
      "(plus ~128 more)"
    ],
    "source_count": 134,
    "freshness_note": "Dilisense aggregates 130+ sanctions, debarment, and restrictive-measure lists into a consolidated index. The publisher refreshes the consolidated index multiple times daily; per-list timestamps are not exposed via the screening API.",
    "last_updated_at": null,
    "source_catalog_url": "https://dilisense.com/en/sources/sanction-sources"
  },
  "total_results": 14,
  "country_filter": null,
  "birth_date_filter": "1952-10-07"
}

Inputs

FieldTypeRequiredWhat it is
namestringYesPerson or company name to check
countrystringNoISO country code filter (optional)
birth_datestringNoISO date of birth (YYYY-MM-DD) for person disambiguation, reduces false positives on common names (optional)
entity_typeone of person, companyNoOverride auto-detection of entity type (optional)

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
querystringAlways (present in every successful answer)
schemaone of Person, CompanyAlways (present in every successful answer)
sourceone of dilisenseAlways (present in every successful answer)
matchesarrayAlways (present in every successful answer)
queried_atstringAlways (present in every successful answer)
match_countintegerAlways (present in every successful answer)
is_sanctionedbooleanAlways (present in every successful answer)
lists_queriedobjectAlways (present in every successful answer)
total_resultsintegerAlways (present in every successful answer)
country_filterstring or nullUsually (present for most inputs)
birth_date_filterstring or nullUsually (present for most inputs)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "sanctions-check",
    "inputs": {
      "name": "Spotify AB"
    },
    "max_price_cents": 20
  }'

Limitations

  • Sanctions lists update daily from OFAC, EU, and UN — newly sanctioned entities may lag up to 24 hours

    Sanctions lists updated daily from OFAC, EU, and UN sources — newly sanctioned entities may take up to 24 hours to appear

    What to do instead: For same-day compliance, subscribe to OFAC's RSS feed and cross-reference against today's additions

  • Name matching uses fuzzy logic and may produce false positives for common names

    Name matching uses fuzzy logic — common names may produce false positives. Always verify flagged results

    What to do instead: Filter results by match confidence score and verify flagged entities against the primary sanctions list PDF

Bundled checks that include it