Skip to main content
Glama
fairquery-sanctions-screener

fairquery-sanctions-screener

Official

Screen names against sanctions lists

screen_names
Read-onlyIdempotent

Fuzzy-screen person and organisation names against OFAC, EU, UK and UN sanctions lists to support KYC/KYB onboarding and counterparty checks.

Instructions

WHAT: Fuzzy-match people or organisation names against the OFAC SDN, OFAC Consolidated (non-SDN), EU, UK and UN sanctions lists, from the official sources (cached in your Apify account for at most 6 h, otherwise re-downloaded; each row reports list publication dates). Order-, case- and diacritics-insensitive; optional country and date-of-birth filters per name. WHEN TO USE: KYC/KYB onboarding, vendor or counterparty checks, bulk re-screening of customer lists. Put all names into one call (lists are downloaded once per run). WHEN NOT TO USE: to see which lists/authorities are covered or to cite sources, call list_sources (free); to see how fresh the cached lists are, list_cache_status (free). Not a PEP or adverse-media check (see LIMITS). COST: paid. Runs Apify Actor fairquery/sanctions-watchlist-screener with your APIFY_TOKEN; pay-per-event "name-screened": $0.003 per name that gets a screening row, match or no match, plus a $0.007 start fee per call (one run); nothing is charged per name if no list could be loaded, and error rows are free. 200 names in one call ~ $0.61. Lists load in ~2-5 s from a cache in your Apify account (at most 6 h old) or ~10-40 s when re-downloaded, then hundreds of names/s. RETURNS: one type="screening" row per name (status potential_match | no_match; matches[] best first, each with list, entry id, score, country_match and dob_match) or free type="error" rows (code, message). EXAMPLE: {"queries":[{"name":"Banco Nacional de Cuba","entityType":"entity"}],"minScore":90} -> one screening row, status potential_match with OFAC_SDN matches. PARAMETERS: names and/or queries: at least one is required although the schema marks both optional (neither -> a free INPUT_EMPTY error row); both may be combined and every entry is billed once, so send all names in ONE call (one start fee and one list load per run). Use names for bare strings and queries when you have per-name country / dateOfBirth / entityType or want your own id echoed. Per query, dateOfBirth drops listed individuals whose recorded birth year differs by more than 1 year (entries without a DOB are kept); country only sets country_match (true/false/null) unless excludeNonMatchingCountry=true, which then drops matches whose listed countries exclude it (entries without country data are kept). entityType: a query's own value wins over the top-level one; "entity" means anything that is not an individual (organisations, vessels, aircraft), and list entries of unknown type always pass. lists: omit for all five; a list whose download fails is reported in lists_unavailable rather than failing the run. minScore: a candidate is returned only if its 0-100 name similarity is >= minScore; it does not change the price - 85 default, 90-95 for large batches with fewer false positives, 75-80 for transliterated names. maxMatchesPerName trims matches[] (best first) but match_count still counts all. LIMITS: Not a certified screening service. Automated fuzzy matching against public lists downloaded at run time; results can contain false positives and miss matches. Review every potential match manually and consult official sources and legal counsel before acting.

Input Schema

NameRequiredDescriptionDefault
listsNoOptional, default all five. Any subset of "OFAC_SDN" | "OFAC_CONS" | "EU" | "UK" | "UN" (ids from list_sources). Example: ["OFAC_SDN","EU"]
namesNoOptional if queries is given (at least one of the two is required). Plain person or organisation names (non-empty strings, any order/case/diacritics); billed per name like queries. Example: ["Vladimir Putin","Acme Trading LLC"]
queriesNoOptional if names is given. {name, id?, country?, dateOfBirth?, entityType?} objects with per-name filters; billed per entry like names. Example: [{"name":"Ali Khamenei","id":"cust-42","country":"IR","dateOfBirth":"1939","entityType":"individual"}]
minScoreNoOptional integer 60-100, default 85. Minimum 0-100 fuzzy name-similarity score for a match. Use 90+ for fewer false positives, ~80 for more recall. Example: 90
entityTypeNoOptional, one of "any" | "individual" | "entity", default "any". Entity filter for all names; a query's own entityType wins. Example: "entity"
maxMatchesPerNameNoOptional integer 1-100, default 10. Top matches returned per name (best first); match_count still reports the total. Example: 3
excludeNonMatchingCountryNoOptional boolean, default false. true removes matches whose listed countries do not include the query country (entries without country data are kept). No effect without queries[].country.

Output Schema

