Monitor a wallet for ongoing risk
Ongoing monitoring rescreens a wallet after onboarding so new exposure is caught. Poll the risk and sanctions endpoints on a schedule and compare against the stored baseline. Record each cycle so risk drift over time is auditable.
- A live API key with AML scope.
- A stored onboarding baseline for the wallet.
1Rescreen the wallet's risk
On each monitoring cycle, request the current risk score. This C3 call returns the up-to-date score and exposure to compare against the baseline.
curl https://api.1st-node.com/v1/aml/tron/TXyz.../risk \
-H "Authorization: Bearer sk_live_..."
> { "score": 47, "risk_level": "medium", "confidence": 0.81, "exposure": [{ "category": "gambling", "hops": 2 }] }2Recheck sanctions
Run the C2 sanctions check each cycle as well, since lists change independently of on-chain activity.
curl https://api.1st-node.com/v1/aml/tron/TXyz.../sanctions \ -H "Authorization: Bearer sk_live_..."
3Detect drift from the baseline
Compare the new score and exposure against the stored baseline. A jump in score or a new exposure category triggers review.
4Record each cycle
Persist every monitoring result keyed to the wallet and timestamp. The series shows when risk changed and supports the audit trail.
Preguntas frecuentes
How often should monitoring run?
Set the cadence to your risk appetite and the wallet's tier. Higher-risk wallets warrant more frequent cycles; also rescreen on each new transaction.
What counts as meaningful drift?
A move across a threshold band or a newly appearing exposure category. Define the deltas that trigger review and store the comparison.
Sigue leyendo
Recarga, obtén tu clave y publica.
Autoservicio. Paga en cripto o con tarjeta. Medido por créditos: las primitivas pesadas cuestan más, las simples son baratas.
Obtener clave API