API reference · Bridges & wallets

Wallet stream

  • Elysium, HyperCore: Every event of the three layers touching one address.
  • HyperEVM: Every event of the three layers touching one address: on HyperEVM its bridge legs to HyperCore and Elysium (its HyperEVM swaps and transfers are not streamed: GET /v1/trades?trader=, /v1/transfers?address=).

WebSocket channel wallet on wss://api.femtos.xyz/v1/ws

Parameters

ParamInExample or valuesMeaning
addressfilter<creator> (Elysium); <address> (HyperCore, HyperEVM)The address: 0x, or a named wallet's handle
channelfilter(optional)Kinds to keep, comma list (or `channels`, a list): hc.trades, hc.orders, hc.ledger, hc.liquidations, hc.positions, bridge.transfers, elysium.trades, elysium.bridge (HyperCore)

Subscribe

Elysium

{"op":"subscribe","channel":"wallet","filter":{"address":"<creator>"}}

HyperCore, HyperEVM

{"op":"subscribe","channel":"wallet","filter":{"address":"<address>"}}

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

Response fields

FieldTypeMeaning
snapshot: trueWalletEvent[]last 50 events
dataWalletEventone event of the three layers touching the address: {channel, data}
billingheavythe snapshot a subscribe asks for counts as GET /v1/wallet/{address} (heavy); every other frame as one WebSocket message

Related: Bridges & wallets

  • Cross-layer wallet GET /v1/wallet/{address} Elysium, HyperCore, HyperEVM
    One address (or a named wallet's handle) on HyperCore, HyperEVM and Elysium, plus its latest events.
  • Swaps by wallet GET /v1/trades Elysium, HyperEVM
    Every swap a wallet sent (or a pool’s, a token’s), newest first, filterable by token, side, size and time.
  • Transfers by wallet GET /v1/transfers Elysium, HyperEVM
    ERC-20 transfers sent and received by a wallet, newest first, filterable by token, direction, size and time.
  • Ledger stream WS hc.ledger HyperCore
    Deposits, withdrawals, transfers and other non-trade balance moves.
  • Bridge movements GET /v1/bridges Elysium, HyperCore, HyperEVM
    Matched HyperCore ↔ HyperEVM transfers with 24 h stats.
  • Bridge stream WS elysium.bridge · bridge.transfers Elysium, HyperCore, HyperEVM
    Each HyperCore ↔ HyperEVM transfer, initiated then completed.
  • Bridge coverage GET /v1/bridges/coverage HyperCore, HyperEVM
    Every HyperCore ↔ HyperEVM leg since our data starts, paired with its other leg: matched share per direction and token, why the others are not, latency.

More

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