HyperEVM · 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

Param	In	Example or values
`address`	path	`<owner>`
`includeSpam`	query	`(empty)`, `true`

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

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

Field	Type	Meaning
`hyperevm.balances[]`	object	{token, symbol, amount, priceUsd, usd, spam, spamReason, family?} at the indexed head
`includeSpam · spamHidden`	query · int	spam tokens out of lists and USD totals unless includeSpam=true
`hyperevm.height · asOf`	int	indexed head block and time
`hyperevm.nfts`	object	{erc721, erc1155, collections[], tokens[]} held
`hyperevm.activity`	object	{scope, swaps, transfers}: its moves are in recent[]
`hyperevm.freshness`	object	head, lagMs, blocksBehind, behindMs (as /api/status)
`hyperevm.bridges[] · bridges`	object	HyperCore ↔ HyperEVM transfers; legs in flight, journeys
`hypercore · elysium`	object	the same address on the other layers

Bridge transfers GET /v1/bridges
HyperCore ↔ HyperEVM transfers (core_evm) or HyperEVM ↔ Elysium movements (evm_elysium), 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.