rank_funding_carry
chainpeek: Rank cross-venue perpetual funding carry. For Hyperliquid against dYdX alone use compare_funding_rates; for market data use get_perp_markets. Returns the best long and short venue pair per asset across Binance USDT-M, Bybit, OKX, Hyperliquid and dYdX v4, with the annualised funding spr...
This record as markdown: /tools/dev-tanod-tanod/rank-funding-carry.md
What rank_funding_carry does on Tanod
AI agents call rank_funding_carry to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Rows returned, 1-100 (default 20). |
venues | object | — | Optional subset of hyperliquid, dydx, binance, bybit, okx (at least two). Default: all five. |
symbols | object | — | Optional: only these base assets (case-insensitive, at most 50), such as BTC. Names listed on fewer than two of the chosen venues are returned in symbols_not_fo |
holding_days | number | — | Days the position is held; the fees are amortised over it (default 7). |
taker_fee_bps | number | — | Taker fee per side in basis points (default 0). Net APR subtracts 4 taker legs (open and close on both venues): 4 x bps / 100 x 365 / holding_days. |
min_volume_usd | number | — | A venue is only used for a symbol when its 24 h volume there reaches this (USD), so it applies to both legs. Default 0. |
Parameters from the server's own tool schema.
Why rank_funding_carry is rated Low
Even though rank_funding_carry only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs rank_funding_carry safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rank_funding_carry, this is the rule to start with:
rank_funding_carry is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every rank_funding_carry call is checked against it from then on.
Questions about rank_funding_carry
chainpeek: Rank cross-venue perpetual funding carry. For Hyperliquid against dYdX alone use compare_funding_rates; for market data use get_perp_markets. Returns the best long and short venue pair per asset across Binance USDT-M, Bybit, OKX, Hyperliquid and dYdX v4, with the annualised funding spread gross and net of taker fees. Net subtracts four taker legs (open and close on both venues) at taker_fee_bps, spread over holding_days; with the default 0 bps net equals gross. Rates are normalised to hourly and annualised (simple); a venue that is down is listed in venues_failed. Cached up to 60 s. Data only, not trading advice. Bad input is a 422 (not charged). Typically 1-5 s. Price: USD 0.005. Free: 10 chain reads per IP per UTC day. Docs: https://tanod.dev/learn/funding-rate-arbitrage-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
rank_funding_carry accepts 6 parameters: limit, venues, symbols, holding_days, taker_fee_bps, min_volume_usd. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for rank_funding_carry: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Tanod. Nothing to install.
rank_funding_carry is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the rank_funding_carry rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for rank_funding_carry. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
rank_funding_carry is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
This server
Across the catalogue