API reference · Chain & reference
OpenAPI document
The OpenAPI 3.1 contract of every REST call, public.
GET https://api.femtos.xyz/v1/openapi.json
Example
Elysium, HyperCore, HyperEVM
curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/openapi.json"Key: Authorization: Bearer $FEMTOS_KEY. Get a free key, or with no browser through agent onboarding.
Response fields
| Field | Type | Meaning |
|---|---|---|
paths | object | every operation |
components.schemas | object | response shapes |
x-websocket.channels | object[] | WebSocket channels |
Related: Chain & reference
- 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. - Stream stats WS stats HyperCore
Our HyperCore stream health, once a second. - 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.
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