proof-verified FOMO trader identity, always fresh.
Resolve a FOMO trader handle to the on-chain wallets they actually control — and go the other way, from wallet back to handle. Every wallet we return is a verified match, kept continuously fresh, over a clean REST API.
Why it’s different
- 01
Proof-verified
Every wallet we return is a verified match. If an address is in the response, it belongs to that trader — never a guess.
- 02
Always fresh
Each lookup reflects the latest verified state at the moment you ask — nothing is served from a stale snapshot, and a trader who has opted out is never returned.
- 03
Clean REST API
One flat JSON record — no envelope to unwrap — with stable error codes and a full OpenAPI spec published as interactive Swagger docs. Built to drop into a data pipeline.
How it works
- 01Forward
GET /v2/user/handle/{handle}Resolve a FOMO trader handle to every verified wallet it controls, across Solana and EVM.
- 02Reverse
GET /v2/user/wallet/{address}Go the other way: hand it a wallet and get the trader behind it, with their key on the other chain. No chain parameter — it is inferred from the address.
- 03By id
GET /v2/user/id/{id}Look a trader up by the id from a previous response. Handles change; the id does not, so it is what you store against your own records.
curl -H "Authorization: Bearer $FOMOSCAN_KEY" \
https://api-production-9541.up.railway.app/v2/user/handle/frankdegods{
"id": "a1f2…c3d4",
"handle": "frankdegods",
"name": "frank",
"bio": "in the candle business",
"banner": "https://…",
"profilePicture": "https://…",
"solanaAddress": "498g1rVn…jxkjAayQ",
"evmAddress": "0x696d12…fa9d8e28"
}identity for onchain.
1,000,000+ verified wallet → handle links. One credit balance, every endpoint.
no card required · we send your API keys and docs over Telegram
Something bigger?
The plans above cover most integrations. If you need higher volume, scoped entitlements per organization, or an enterprise agreement, tell us what you’re building and we’ll size a key for you.
