API reference · Bridges & wallets
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
| Param | In | Example or values | Meaning |
|---|---|---|---|
address | path | <creator> (Elysium); <address> (HyperCore); <owner> (HyperEVM) | 0x address, or a named wallet's handle <entityId>.<hex> |
includeSpam | query | (empty), true | Show spam tokens (tokens.spam: homoglyph, impostor, fake transfers…), flagged spam / spamReason; hidden from lists and USD totals by default (HyperEVM) |
Example
Elysium
curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/wallet/<creator>"HyperCore
curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/wallet/<address>"HyperEVM
curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/wallet/<owner>"Key: Authorization: Bearer $FEMTOS_KEY. Get a free key, or with no browser through agent onboarding.
Response fields
| Field | Type | Meaning |
|---|---|---|
hypercore | object | {perp:{accountValue, positions[]}, dexes[], spot:{balances[], totalUsd}, freshness:{source: info-server, asOf, latencyMs, state, head, headTime, lagMs}} or {unavailable}: live state from the node info server; head = the HyperCore block of the fills ingested |
hyperevm | object | {balances:[{token, symbol, name, decimals, amount, priceUsd, usd, spam, spamReason, family?}], count, totalUsd, totalUsdComplete, includeSpam, spamHidden, height, asOf, syncing?, dataUntil?, nfts, activity, freshness, bridges:[core_evm rows]}: token balances at the indexed head (token-family tokens at balanceOf from their formula), USD at the pool prices of the last daily close; {balances:{unavailable}} when the database cannot answer. nfts: {erc721, erc1155, capped, collections[≤20]:{address, name, symbol, erc721, erc1155}, tokens[≤20]}. activity: {scope: EvmScope, swaps, transfers, more} (the moves are in `recent`). freshness: the layer as /api/status gives it {state, head, headTime, lagMs, chainHead?, blocksBehind?, behindMs?, clock?} |
elysium | object | {balances:[{token, symbol, name, decimals, amount, priceUsd, usd, spam, spamReason, testnet}], count, totalUsd, includeSpam, spamHidden, testnet, nfts, activity, freshness, bridges:[evm_elysium rows]} (same nfts / activity / freshness as hyperevm) |
bridges | object | The legs linking the layers over 7 days: {window: 7d, legs:{core_evm, evm_elysium}, inFlight:[{route, direction, status, detail?, token, amount, amountRaw?, t, ageMs, tx}] (core_evm initiated / stuck, evm_elysium sent / claimable), journeys:[{journey: core_to_elysium | elysium_to_core, link: same_tx | unique | ordered, status: complete | failed | stuck | in_flight, token (HyperEVM address, 0x2222…2222 = HYPE), amountRaw, startTime, endTime, evmMs, totalMs, hop1, hop2}]}: a journey = a hop into HyperEVM then a hop out of it of the same asset and amount by the same HyperEVM account within the hour (rules of the bridge_journeys view) |
recent[] | object | 50 latest events of the three layers, newest first: {layer, kind, t, data} |
labels.<key> | object | {address: name} of known addresses in the answer (bridge system senders, contracts) (Elysium, HyperCore) |
billing | heavy | heavy |
Related: Bridges & wallets
- Wallet stream WS wallet Elysium, HyperCore, HyperEVM
Every event of the three layers touching one address. - 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
- This page as Markdown
- The whole API reference
- What Elysium serves
- What HyperCore serves
- What HyperEVM serves
- The whole API in one Markdown file
- OpenAPI 3.1 document
Agent guide (agents.md)llms.txtOpenAPIMCP serverGet an API keyChangelog