API reference · Bridges & wallets
Bridge 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.
- Not on Elysium: covers the HyperCore <> HyperEVM legs; the HyperEVM <> Elysium ones are in GET /v1/bridges?route=evm_elysium, with no coverage report until the Elysium token registry runs (Kinetiq factories not deployed yet)
GET https://api.femtos.xyz/v1/bridges/coverage
Parameters
| Param | In | Example or values | Meaning |
|---|---|---|---|
window | query | all, 30d, 7d, 24h | Legs of the window (by sending time) |
Example
HyperCore, HyperEVM
curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/bridges/coverage?window=all"Key: Authorization: Bearer $FEMTOS_KEY. Get a free key, or with no browser through agent onboarding.
Response fields
| Field | Type | Meaning |
|---|---|---|
directions.evm_to_core | object | {legs, matched, coverage, unmatched, notALeg, finalPending, reverted, matchedBy, latencyMs, unpairedCredits, tokens} |
directions.core_to_evm | object | {legs, matched, coverage, unmatched, notALeg, finalPending, reverted, matchedBy, latencyMs, unpairedCredits, tokens} |
directions.evm_to_core.coverage | number | null | matched / (legs - notALeg - in_flight): 1 = every settled leg has its other leg |
directions.evm_to_core.unmatched | object | {<reason>: n}. in_flight: younger than the other layer read (2 min; 30 s for core_to_evm); missing_peer: no credit found; amount_mismatch: a credit of the same system address to the same account, another amount; late_peer (core_to_evm): an identical credit 10 s-10 min later, past the 10 s window; unknown_token: system address not in the token registry; unmatched: views source (no reason) |
directions.core_to_evm.matchedBy | object | core_to_evm: {nonce, order} |
directions.evm_to_core.unpairedCredits | object | null | {in_flight, missing_peer}: credits on the receiving side no leg took (null: views source) |
source | materialized | views | materialized: the tables bridge-match keeps (a reason per leg); views: the matching views read directly (every 10 min) |
settledUntil | int | null | materialized: every leg before this time was matched with both layers read past it (Unix ms) |
Related: Bridges & wallets
- Cross-layer wallet GET /v1/wallet/{address} Elysium, HyperCore, HyperEVM
One address (or a named wallet's handle) on HyperCore, HyperEVM and Elysium, plus its latest events. - 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.
More
- This page as Markdown
- The whole API reference
- 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