Skip to main content

Integration profile

Chainalysis KYT

AutoKYC integrates Chainalysis KYT to evaluate crypto transactions and wallet exposure alongside traditional KYC/KYB evidence. Rules combine blockchain heuristics with sanctions screening, triggering ODD or EDD workflows when risky counterparties are detected.

SaaS + Managed Services Coverage: 150+ crypto assets with behavioural clustering Data residency: US, EU
Discuss integration rollout View developer documentation

Why teams pair with Chainalysis KYT

  • Unified risk scores merge blockchain exposure with identity results in the case graph.
  • Rules engine pauses payouts or onboarding when Chainalysis flags sanctioned or ransomware-linked wallets.
  • Managed analysts receive queue-ready narratives with on-chain evidence and recommended actions.

Use cases

Crypto exchange onboarding

Screen customer deposit addresses during onboarding and trigger enhanced verification when exposure exceeds defined thresholds.

Ongoing transaction monitoring

Run real-time KYT checks on withdrawals and settlements, escalating to operations when suspicious flows emerge.

Regulatory reporting

Generate SAR-ready evidence packages that combine Chainalysis findings with KYC and KYB data.

Setup steps

  1. 1

    Enable API access

    Provision Chainalysis API keys with least privilege and store them using AutoKYC-managed secrets rotation.

  2. 2

    Configure asset coverage

    Select supported assets and service-specific risk rules, then map them to AutoKYC monitoring policies.

  3. 3

    Align escalation thresholds

    Define score thresholds that trigger AutoKYC’s voting engine, pause payouts, or notify compliance leadership.

Implementation notes

  • Webhook retries are handled automatically; monitor Chainalysis health in AutoKYC dashboards.
  • Backfills can be scheduled to re-evaluate legacy transactions after policy updates.

Operational considerations

  • Restricted in jurisdictions where Chainalysis is not licensed to operate.
  • Historical lookbacks beyond three years may require asynchronous batch processing.
  • Requires separate fiat AML coverage for non-crypto entities.