NameRequiredDescriptionDefault
countYesNumber of rows in items
itemsYesDataset rows: type=screening or type=error

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.5
    • changedInput schema / properties / names / description
      Previous value: -"Optional if queries is given (at least one of the two is required). Plain person or organisation names (non-empty strings, any order/case/diacritics); $0.003 each. Example: [\"Vladimir Putin\",\"Acme Trading LLC\"]"New value: +"Optional if queries is given (at least one of the two is required). Plain person or organisation names (non-empty strings, any order/case/diacritics); billed per name like queries. Example: [\"Vladimir Putin\",\"Acme Trading LLC\"]"
    • changedInput schema / properties / queries / description
      Previous value: -"Optional if names is given. {name, id?, country?, dateOfBirth?, entityType?} objects with per-name filters; $0.003 each. Example: [{\"name\":\"Ali Khamenei\",\"id\":\"cust-42\",\"country\":\"IR\",\"dateOfBirth\":\"1939\",\"entityType\":\"individual\"}]"New value: +"Optional if names is given. {name, id?, country?, dateOfBirth?, entityType?} objects with per-name filters; billed per entry like names. Example: [{\"name\":\"Ali Khamenei\",\"id\":\"cust-42\",\"country\":\"IR\",\"dateOfBirth\":\"1939\",\"entityType\":\"individual\"}]"
  2. Changed13 schema fields changedv1.0.2
    • addedInput schema / properties / entityType / description
      Added value: +"Optional, one of \"any\" | \"individual\" | \"entity\", default \"any\". Entity filter for all names; a query's own entityType wins. Example: \"entity\""
    • addedInput schema / properties / excludeNonMatchingCountry / description
      Added value: +"Optional boolean, default false. true removes matches whose listed countries do not include the query country (entries without country data are kept). No effect without queries[].country."
    • changedInput schema / properties / lists / description
      Previous value: -"Default: all five"New value: +"Optional, default all five. Any subset of \"OFAC_SDN\" | \"OFAC_CONS\" | \"EU\" | \"UK\" | \"UN\" (ids from list_sources). Example: [\"OFAC_SDN\",\"EU\"]"
    • addedInput schema / properties / maxMatchesPerName / description
      Added value: +"Optional integer 1-100, default 10. Top matches returned per name (best first); match_count still reports the total. Example: 3"
    • changedInput schema / properties / minScore / description
      Previous value: -"Default 85"New value: +"Optional integer 60-100, default 85. Minimum 0-100 fuzzy name-similarity score for a match. Use 90+ for fewer false positives, ~80 for more recall. Example: 90"
    • changedInput schema / properties / names / description
      Previous value: -"Names to screen"New value: +"Optional if queries is given (at least one of the two is required). Plain person or organisation names (non-empty strings, any order/case/diacritics); $0.003 each. Example: [\"Vladimir Putin\",\"Acme Trading LLC\"]"
    • changedInput schema / properties / queries / description
      Previous value: -"Names with optional country (ISO-2 or name), dateOfBirth (YYYY or YYYY-MM-DD), entityType"New value: +"Optional if names is given. {name, id?, country?, dateOfBirth?, entityType?} objects with per-name filters; $0.003 each. Example: [{\"name\":\"Ali Khamenei\",\"id\":\"cust-42\",\"country\":\"IR\",\"dateOfBirth\":\"1939\",\"entityType\":\"individual\"}]"
    • addedInput schema / properties / queries / items / properties / country / description
      Added value: +"Optional. ISO 3166-1 alpha-2 code (\"IR\") or English country name (\"Iran\"); adds country_match to each match (filters only with excludeNonMatchingCountry=true)"
    • addedInput schema / properties / queries / items / properties / dateOfBirth / description
      Added value: +"Optional. Format YYYY or YYYY-MM-DD, e.g. \"1939\" or \"1939-04-19\"; drops listed individuals whose birth year differs by more than 1 year"
    • addedInput schema / properties / queries / items / properties / entityType / description
      Added value: +"Optional, one of \"individual\" | \"entity\" | \"any\"; default = top-level entityType. \"entity\" = organisations, vessels, aircraft"
    • addedInput schema / properties / queries / items / properties / id / description
      Added value: +"Optional. Your own reference echoed in the output row, e.g. \"cust-42\""
    • addedInput schema / properties / queries / items / properties / name / description
      Added value: +"Required. Person or organisation name to screen (non-empty), e.g. \"Ali Khamenei\""
    • addedOutput schema / properties / count / description
      Added value: +"Number of rows in items"
  3. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes far beyond the readOnly/openWorld/idempotent annotations: it discloses cache lifetime (6 h), load latency (~2-5 s cached, ~10-40 s re-downloaded), throughput, the exact pay-per-event price model ($0.003/name + $0.007 start fee, error rows free), billing for non-matches, and that failed list downloads degrade to lists_unavailable rather than failing the run.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Long but deliberately so for a complex, paid, cost-incurring tool. Sections are labelled (WHAT / WHEN TO USE / WHEN NOT TO USE / COST / RETURNS / EXAMPLE / PARAMETERS / LIMITS), front-loaded with purpose and cost, and each section carries non-redundant operational facts.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, yet the description still summarises the row shapes (type=screening with status/matches[] vs. free type=error rows) and adds an end-to-end example. Cost, latency, limits/liability caveats, and edge cases (INPUT_EMPTY, lists_unavailable) are all covered, so nothing an agent needs to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3), but the description adds meaning the schema cannot: it flags that names and queries are both schema-optional yet at least one is required, explains billing per entry, entityType precedence (query value wins), dateOfBirth ±1-year drop behavior, country semantics with excludeNonMatchingCountry, and minScore tuning guidance (90-95 large batches, 75-80 transliterated).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: 'Fuzzy-match people or organisation names against the OFAC SDN, OFAC Consolidated (non-SDN), EU, UK and UN sanctions lists.' It names the exact sources and matching semantics (order-, case-, diacritics-insensitive), and the WHEN NOT TO USE section explicitly differentiates it from the siblings list_sources and list_cache_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit WHEN TO USE (KYC/KYB onboarding, vendor/counterparty checks, bulk re-screening) and WHEN NOT TO USE with named alternatives (list_sources for coverage/citation, list_cache_status for freshness). It also states the batching condition — put all names into one call — leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools