MARKETS & FINANCE
Crypto Funding Rates Tracker - Binance & Hyperliquid
Perpetual funding-rate board across Binance and Hyperliquid for a symbol watchlist or the top perps by 24h turnover: rate, timestamp, mark price and annualized funding per symbol.
About this data
Perpetual funding-rate board across Binance and Hyperliquid for a symbol watchlist or the top perps by 24h turnover: rate, timestamp, mark price and annualized funding per symbol. Optional Telegram alert when funding crosses your threshold. No API keys needed. Live snapshot per run.
From the actor’s Apify Store listing. The per-call endpoint may return a bounded subset; its own description is below.
Buy per call over x402
One endpoint at api.ssh.autos. Each call is one JSON POST, paid in USDC with no account or API key, and answered in the same HTTP response.
POST /v1/crypto/funding-rates
Snapshot of one venue: funding rate and percentage, funding timestamp, mark price, observed payment interval and cadence-based annualized percentage where computable.
Choose Binance or Hyperliquid and up to three symbols, or three leading symbols by turnover.
Alerts, Telegram and stored state are excluded.
Input
Send a JSON body to POST https://api.ssh.autos/v1/crypto/funding-rates.
| Field | Type | Required | Notes |
|---|---|---|---|
venue | string | optional | one of binance, hyperliquid; default "binance" |
symbols | array of strings | optional | up to 3 items |
Returned fields
The answer is JSON: records, a list, and summary, the run status and counts. Each record has these 18 fields; a field the source does not publish comes back null.
18 fields per record
| Field | Type | Notes |
|---|---|---|
recordKey | string | — |
source | string | one of binance-fapi, hyperliquid-info |
kind | string | always funding_rate |
venue | string | one of binance, hyperliquid |
symbol | string | Venue-native symbol: BTCUSDT on Binance, BTC on Hyperliquid. |
coin | string | Base asset — the cross-venue join key (BTCUSDT → BTC). |
fundingRate | number | Latest settled funding rate as a decimal (0.0001 = 0.01% per period). Positive = longs pay shorts. |
fundingRatePct | number | fundingRate × 100 (percent per funding period). |
fundingTime | string | Settlement timestamp of the latest funding event (ISO). |
fundingIntervalHours | number | Funding cadence in hours: the symbol's own observed event spacing when the history supports one, otherwise the venue's dominant cadence as a labeled estimate (see fundingIntervalBasis; Binance mixes… |
fundingIntervalBasis | string | Evidence basis of fundingIntervalHours (issues #118/#131): event-spacing = derived from this symbol's own settled events at a currently observed cadence, which takes two adjacent, equal/plausibly-equ… one of event-spacing, stale-spacing, venue-default |
fundingHistoryStale | boolean | True when the latest settled event is older than two cadence periods (+ slack): settlements were missed, so spacing-derived cadence claims are downgraded and annualizedFundingPct is withheld. |
annualizedFundingPct | number | fundingRate × (24 / fundingIntervalHours) × 365 × 100 — emitted ONLY at a currently observed cadence proven by consecutive evidence, two adjacent equal latest gaps (fundingIntervalBasis = event-spaci… |
markPrice | number | Binance: the mark at funding time (from the funding row). Hyperliquid: the live markPx from the same run's metaAndAssetCtxs sweep (documented nuance: a live mark, not the mark at funding time). |
rateType | string | Binance rateType passthrough (e.g. Regular); null on Hyperliquid. |
quoteVolume24h | number | 24h quote turnover (USDT on Binance, USD on Hyperliquid) — the board's ranking key. |
sourceUrl | string | — |
collectedAt | string | — |
Example call
npx agentcash@latest fetch https://api.ssh.autos/v1/crypto/funding-rates -m POST -b '{"venue": "binance", "symbols": ["BTC", "ETH"]}'The example values come from the API spec or the actor’s own sample input. Running it is a paid call.
What is and isn’t charged
You pay the call price for
- An answer, including a definitive “not found” or an empty result.
- Confirmed no matches returns records: [] (charged: it is an answer).
Free
- Invalid input (422), busy (503), source failure (502), timeout (504) and calls whose client hung up are never charged.
- Invalid input and source failures are not charged.
Prefer a subscription? Run it on Apify
This data source is a public actor on the Apify Store: Crypto Funding Rates Tracker - Binance & Hyperliquid. Run it with your Apify account and plan for larger, scheduled or exported runs; it may offer more input options than the per-call endpoint.
How x402 payment works
- Your client sends the request. The API answers
402 Payment Requiredwith the price and where to pay. - The client pays from its own wallet: USDC on Base or Solana over x402, or over MPP on Tempo. No account, sign-up or API key.
- The client retries with the payment attached and gets the JSON answer in the same call. You are only charged for answers.
The AgentCash CLI in the example does all three steps for you and pays from your AgentCash wallet. Any x402 or MPP client works the same way.
Recipes that use this
-
A morning market brief, written by your agent
Five calls, five market signals, one short briefing waiting when you wake up: sentiment, ETF flows, funding, rates and token unlocks.
Machine-readable: openapi.json · llms.txt