AML

Screen a crypto deposit for AML risk

Before you credit an incoming deposit, screen the sender address. One REST call returns a risk level, a confidence value and an exposure breakdown by category and hop distance — enough to make and log an auditable decision.

Перед началом
  • A live API key (Bearer token) with a positive credit balance
  • The deposit's source address and chain

1Call risk-score on the source address

Pass the chain and address. The risk endpoint is C3-metered, so a small per-call credit cost applies.

curl https://api.1st-node.com/v1/aml/eth/0x9a..f2/risk \
  -H "Authorization: Bearer sk_live_..."

2Read the score and exposure

The response carries a 0–100 score, a normalized risk_level, a confidence value and an exposure array listing the illicit categories the address is connected to and how many hops away.

> { "score": 72, "risk_level": "high",
>   "confidence": 0.86, "source": "internal-graph",
>   "exposure": [{ "category": "mixer", "hops": 1 }] }

3Route the decision

Apply your own thresholds: credit low-risk deposits automatically, queue medium-risk for manual review, and hold high-risk until cleared. Persist the full response alongside the deposit for your audit trail.

4Monitor afterwards with KYT

For ongoing obligations, send the same transfer through transaction screening (KYT) so post-credit activity keeps generating decisions without a separate console.

Частые вопросы

What does a credit cost per screen?

Risk-score is a C3 primitive — heavier than a plain balance read but far cheaper than a per-seat dashboard license. You only pay per call.

Is the decision auditable?

Yes. Every response includes confidence and an exposure list (category, hops) you can store verbatim for regulators.

Читать дальше

Пополнили, получили ключ, запустили.

Полное самообслуживание. Оплата криптой или картой. Тарификация в кредитах — тяжёлые примитивы дороже, простые дёшевы.

Получить API-ключ