The paid API
GET /api/v1/wallet/{address}/… accepts an EVM 0x address or a base58 Solana
address. What each route does with them:
A direct sanctions match works on any address the list carries, because that is
a string comparison against a published list. The proximity walk is what
needs transfer history, and that history is EVM.
The engine behind the wallet pages
The intelligence service advertises its own coverage per route, and reports it on its health endpoint rather than in a comment that can drift:
Clustering is the widest because it reads addresses and their relationships.
Bridge tracing is the narrowest because it matches transfers against a registry
of contracts, and that registry is EVM.
Solana, specifically
Solana is covered for identity and for token scoring, and not for the transfer-history capabilities. Separately from the wallet routes, the launch census is Solana-only: it records pool creations, what became of them, and which wallet created each one.What “supported” does not promise
- A supported chain is not a guarantee of an answer. A capability can cover
your chain and still return
insufficient_evidencebecause nothing is held about that particular address. - Coverage is not depth. Ethereum has the most history behind it; a newer chain on the same list has less, and a thinner answer is not a cleaner one.
- This page can go stale. The engine reports its own route coverage at
/health, and that is the authority if the two ever disagree.
Scienter analyses public blockchain records. A finding states what those records show and how confident we are; it is evidence, not proof of anyone’s identity, intent or wrongdoing, and an attribution we cite is the cited source’s. An empty result means not analysed, never safe. Nothing here is legal, tax or investment advice, or a recommendation to transact with any address or asset — see Disclaimers for the full text.