Skip to main content
This guide shows the token assessment request and its validation errors, followed by a separate address risk request for a deployer.
Prerequisites: You need a Risk API key and familiarity with the Token Risk Assessment and Address Risk Score endpoints.

When to Use This

  • Exchanges - Before listing a new token for trading
  • DEX aggregators - Before including a token in routing
  • Portfolio trackers - Before displaying a token’s price and details
  • DeFi protocols - Before accepting a token as collateral or in liquidity pools
  • Wallet providers - Before showing token metadata to users

Step 1: Assess Token Risk

Submit the token’s mint address as asset_address to GET /v1/risk/token. Both asset_address and network are required; solana is the only supported network.

Unsupported Network

A request to GET /v1/risk/token with asset_address=EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v and network=ethereum returns HTTP 400:

Step 2: Check the Deployer Address

If you have identified the token deployer onchain, submit its address to the Address Risk Score endpoint. The request below uses a known high-risk address to demonstrate the request format.

What’s Next

Token Risk Assessment

Request parameters, documented response contract, and validation errors.

Understanding Risk Scores

Risk scoring methodology.
Last modified on October 8, 2026