Crypto Funding Rates Tracker - Binance & Hyperliquid

Crypto Funding Rates Tracker: Binance & Hyperliquid

Collect perpetual futures funding rates for Binance USD-M and Hyperliquid perps: the latest rate, settlement time, mark price, funding cadence and annualized funding per symbol. Each run returns one record per symbol and venue, with a shared coin field to compare venues side by side. Built for traders, quant hobbyists and bot builders who schedule runs and pipe the JSON into dashboards, alerts or models. No account or API key is needed.

Data only, not financial advice.

Use cases

• Funding dashboards: a live board of the top perps by turnover, refreshed every hour.
• Cross-venue comparison: join Binance and Hyperliquid rows on coin to spot funding gaps for basis and arbitrage research.
• Crowding alerts: get a Telegram message when a symbol's funding (positive or negative) passes your threshold.
• Model features: store snapshots and use funding and annualized funding as positioning inputs in your own backtests.

Quick start

1. Open the Actor and click Start. The form is prefilled with Binance and the top 20 perps by 24-hour turnover.
2. Read the rows in the Output tab, or export them as JSON, CSV or Excel.

For a fixed watchlist on both venues:

{"symbols": ["BTC", "ETH", "SOL", "HYPE"], "venue": "both"}

An empty input ({}) runs the same defaults as the prefilled form: the top 20 Binance perps by 24-hour turnover.

Input

Name	Type	Default	Meaning
symbols	array	[]	Optional watchlist of up to 100 entries, case-insensitive ("BTC", "btc", "BTCUSDT" all work). Empty tracks the top perps by 24h turnover.
topSymbols	integer	20	Board size per venue when no watchlist is given (5–100).
venue	string	binance	binance, hyperliquid or both.
alertAbsFundingPct	number	0	When above 0 (up to 100), each symbol whose funding magnitude reaches this percent per period sends one Telegram alert per run. The threshold is symmetric, so deeply negative funding counts too. 0 turns alerts off.
telegramBotToken	string	empty	Secret Telegram bot token for alerts; the TELEGRAM_BOT_TOKEN secret environment variable also works.
telegramChatId	string	empty	Chat that receives the alerts.
requestDelaySecs	number	0.15	Pause between symbols (0–10 seconds).

A misspelt input field stops the run with an error that names it.

What it returns

One dataset row per symbol and venue:

Field	Meaning
recordKey	Stable key, funding:{venue}:{symbol}.
source, kind	Record source and type.
venue, symbol	Venue and its symbol for the perp.
coin	Base coin, the join key across venues.
fundingRate, fundingRatePct	Latest funding rate, as a fraction and in percent.
fundingTime	Time of the latest funding settlement.
fundingIntervalHours	Funding cadence in hours (8, 4 or 1).
fundingIntervalBasis	How the cadence is known: event-spacing (observed), venue-default or stale-spacing.
fundingHistoryStale	true when recent settlements are too old to confirm the cadence.
annualizedFundingPct	Annualized funding in percent; null unless the cadence is observed.
markPrice	Mark price at the latest settlement.
rateType	Venue rate type label where provided, otherwise null.
quoteVolume24h	24-hour quote turnover used for ranking.
sourceUrl	Link to the perp's trading page.
collectedAt	UTC time the snapshot was taken.

The run summary (OUTPUT) reports coverage counters, the alert result and warnings such as unmatched watchlist entries. records counts only the rows stored in the dataset; if your maximum charge per run stops the run early, stoppedBy is chargeLimit and the status message says how many funding records were stored.

Output example

A real record from a run with the Quick Start input:

{"recordKey":"funding:binance:BTCUSDT","source":"binance-fapi","kind":"funding_rate","venue":"binance","symbol":"BTCUSDT","coin":"BTC","fundingRate":6.542e-05,"fundingRatePct":0.006542,"fundingTime":"2026-10-21T00:00:00+00:00","fundingIntervalHours":8,"fundingIntervalBasis":"event-spacing","fundingHistoryStale":false,"annualizedFundingPct":7.1635,"markPrice":82984.7,"rateType":"Regular","quoteVolume24h":10412086707.75,"sourceUrl":"https://www.binance.com/en/futures/BTCUSDT","collectedAt":"2026-10-21T06:06:59.241744+00:00"}

Pricing

• $0.0025 per result row (one symbol on one venue).
• $0.005 per run start. The run-start event is charged per GB of memory; the default 512 MB run is one start event. The start is charged even if the run saves no rows.

You pay only for rows actually saved to the dataset; if fetching or validation fails, no rows are saved and none are charged. Platform usage is included in these prices.

Worked cost: the default run (top 20 Binance perps) is $0.005 + 20 × $0.0025 = $0.055. The same board on both venues (40 rows) is $0.105. A 4-symbol watchlist on both venues (8 rows) is $0.025.

Scheduling and monitoring

• Schedule a run every hour (Hyperliquid settles hourly) or every 4–8 hours for Binance-only boards. recordKey is stable per venue and symbol; key your own history on recordKey plus fundingTime.
• For alert-only use, set alertAbsFundingPct (for example 0.05) with telegramChatId and the bot token. A failed or skipped send is a warning in OUTPUT, never a failed run.

FAQ

How is annualized funding computed? From each symbol's own observed settlement cadence (8h, 4h or 1h). When the cadence cannot be confirmed from recent settlements, fundingIntervalBasis says so (venue-default or stale-spacing) and annualizedFundingPct stays null rather than guessing. The raw rate is always included.

Which venues are supported? Binance USD-M perpetuals and Hyperliquid perps. Set venue: "both" and join records across venues on coin.

How many symbols can I track? Up to 100 watchlist entries, or the top 20 (configurable up to 100) per venue by turnover.

What happens if a symbol has no funding history? It is named in the run warnings; the rest of the run continues.

How fresh is the data? Each run reads the latest settled funding rate and mark price at run time; nothing is cached between runs. The rate is the last settled one, not a predicted next rate.

Export formats? JSON, CSV, Excel, XML or RSS from the dataset, or read it through the Apify API in your own pipeline.

Limits

• Binance USD-M and Hyperliquid perps only.
• One snapshot per run; the Actor doesn't return funding history.
• Up to 100 watchlist entries, or up to 100 top perps per venue.

For support, contact Apify support and include the Actor run ID.