API reference · Named wallets

Named wallets

Every named entity, its X account, kinds, sources and wallets.

GET https://api.femtos.xyz/v1/entities

Parameters

ParamInExample or valuesMeaning
qquery(optional)Name, X handle, alias, wallet address or handle
kindquery(optional)Entities: named (people, funds, pseudonyms from public sources), cluster (anonymous smart-money clusters: HyperCore traders selected on their results), all, or a kind it contains (whale, market maker…). Default: all
confidencequery(empty), high, medium, low, unratedEntities with at least one wallet of this confidence
viaquery(empty), list, bridge, subaccount, transfer, vault-leader, self-declared, smart-money, smart-money-linkEntities with at least one wallet found this way (`via` of the wallets)
sortquerydefault, wallets, name, pnldefault: the registry order (our research first); wallets: most wallets first; name; pnl: smart-money net PnL first
cursorquery(optional)Next page: `next_cursor` of the previous answer

Example

Elysium, HyperCore, HyperEVM

curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/entities"

Key: Authorization: Bearer $FEMTOS_KEY. Get a free key, or with no browser through agent onboarding.

Response fields

FieldTypeMeaning
entities[]object{id, name, x, kinds, confidence, aliases, sources, wallets, smartMoney}
entities[].wallets[].addressstringWallet: 0x address, or a named wallet's handle
entities[].wallets[].vialist | bridge | subaccount | transfer | vault-leader | self-declared | smart-money | smart-money-linkHow the wallet was found: list (a public list or our research names it), bridge (cross-chain bridges with a wallet of the entity, Solana ones included), subaccount (a HyperCore sub-account), transfer (HyperCore sends both ways), vault-leader (leads the vault), self-declared (verified on Farcaster by the X account), smart-money (selected on its HyperCore results), smart-money-link (linked to such a wallet)
totalintEntities matching
facetsobjectCounts over the entities matching `q` and `kind`, before the `confidence` and `via` filters: what each filter value would select: {entities, wallets, groups, confidence, via}
next_cursorstring | nullOpaque cursor of the next page: pass it as `cursor`, unchanged. null on the last page

Next page: cursor = the next_cursor of the previous answer, the same on every list (pagination).

Related: Named wallets

  • One entity GET /v1/entities/{id} Elysium, HyperCore, HyperEVM
    One named entity: its wallets on the three layers and 30 days of HyperCore trading.
  • Entity proofs GET /v1/entities/{id}/graph Elysium, HyperCore, HyperEVM
    How each wallet of an entity was found: the path of links back to a public source and their proofs.
  • KOL leaderboard GET /v1/kols/leaderboard Elysium, HyperCore, HyperEVM
    KOLs, traders and funds ranked by their HyperCore PnL, volume and open positions.
  • KOL moves GET /v1/kols/activity Elysium, HyperCore, HyperEVM
    The latest fills of the named wallets, newest first, with who traded.
  • KOL stream WS kol.activity Elysium, HyperCore, HyperEVM
    Every fill, liquidation, EVM swap, transfer and bridge leg of a named wallet, live.

More

Agent guide (agents.md)llms.txtOpenAPIMCP serverGet an API keyChangelog