# Screen a person or company against sanctions, PEP and adverse media lists

> Screen a person or company against sanctions, PEP and adverse media lists: 4 companies fully do it, 10 with a limit, 16 carry the tag. Every listing in Identity & business verification with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/identity-verification.screen-watchlist/
- Markdown: https://www.anchorterminal.com/niches/identity-verification.screen-watchlist/index.md (~1,700 tokens)
- Slim: https://www.anchorterminal.com/niches/identity-verification.screen-watchlist/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/identity-verification.screen-watchlist/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 4 | 10 | 16 | 10 | 3 |

## What counts as done

Each screen returns no match, potential match or confirmed match with the list name, the matched entity and a match strength, and a potential match can be routed to a human; the subject can be enrolled in ongoing monitoring that raises a new alert when lists change.

How agents ask for it: is this person on a sanctions list; run AML screening on this company; check this payee against OFAC; keep these customers under monitoring

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Didit (Didit Identity Spain, S.L.)**: AML screening against 1,300+ sanctions, PEP and adverse media sources returns each potential match with a match score and risk score, In Review routes to a human, and include_ongoing_monitoring re-screens daily.
- **Shufti (Shufti Pro Limited)**: AML screening returns each hit with a match type from name_exact to phonetic and synonym matches, list filters (sanction, PEP classes, warning), declined_codes, and ongoing: 1 enrols the subject in monitoring.
- **Sumsub (Sum and Substance Ltd)**: Run AML check and Get AML case data return each hit with sources, nameMatchScore and matchStatus (true_positive, false_positive); Update AML Hit Review resolves a hit, and ongoing monitoring applies new alerts on a daily cycle.
- **Veriff (Veriff OÜ)**: Enhanced AML screening sets lists and match strictness, GET watchlist-screening returns hits, GET person details a match, PATCH reviews a hit, and ongoing monitoring sends a new webhook when a verified person's status changes.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **ComplyAdvantage (IVXS UK Limited (trading as ComplyAdvantage))**: Create and screen a customer returns alerts holding matched profiles that a reviewer marks risk or no risk, monitoring is set per customer, and webhooks retry with a stable webhook-id. Match strength fields weren't confirmed and there is no free tier.
- **ComplyCube (Teemo Technology Ltd)**: AML Screening covers sanctions, PEP and adverse media with continuous monitoring and alerts, and POST /checks/:id/validate confirms or rejects a potential match. No match strength field was confirmed in the pages read.
- **Entrust Identity Verification (formerly Onfido) (Onfido Ltd)**: Watchlist AML, enhanced, PEP-only and sanctions-only reports, plus watchlist_monitors whose matches can be listed and enabled or disabled, and new_report to rescreen. Match strength and refresh frequency are not in the files read.
- **Jumio (Jumio Corporation)**: A workflow can include watchlist screening and the account request can override the search profile; screening is configured through a linked ComplyAdvantage portal, and the hit schema wasn't read.
- **Middesk (Middesk, Inc.)**: Every business created is screened against OFAC and global watchlists with potential matches flagged for review, plus PEP and adverse media add-ons. Screening runs inside a business order, not as a standalone person screen, and match strength wasn't confirmed.
- **Persona (Persona Identities, Inc.)**: Watchlist and PEP reports run by API inside a transaction, which goes to needs_review on a hit. The guide read shows no list name or match strength fields, and recurring monitoring wasn't read.
- **Plaid Identity Verification (Plaid Inc.)**: Monitor screens against sanction and PEP lists, returns cleared or pending_review, supports rescan programs and API review, but is a separate product not enabled in Sandbox by default and needs a Production request.
- **Socure RiskOS (Socure Inc.)**: Watchlist screening runs inside an evaluation workflow, and /api/evaluation/monitoring enrols an evaluation in daily monitoring for list changes. The hit schema (list, entity, strength) wasn't read.
- **Trulioo (Trulioo Information Services Inc.)**: Trulioo Watchlist checks sanctions, PEP and adverse media and appends detail on a potential match for the client to judge. Standalone aml_screen and monitoring are off unless entitled, and no match strength field was confirmed.
- **Vouched (Vouched Identity, Inc.)**: AML Enhanced Screening and Monitoring returns match status and monitoring alerts for a job, but the standalone AML job shuts down on 2027-01-31 and AML sits on custom plans; match strength fields weren't confirmed.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Alloy (First Mile Group, Inc.)**: Not read: Alloy's Terms of Service forbid robots and automatic data gathering on alloy.com and related sites, so developer.alloy.com was not opened and no independent source covers this.

- not this job: Stripe Identity (Stripe, LLC): Stripe Identity covers document, selfie and US SSN checks only; no sanctions or PEP screening endpoint exists in the Identity docs.

## What stops agents finishing

- potential match needs a human decision
- screening sold only inside a contracted bundle
- screening not entitled on the account (Trulioo notes)

## Around it

Before: identity-verification.verify-person, identity-verification.verify-business. After: identity-verification.review-case, human-in-the-loop.request-review.

## Where this comes from

Weight 10 of 100 in Identity & business verification: 3 of 34 accounts (a builder who wrote his own screening API on cost, a marketplace blocking OFAC wallets, a launch plan that calls screening non-negotiable); raised above count because every regulated buyer needs it and five listings sell it

As data: https://www.anchorterminal.com/api/v1/use-cases/identity-verification.screen-watchlist.json, or the MCP tool get_use_case with id identity-verification.screen-watchlist. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
