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.

What it answers

• Which on-chain wallets does a given FOMO handle control?
• Which handle is behind a given Solana or EVM address?
• Who follows a given trader, and who do they follow?
• Which verified identities hold a given token?

It never takes custody of funds, executes trades, or asks for a private key or seed phrase. It does not give financial advice or rank traders by profitability, and it does not publish an address it cannot verify.

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 verified state at the moment you ask.

• 03

  Clean REST API

  One flat JSON record — no envelope to unwrap — with stable error codes and a full OpenAPI spec that your API key unlocks. Built to drop into a data pipeline.

How it works

1. 01Forward
   GET /v2/user/handle/{handle}

   Resolve a FOMO trader handle to every verified wallet it controls, across Solana and EVM.

2. 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.

3. 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.fomoscan.sh/v2/user/handle/tradername

{
  "id": "a1f2…c3d4",
  "handle": "tradername",
  "name": "frank",
  "bio": "in the candle business",
  "banner": "https://…/a/9c1d…e2f0.webp",
  "profilePicture": "https://…/a/3e0e…5671.webp",
  "solanaAddress": "498g1rVn…jxkjAayQ",
  "evmAddress": "0x696d12…fa9d8e28"
}