API reference · Chain & reference

Stream stats

Our HyperCore stream health, once a second.

Not on Elysium or HyperEVM: a stream of our HyperCore node: the EVM layers have their own channels (trades, candles, blocks)

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

{"op":"subscribe","channel":"stats","filter":{}}

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

Response fields

Field	Type	Meaning
`data`	StreamStats	HyperCore stream health, once a second: {msgsPerSec, p50, p99, height, books, clients}

Freshness GET /v1/status Elysium, HyperCore, HyperEVM
Head and lag of each layer, measured now.
Blocks stream WS elysium.blocks · hyperevm.blocks Elysium, HyperEVM
Each new HyperEVM block header, small and big blocks, from our node.
Transaction GET /v1/tx/{hash} Elysium, HyperEVM
One transaction: status, gas, decoded transfers, swaps and liquidity, bridge legs and journey.
Elysium RPC POST /v1/elysium/rpc Elysium
Free public Elysium mainnet RPC by Femtos (chain 99901), no key, read only (no transaction sending), for wallets and dapps, not for indexing (use the Femtos API for history): per IP 5 requests a second and 60 a minute, batches of 5, eth_getLogs over 1,000 blocks at most, state of the last 128 blocks only.
Check your key GET /v1/whoami Elysium, HyperCore, HyperEVM
Answers the name your key is registered under, its tier, billing state and the limits in force.
OpenAPI document GET /v1/openapi.json Elysium, HyperCore, HyperEVM
The OpenAPI 3.1 contract of every REST call, public.