Implement Know Your Transaction (KYT) monitoring by submitting a cryptocurrency transfer to the Chainalysis KYT API and retrieving the risk exposure
domain: docs.chainalysis.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a transfer via POST /api/kyt/v2/users/{userId}/transfers with the asset, network, transferReference, direction, and transferTimestamp
Retrieve the risk assessment via GET /api/kyt/v2/transfers/{externalId}/summary once the transfer has been processed
Inspect the riskScore (low, medium, high, severe) and the exposures array which lists counterparty categories and percentage contributions
Apply your policy: automatically flag transfers with riskScore of high or severe for compliance review; reject or freeze funds for severe scores above your threshold
Use the clusterName and clusterCategory fields in the exposures to determine whether the counterparty is a sanctioned entity, darknet market, or mixer
Known gotchas
KYT transfer registration is asynchronous; the risk summary is not immediately available — poll or implement a webhook (Reactor alert) for production use
Direct and indirect exposure are both reported; understand the difference — indirect exposure through one hop may be treated differently in your risk policy
Transaction monitoring rules under FinCEN and FATF Travel Rule require retaining transfer metadata; KYT alone does not satisfy Travel Rule originator/beneficiary data requirements
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