Tokens API

A second, independent token risk score

A second, independent risk read (0-100, higher means more risk) from a different source than the main security check; ETH, BNB and BASE only. Read alongside security, never averaged with it.

GET/api/external/token-analysis/token-score/{chain}/{mint}

Get a free API key Try it in the API reference

Chains

BNB Chain BNB
Ethereum ETH
Base BASE

Request

Send your key in the x-dex-data-key header. Replace each <placeholder> with a real value.

curl -H "x-dex-data-key: $DEXDATA_API_KEY" \
  "https://api.dexdata.io/api/external/token-analysis/token-score/BNB/<mint>"

Parameters
Parameter	Description
`chain` path · string · required	ETH, BNB and BASE only; every other chain returns 400.
`mint` path · string · required	The token mint address (Solana) or contract address (EVM).

Response fields

A JSON response. Every field is always present; null means the value could not be established, never zero.

Response fields of A second, independent token risk score
Field	Type	Description
`rugScore`	number \| null	A second, independent risk read (0-100, HIGHER = MORE RISK), normalised to this surface's convention from a source whose own scale runs the OPPOSITE way (higher = safer). `null` means the source had no reading at all — never read `null` as clean. Distinct from `security.rugScore`: read both, do not average them.
`updatedAt`	string \| null	When this reading was computed, ISO-8601 UTC, or `null` when unavailable.

Price per call

BNB Chain, Ethereum, Base: 100 credits

Charged only when the call succeeds. Prices as of 2026-10-30; the current ones are always in the API reference.

Security check, all at once
A second, independent risk model, not a subset or a replacement of the main security check.
A token's risk-score history over time
The same source's reading right now, with no history.
Lifetime transfer count
How many transfers a token has had in total, over its whole lifetime -- one running number, not a bounded list of events. Solana and RHC.
DCA flow against one counter-token
Recurring (DCA) order flow between this token and ONE named counter-token, split by direction -- not the token's whole DCA picture.
A token's own submitted description and social links
A project's own curated description, verified badge, and extended social links (Discord, GitHub, whitepaper) beyond what identity already publishes.
Which wallets hold the token together, as clusters?
Groups of connected holder wallets, largest share first: each cluster's share of supply, its wallets, the wallets linking them and the venues used in one time window. Evidence, not proof.

Start building with DexData today

Sign in, create a key and make your first call in a minute. Free credits every month, and you only pay for calls that succeed.

Get a free API key