Skip to main content
Use these addresses and parameters to test your Risk API integration. Each example produces a known, predictable result so you can verify correct parsing, display logic, and error handling.
All examples use real onchain data. Responses may shift over time as new threat intelligence becomes available, but the general risk profile of each address should remain stable.

Address Risk Score

Test addresses for the GET /v1/risk/address endpoint.

High Risk (Score 10 - Directly Malicious)

Low Risk (Score 1 - Clean Address)

Attribution Override (System Address)

This address demonstrates the attribution override: despite being close to malicious addresses, it scores 1 because it’s a verified system program.

Additional Test Addresses


Sanctions & Blacklist Check

Test addresses for the GET /v1/risk/sanctions endpoint.

Sanctioned Address

Expect is_ofac_sanctioned: true and is_sanctioned: true, with an ofac-sanctioned entry in sanctions.

Clean Address

Expect no sanctions or blacklist flags: is_sanctioned: false, an empty sanctions array, and lists_checked: true.

Additional Test Addresses


Payment Risk Assessment

Test parameters for the GET /v1/risk/payment endpoint.

Payment Response Fields

Use this sender and recipient to check response parsing. Read the returned risk level and factors rather than assuming a fixed scenario outcome.

Token Risk Assessment

Test mint addresses for the GET /v1/risk/token endpoint (Solana only).

Token Request

asset_address and network are required. The endpoint currently supports only network=solana.

Integration Checklist

Use this checklist to verify your integration handles all response variations:
1

Score 10 - Direct malicious hit

Call Address Risk Score with the high-risk address. Verify your UI displays the critical risk warning and reasoning text.
2

Score 1 with attribution

Call Address Risk Score with the Token Program address. Verify your UI correctly handles the attribution object and shows the override explanation.
3

Score 1 - Clean address

Call Address Risk Score with a low-risk address. Verify your UI handles empty maliciousAddressesFound arrays.
4

Payment with multiple risk factors

Call Payment Risk Assessment with the example sender and recipient. Verify your UI displays all individual risk_factors and the overall_risk_level.
5

Error handling

Send a request with an invalid address or missing parameters. Verify your integration handles 400 error responses gracefully.

Error Scenarios

Test these inputs to verify your error handling:

Invalid Token Address Response

GET /v1/risk/token returns HTTP 400 for asset_address=not_a_real_address with network=solana:
Last modified on October 8, 2026