Products

Compliance workflows built for crypto teams

AMLBot centralizes wallet screening, KYC and KYB, continuous monitoring, investigations, and API deployment so operations and compliance can move inside one flow.

AML Screening

Screen wallets before funds move

Run checks against sanctions, scam clusters, stolen funds, mixers, darknet exposure, and other risky categories before accepting deposits or counterparties.

  • Single-wallet checks for manual reviews
  • Risk score, category breakdown, and trace context
  • Ready for onboarding, treasury, and support teams
See analysis outputs
KYT Monitoring

Track risk continuously, not once

Use recurring monitoring for incoming and outgoing activity, then escalate only the cases that cross your business thresholds.

  • Rules by source type, score, and counterparty behavior
  • Useful for exchanges, brokers, and OTC desks
  • Built to reduce manual queue noise
Compare plans
KYC

Onboard individuals with fewer handoffs

Move identity verification, review checks, and audit notes into one internal process so onboarding stays fast without dropping documentation quality.

  • Manual and semi-automated review flows
  • Built for audit-ready case records
  • Good fit for new account approval paths
Start onboarding
KYB

Validate business counterparties

Collect entity details, ownership context, and risk notes in one view before you approve B2B relationships or higher-value transaction channels.

  • Useful for merchant, OTC, and partnership approval
  • Supports internal review checkpoints
  • Keeps case files consistent across teams
Review verification flow
Investigations

Trace incidents and document recovery work

When a case moves beyond routine screening, AMLBot gives your team a structured way to review chains, cluster behavior, and recovery evidence.

  • Supports scam, theft, and suspicious routing cases
  • Clear handoff from support to investigation team
  • Useful for partner updates and evidence packaging
Talk to investigations
API Documentation

Ship checks inside your own product

Use the API layer when you need screening or review triggers directly in your internal tooling, customer flows, or analyst dashboards.

  • Designed for operational integration, not just manual use
  • Good fit for pre-trade, deposit, and risk review hooks
  • Lets engineering and compliance share one standard
Talk implementation
Deployment

How teams usually launch

Most projects start with manual checks, then add API triggers, recurring monitoring, and a defined escalation path between operations and analysts.

1. Define the review scope

Choose which customers, wallets, or flows need mandatory screening and which ones only need analyst review.

2. Set thresholds and ownership

Document who handles alerts, when an issue escalates, and which cases require deeper tracing.

3. Connect onboarding, monitoring, and reporting

Make sure product, support, and compliance all use the same case record and response logic.