> For the complete documentation index, see [llms.txt](https://www.bokk.ltd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.bokk.ltd/readme/v3/4.-wallet-address-risk-screening-api.md).

# 4. Wallet Address Risk Screening API

#### Description

Performs risk screening on a wallet address.

This endpoint **does not** execute rule engine–configured strategies and **does not** evaluate any private data configured by the user in the KYT system.

***

### 1. Endpoint URL

```
GET /openapi/v3/risk/address/screening
```

***

### 2. Request Parameters

| Parameter | Type   | Required | Description    |
| --------- | ------ | -------- | -------------- |
| apikey    | string | true     | API key        |
| chain     | string | true     | Main chain     |
| address   | string | true     | Wallet address |

***

### 3. Response Parameters

```
{
  "code": 200,
  "message": "success",
  "data": {
    "unique_id": "0140......8be5",
    "tcr_score": 41,
    "risk_level": "severe",
    "risk_types": [
      "Stolen Crypto"
    ],
    "risk_tags": [
      "Theft",
      "Stolen Crypto"
    ],
    "risk_detail": {
      "is_blacklist_address": true,
      "hit_direct_risk_review": false,
      "hit_indirect_risk_review": true,
      "hit_aml_review": true
    }
  }
}
```

***

## Response Field Description

<table><thead><tr><th width="117.078125">Field</th><th width="112.46484375">Type</th><th>Description</th></tr></thead><tbody><tr><td>code</td><td>int</td><td>Business status code. <code>200</code> indicates success; other values indicate failure (refer to actual error codes returned).</td></tr><tr><td>message</td><td>string</td><td>Response status message, e.g., <code>success</code>.</td></tr><tr><td>data</td><td>object</td><td>Response data object.</td></tr></tbody></table>

***

## `data` Field Description

<table><thead><tr><th width="116.4140625">Field</th><th width="117.21875">Type</th><th>Description</th></tr></thead><tbody><tr><td>unique_id</td><td>string</td><td>Unique request ID (used for tracking and troubleshooting).</td></tr><tr><td>tcr_score</td><td>int</td><td>Address risk score (TCR Score). A higher value indicates a higher level of risk.</td></tr><tr><td>risk_level</td><td>string</td><td>Risk level: <code>severe</code>, <code>high</code>, <code>medium</code>, <code>low</code>, <code>none</code> (no risk detected or unknown).</td></tr><tr><td>risk_types</td><td>string[]</td><td>Risk type array (high-level categories), e.g., <code>["Stolen Crypto"]</code>.</td></tr><tr><td>risk_tags</td><td>string[]</td><td>Risk tag array (more granular labels), e.g., <code>["Theft","Stolen Crypto"]</code>.</td></tr><tr><td>risk_detail</td><td>object</td><td>Risk detail object (description of matched risk conditions).</td></tr></tbody></table>

***

## `risk_detail` Field Description

<table><thead><tr><th width="207.37109375">Field</th><th width="119.75390625">Type</th><th>Description</th></tr></thead><tbody><tr><td>is_blacklist_address</td><td>boolean</td><td>Whether the address is classified as a blacklist address (based on the platform’s public risk database).</td></tr><tr><td>hit_direct_risk_review</td><td>boolean</td><td>Whether direct risk review rules were triggered.</td></tr><tr><td>hit_indirect_risk_review</td><td>boolean</td><td>Whether indirect risk review rules were triggered.</td></tr><tr><td>hit_aml_review</td><td>boolean</td><td>Whether AML review rules were triggered.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.bokk.ltd/readme/v3/4.-wallet-address-risk-screening-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.