# Risk Score API

The **Risk Score API** evaluates the risk level associated with a given address. When an address is assessed as high-risk, the API also returns detailed insights explaining the key factors contributing to that risk.

Please note that this API analyzes only the target address and its **one-hop** related addresses. For a comprehensive crypto-compliance solution—such as a fully featured **Know-Your-Address (KYA)** API—refer to the [**BlockSec Phalcon Compliance App**](https://blocksec.com/phalcon/compliance), which offers a free trial account.

## How is risk assessed?

When assessing the risk of an address, we take into account several key factors, including its type, attributes, associated entities, and on-chain interactions. The address type indicates whether it is an **EOA (Externally Owned Account)** or a **CA (Contract Account)**. The concepts of *attributes* and *entities* are [explored in detail in this document](https://docs.metasleuth.io/address-label-api#whats-an-address-label). On-chain interactions refer to the specific blockchain transactions and activities in which the address has participated.

Among the information involved in the assessment, certain factors influence the assessment strategy, while others serve as critical risk indicators that significantly affect the assessment results. The following are the leading risk indicators used in our methodology, which can also be obtained through [APIs](https://docs.metasleuth.io/blocksec-aml-api/apis#get-risk-indicators) requests to stay informed about any changes in risk indicators.

<table><thead><tr><th width="180">Risk Indicator</th><th width="86">Code</th><th>Description</th></tr></thead><tbody><tr><td>NO KYC</td><td>5020</td><td>The VASP (Virtual Asset Service Provider) associated with the address does not have a KYC (Know Your Customer) procedure in place.</td></tr><tr><td>BLOCKED</td><td>5018</td><td>The address has been blacklisted by critical contracts, primarily USDT and USDC.</td></tr><tr><td>SUSPICIOUS</td><td>5017</td><td>Address with suspicious activities.</td></tr><tr><td>COMPROMISED</td><td>5013</td><td>This address is deemed at risk, either due to being an externally owned account (EOA) with a weak key or a contract that is susceptible to exploitation.</td></tr><tr><td>GAMBLING</td><td>5016</td><td>The entity associated with this address is a gambling platform.</td></tr><tr><td>MIXING</td><td>5008</td><td>The address, primarily a contract, or associated service is believed to possess the capability to obfuscate fund flows.</td></tr><tr><td>LAUNDERING</td><td>5034</td><td>The addresses and entities associated with this label are believed to engage in money laundering activities.</td></tr><tr><td>CHILD ABUSE MATERIAL</td><td>5002</td><td>The entity associated with this address has been identified as forums and websites that facilitate the buying, selling, and distribution of child abuse material.</td></tr><tr><td>MIXER</td><td>5003</td><td>The entity associated with this address has been classified as a mixer.</td></tr><tr><td>DARKWEB BUSINESS</td><td>5001</td><td>This address has been involved in illicit businesses within the dark web.</td></tr><tr><td>DARK MARKET</td><td>5010</td><td>The entity associated with this address is a dark web marketplace.</td></tr><tr><td>ATTACKER</td><td>5012</td><td>This address is involved in a cyber attack.</td></tr><tr><td>RANSOMWARE</td><td>5009</td><td>The entity affiliated with this address is a ransomware group.</td></tr><tr><td>SCAM</td><td>5005</td><td>This address is engaged in fraudulent activities.</td></tr><tr><td>SANCTIONED</td><td>5006</td><td>The entity associated with this address has been sanctioned.</td></tr><tr><td>EXPLOIT</td><td>5040</td><td>The attacker or the attacker's contract or the attacker transfers funds and other addresses related to the attacker.</td></tr><tr><td>TERRORIST</td><td>5043</td><td>Entities that use violence or threats to intimidate populations or governments for political or ideological aims.</td></tr></tbody></table>

### Interpreting the risk score

Based on the risk assessment algorithm mentioned earlier, we classify an address's compliance risk into five levels, represented by **scores ranging from 1 to 5**. A higher score indicates a higher compliance risk associated with that address.

For addresses with a score of **4 or higher**, it is advisable to refrain from interacting with them. For addresses with a score of 3, it is recommended to carefully consider the accompanying indicators to determine whether it is appropriate to engage with them.

### Individual risk vs. Interaction risk

Based on how we identify risks, we categorize them into Individual and interaction risk&#x73;**. Individual risk primarily stems from the attributes and behavior of the address itself, while interaction risk arises from the address's involvement in risky on-chain transactions.**

By default, we consider Individual and interaction risks to provide the final result. However, due to the temporary lack of support for interaction risk in some networks (refer to the [Supported Networks ](#supported-networks)section) and the longer calculation time required for interaction risk, we offer the option to specify whether to include the calculation of interaction risk when requesting compliance risk for an address.

## Supported networks

<table><thead><tr><th width="207">Network Name</th><th width="172">Short Name</th><th width="117">Chain ID</th><th>Support for interaction risk</th></tr></thead><tbody><tr><td>Solana</td><td>SOLANA</td><td>-3</td><td><code>True</code></td></tr><tr><td>Tron</td><td>TRX</td><td>-2</td><td><code>True</code></td></tr><tr><td>Bitcoin Mainnet</td><td>BTC</td><td>-1</td><td><code>True</code></td></tr><tr><td>Ethereum Mainnet</td><td>ETH</td><td>1</td><td><code>True</code></td></tr><tr><td>Optimism Mainnet</td><td>OPTIMISM</td><td>10</td><td><code>True</code></td></tr><tr><td>Cronos Mainnet</td><td>CRONOS</td><td>25</td><td><code>False</code></td></tr><tr><td>BNB Smart Chain Mainnet</td><td>BSC</td><td>56</td><td><code>True</code></td></tr><tr><td>Gnosis</td><td>GNOSIS</td><td>100</td><td><code>False</code></td></tr><tr><td>Polygon Mainnet</td><td>POLYGON</td><td>137</td><td><code>True</code></td></tr><tr><td>BitTorrent Chain Mainnet</td><td>BITTORRENT</td><td>199</td><td><code>False</code></td></tr><tr><td>Fantom</td><td>FANTOM</td><td>250</td><td><code>False</code></td></tr><tr><td>Boba Network</td><td>BOBA</td><td>288</td><td><code>False</code></td></tr><tr><td>zkSync Era Mainnet</td><td>ZKSYNC ERA</td><td>324</td><td><code>False</code></td></tr><tr><td>CLV Parachain</td><td>CLV</td><td>1024</td><td><code>False</code></td></tr><tr><td>Polygon zkEvm</td><td>POLYGON ZKEVM</td><td>1101</td><td><code>False</code></td></tr><tr><td>WEMIX3.0 Mainnet</td><td>WEMIX</td><td>1111</td><td><code>False</code></td></tr><tr><td>Moonbeam</td><td>MOONBEAM</td><td>1284</td><td><code>False</code></td></tr><tr><td>Mantle</td><td>MANTLE</td><td>5000</td><td><code>True</code></td></tr><tr><td>Moonriver</td><td>MOONRIVER</td><td>1285</td><td><code>False</code></td></tr><tr><td>Base</td><td>BASE</td><td>8453</td><td><code>True</code></td></tr><tr><td>Arbitrum One</td><td>ARBITRUM</td><td>42161</td><td><code>True</code></td></tr><tr><td>Celo Mainnet</td><td>CELO</td><td>42220</td><td><code>False</code></td></tr><tr><td>Avalanche C-Chain</td><td>AVALANCHE</td><td>43114</td><td><code>True</code></td></tr><tr><td>Linea</td><td>LINEA</td><td>59144</td><td><code>True</code></td></tr><tr><td>Blast Mainnet</td><td>BLAST</td><td>81457</td><td><code>False</code></td></tr><tr><td>Aurora Mainnet</td><td>AURORA</td><td>1313161554</td><td><code>False</code></td></tr></tbody></table>

{% hint style="info" %}
**What does 'Support for interaction risk' mean?**

When evaluating risks, we distinguish between [Individual and Interaction risks](#individual-risk-vs.-interaction-risk) based on their origins. It is worth noting that calculating interaction risk may require additional resources that may not be readily available in specific networks. If a network supports Interaction risk, querying an address on that blockchain will yield a more thorough evaluation result.
{% endhint %}

## Subscription

{% hint style="success" %}
Subscribe to [our plan](https://metasleuth.io/plans#apis) to use this API in your service to help meet the compliance requirements and secure users' assets.
{% endhint %}