Risk Score Overview
The Webacy API returns an overallRisk score from 0 to 100, where higher scores indicate greater risk.
Risk levels are guidelines and may need adjustment for your specific use case. We recommend examining the response fields and specific issue tags to build more robust, customized risk policies.
Risk Classifications
Response Fields
The API returns several risk-related fields:
overallRisk vs issues[].riskScore
These fields look similar but are not interchangeable:
overallRisk is a number (e.g. 31.62) rolled up across every issue on the address. Use it as the top-level score for the address.issues[].riskScore is a string label (e.g. "Medium Risk") scoped to a single issue, not the whole address. It categorizes that one finding based on its score and is not a rewording of overallRisk.
An address can therefore have a single "Medium Risk" issue that contributes to an overallRisk value in the low-risk numeric range, or several "Low Risk" issues that push the aggregate overallRisk higher. Always compare overallRisk against the numeric ranges above rather than reading it from a per-issue riskScore.
Issue Severity Levels
Individual risk issues have their own severity:
Calculating Custom Risk Scores
You can build custom risk logic using the raw data:
Using Modules for Targeted Analysis
Use modules to request specific risk categories:
- Security-focused:
security_essentials, token_security, fraud_detection
- Compliance-focused:
sanctions_compliance, mixer_detection
- Investment-focused:
holder_analysis, liquidity_analysis, market_data
When using modules, the risk score reflects only the selected modules, not a comprehensive assessment.
Best Practices
- Don’t rely solely on
overallRisk - Review individual issues for context
- Consider the use case - Trading apps may weight different risks than compliance tools
- Use appropriate modules - Select modules relevant to your risk assessment needs
- Combine with other signals - Use risk scores alongside your own business logic
