Crypto Funding Rates 💹

foXLabs crypto series: Token unlocks · DeFi volume & fees · Stablecoins · Hacks database

🎉 Turn perp funding into clean, structured data — no login, no API key, one row per market, with the token, exchange, funding rate and interval. Built for crypto traders and quant research.

🔍 What is the Crypto Funding Rates — and when should you use it?

Give this actor token symbols or exchanges and it returns matching markets from public perpetual-futures funding-rate data — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live.

Use it when you need: current funding rates for a token; cross-exchange funding spreads; or a funding-rate table.

Use something else when: you need spot price or order books — this is funding rates, not full market data.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/crypto-funding-rates.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull funding rate company records using the Apify Actor `foxlabs/crypto-funding-rates`.
Input: `mode`, `coin`, `exchange`, `contractType` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"mode":"tickers","maxResults":500}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/crypto-funding-rates.md.

📋 Overview

Everything you need to turn public perpetual-futures funding-rate data into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole feed, one call — name or ID in, matching markets out.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable identifiers — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
• 💰 Per-row pricing — a minimal price per delivered row, no subscription.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Name or ID lookup — relevance-ranked name search or exact registry-ID lookup.
• 🏢 Full entity profile — status, legal form, formation date, address and the registry’s own contact fields.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~crypto-funding-rates/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"tickers","maxResults":500}'

🚀 Getting Started (3 steps)

1. Choose your targets — token symbols or exchanges.
2. Set the cap — maxResults limits how many results are returned.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"mode":"tickers","maxResults":500}

Field	Type	Description
mode	string	"Tickers" = one row per market (funding rate, OI, volume). "Funding comparison" = one row per coin showing the cross-exchange funding-rate spread (highest vs…
coin	string	Filter to one coin by its index symbol (e.g. "BTC", "ETH", "SOL"). Leave empty for all.
exchange	string	Keep only markets whose exchange name contains this (e.g. "Binance", "Bybit", "OKX"). Leave empty for all.
contractType	string	Filter by contract type.
minOpenInterest	integer	Drop illiquid markets below this open interest. Defaults to 1,000,000 to filter out junk/low-liquidity exchanges — set to 0 to include everything.
minVolume24h	integer	Only include markets with at least this 24h volume. 0 = no filter.
maxAbsFundingRate	number	Drop markets whose absolute funding rate is above this — a sanity filter for broken/illiquid exchanges reporting nonsense rates. Default 1 (real rates cluster…
onlyMajorExchanges	boolean	Keep only well-known liquid venues (Binance, Bybit, OKX, Bitget, Gate, MEXC, Kraken, Deribit, Hyperliquid…). Defaults ON in spread mode (the comparison is only…
sortBy	string	How to rank rows in tickers mode.
maxResults	integer	Cap the number of rows returned.

📤 Output

One row per result, saved to the dataset. Every row carries scrapedAt. Lookups that cannot be completed are reported in the run log rather than silently dropped.

Field	Description
rank	Rank
market	Market
symbol	Symbol
indexId	Index Id
contractType	Contract Type
price	Price
priceChange24hPct	Price Change24h Pct
fundingRate	Funding Rate
fundingIntervalHours	Funding Interval Hours
fundingIntervalSource	Funding Interval Source
annualizedFundingRate	Annualized Funding Rate
openInterest	Open Interest
volume24h	Volume24h
basis	Basis
spread	Spread
source	Source
generatedAtIso	Generated At Iso

💼 Use cases

1. Funding arbitrage — find funding spreads across exchanges. Input: token symbols. Output: rates per exchange. Use: spot arb opportunities.

2. Sentiment signal — read funding as a positioning signal. Input: token symbols. Output: funding rates. Use: gauge long/short bias.

3. Monitoring — track a token’s funding over time. Input: symbols, scheduled. Output: rate history. Use: spot regime shifts.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/crypto-funding-rates').call({"mode":"tickers","maxResults":500});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/crypto-funding-rates').call(run_input={"mode":"tickers","maxResults":500})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads public perpetual-futures funding-rate data.

What do I search by? Token symbols or exchanges.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

What does each row cover? One perp market: token, exchange, current funding rate and interval.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — raise maxResults, or refine the input.
• A name returns an unexpected entity — it matched a similar registered name; search the exact registry ID.
• No rows for a name — try the entity’s exact legal name or its registry ID.

⚖️ Is it legal to scrape this data?

This actor reads public perpetual-futures funding-rate data. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.1.19 — 2026-09-20 — README examples corrected against the real input schema

• The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"mode":"tickers","maxResults":500}
• The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
• Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
• No code, output field or pricing change.

0.1 — 2026-09-07

• Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.0

• Initial release: data from public perpetual-futures funding-rate data by name or registry ID.