femtos

HyperCore · Bridge & wallet

Cross-layer wallet

One address (or a named wallet's handle) on HyperCore, HyperEVM and Elysium, plus its latest events.

GET https://api.femtos.xyz/v1/wallet/{address}

Parameters

ParamInExample or values
addresspath<address>

Example

curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/wallet/<address>"

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

Response fields

FieldTypeMeaning
hypercore.perpobjectaccount value, margin, positions with liquidation price
hypercore.spotobjectbalances with USD value
hyperevm · elysiumobjectbalances, NFTs, swaps / transfers and bridges on the other layers
bridgesobjectlegs in flight and journeys across the three layers
*.freshnessobjecteach section: head, headTime, lagMs, behindMs (as /api/status)
recent[]object{layer, kind: fill | ledger | bridge | swap | transfer, t, data}

Related: Bridge & wallet

  • Bridge transfers GET /v1/bridges
    Matched HyperCore ↔ HyperEVM transfers with 24 h stats.
  • Bridge coverage GET /v1/bridges/coverage
    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.
  • Bridge stream WS bridge.transfers
    Each HyperCore ↔ HyperEVM transfer, initiated then completed.
  • Wallet stream WS wallet
    Every event of the three layers touching one address.
  • Ledger stream WS hc.ledger
    Deposits, withdrawals, transfers and other non-trade balance moves.

More