Authenticate using HMAC-SHA256 signed request headers — compute the signature over the HTTP method, Content-Type, date, and request path
POST to /v2/cases/screeningRequest with a CaseSystemId, secondaryFields (dateOfBirth, nationality), and a groupId corresponding to your screening configuration
Poll GET /v2/cases/{caseSystemId}/results or handle the webhook callback to retrieve the screened result
Filter results by the entityType and primaryName fields; use the category field to separate PEP hits from sanctions hits
For each ongoing customer relationship, resubmit a screening request at the interval required by your AML policy (typically monthly or on trigger events)
Known gotchas
World-Check uses a subscription-based data model — ensure your API key is provisioned for the risk entity categories you intend to screen
The HMAC signature must use the exact Date header value transmitted; clock skew of more than 15 minutes will cause 401 errors
Do not cache screening results beyond 24 hours without verifying that the underlying data has not changed
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp