Screen a customer or counterparty against consolidated sanctions and PEP data using the OpenSanctions match API
domain: opensanctions.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Choose the target dataset to match against (e.g. default for the full consolidated sanctions/PEP/crime dataset)
Call POST https://api.opensanctions.org/match/{dataset} with a schema value (e.g. Person or Company) and a properties object containing known identifiers (name, birthDate, country, etc.)
Optionally scope results with include_dataset or exclude_dataset to restrict which source lists are considered
Review the returned scored candidates, treating high-score matches as requiring manual review rather than auto-blocking
Re-run screening periodically for existing customers, since underlying sanctions/PEP data updates continuously
Known gotchas
Match scores are similarity-based, not identity-confirmed — a high score on a common name still requires human review before action is taken
Dataset selection matters: using a narrower dataset than 'default' can silently exclude relevant sanctions lists you intended to screen against
This is a public/open data source, not a commercial vendor SLA — validate its list coverage and update cadence against your specific regulatory requirement before relying on it as a sole screening source
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?