Wallet Compliance Report
Generate a compliance risk report for a wallet address.
risk_score is the maximum of the named ADVERSE lanes in risk_breakdown (sanctions match, sanctioned counterparties, behavioral intents, other adverse risk flags) — so the headline never disagrees with its breakdown, and benign heuristics (volume, wallet class) never drive it. A mixer touch is DISCLOSED in mixer_touch but does NOT score (its authorship is unverified — direction-agnostic with no dusting filter — so, mirroring the signed report, an inbound dusting victim never reads elevated here). Likewise the profiler's unverified sanctioned_interaction remnant-label flag is DISCLOSED, non-scoring, in sanctioned_interaction (the live sanctioned-counterparties lane does the real scoring). sanctions_screened is always true (that lane runs live for every address); risk_lanes_screened is true only when a wallet profile was available to assess the behavioral/flag lanes — when it is false and nothing was found, risk_level is "unknown" (unscreened), never "low". A malformed address returns 422.
Request
- Base URL: https://api.bitpoort.com (the document declares no server; this is the origin it was published from)
- URL: https://api.bitpoort.com/v1/wallets/compliance/{address}
- Auth: one of:
- API key in header X-API-Key
- HTTP bearer
Path parameters
Query parameters
Chain to check
Response
Successful Response
Changes
No recorded changes to this operation across all 1 revision of this API.