AML

Explain an AML risk score

An AML risk response is more than a number. The score, risk_level, confidence, and exposure array together explain why an address is rated as it is. Reading each field lets an analyst justify and record a decision.

はじめる前に
  • A live API key with AML scope.
  • An address whose score you need to explain.

1Request the risk score

Call the risk endpoint to retrieve the full response. This C3 call returns every field the explanation draws on.

curl https://api.1st-node.com/v1/aml/eth/0x3f9a.../risk \
  -H "Authorization: Bearer sk_live_..."
> { "score": 72, "risk_level": "high", "confidence": 0.86, "exposure": [{ "category": "mixer", "hops": 1 }] }

2Read the headline fields

The score is a 0-100 aggregate and risk_level is its coarse band. Confidence indicates how well the underlying attribution is established; a high score at low confidence merits review rather than an automatic block.

3Read the exposure array

Each exposure entry names a category and the hop distance to it. This is the substance of the score: mixer at hop 1 explains a high rating far more precisely than the number alone.

4Record the explanation

Store the full response with the decision so a reviewer can see exactly which fields drove the outcome. This is the audit-ready justification.

よくある質問

What is the difference between score and confidence?

Score is how risky the address is; confidence is how sure the attribution behind that score is. Treat them independently when deciding whether to act automatically.

Why does hop distance matter in the exposure?

Hops measure how directly the address touches a category. Hop 1 is direct; larger hops involve intermediaries and generally warrant lighter handling.

続けて読む

チャージして、キーを取得し、リリース。

セルフサーブ。暗号資産またはカードで支払い。クレジットで従量課金——重いプリミティブは高く、単純なものは安価。

APIキーを取得