Inspect a perpetual contract's current funding and open interest. Returns funding-rate fields, settlement context and available open-interest values for one perpetual contract. Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0072 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
Up to 0.0072 credits / call
The final charge is based on confirmed usage. Unused reserved credits return to your available balance.
Surf
Perpetual Open Interest and Funding Rate Snapshot
Inspect a perpetual contract's current funding and open interest. Returns funding-rate fields, settlement context and available open-interest values for one perpetual contract. Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0072 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
You receive
Returns funding-rate fields, settlement context and available open-interest values for one perpetual contract. Keep raw and normalized funding rates distinct. Contract counts and USD open interest are separate measures; next settlement time is source-reported.
Start with your task
On [Binance], check whether holders of [Bitcoin] contracts priced in [Tether] are paying or receiving funding, and show the value of contracts traders still hold.
Inputs & outputs
Inspect the current inputs, availability, and maximum charge before starting.
Input schema
Input schema
Field / Path
Type
Requirement
Meaning
queryParamsqueryParams
object
Required
Required fields
pair
pairqueryParams.pair
string
Required
Trading pair (e.g. BTC/USDT). The swap settle suffix is added automatically from the quote currency, e.g. BTC/USDT:USDT or BTC/USDC:USDC. Example: BTC/USDT.
Minimum length
1
fieldsqueryParams.fields
string
Optional
Comma-separated fields to include: 'funding' (current funding rate), 'oi' (open interest). Defaults to all fields. Example: funding,oi. Defaults to "funding,oi".
Inspect a perpetual contract's current funding and open interest
How to use this Tool
Use the deployed input fields below. Required fields must be supplied; optional filters narrow the result.
queryParams.pair (Required): Trading pair (e.g. BTC/USDT). The swap settle suffix is added automatically from the quote currency, e.g. BTC/USDT:USDT or BTC/USDC:USDC. Example: BTC/USDT.
queryParams.fields (Optional): Comma-separated fields to include: 'funding' (current funding rate), 'oi' (open interest). Defaults to all fields. Example: funding,oi. Defaults to "funding,oi".
Returns funding-rate fields, settlement context and available open-interest values for one perpetual contract.
Response fields and how to read them
The table follows the official response contract, including nested fields and useful response metadata. [] denotes an array item. Required means required within its parent object, not that a conditional parent always exists. A nullable type permits null; an optional field can be absent. Use the documented conditions below to distinguish missing, empty and zero values. Units and reporting windows apply only where explicitly documented.
Field, type and presence
Meaning and conditions
data.exchange
string; Required within parent
Exchange identifier
data.funding
object; Required within parent
Current funding rate data; null when not requested
data.funding.exchange
string; Required within parent
Exchange identifier
data.funding.funding_interval_hours
integer | null; Required within parent; format: int64
Funding interval in hours when known
data.funding.funding_rate
number | null; Required within parent; format: double
Current raw funding rate for the exchange settlement interval (0.0001 = 0.01%). Use funding_rate_8h for cross-exchange comparison.
data.funding.funding_rate_1h
number; Optional within parent; format: double
Funding rate normalized to a 1-hour interval
data.funding.funding_rate_8h
number; Optional within parent; format: double
Funding rate normalized to an 8-hour interval for cross-exchange comparison
data.funding.funding_rate_annualized
number; Optional within parent; format: double
Simple annualized funding rate derived from the 1-hour normalized rate
data.funding.funding_rate_raw
number; Optional within parent; format: double
Alias of funding_rate: raw funding rate for the exchange settlement interval
data.funding.index_price
number | null; Required within parent; format: double
Index price derived from the weighted average of spot prices across multiple exchanges
data.funding.interval
string | null; Required within parent
Funding interval like 8h
data.funding.mark_price
number | null; Required within parent; format: double
Mark price calculated by the exchange from the index price and funding rate, used as the reference for liquidations
data.funding.next_funding
string | null; Required within parent
Next settlement time ISO8601
data.funding.pair
string; Required within parent
Perpetual contract pair like BTC/USDT
data.open_interest
object; Required within parent
Current open interest data; null when not requested
data.open_interest.exchange
string; Required within parent
Exchange identifier
data.open_interest.open_interest_amount
number | null; Required within parent; format: double
Open interest in contracts
data.open_interest.open_interest_usd
number | null; Required within parent; format: double
Open interest in USD
data.open_interest.pair
string; Required within parent
Trading pair like BTC/USDT
data.open_interest.timestamp
integer | null; Required within parent; format: int64
Unix timestamp in seconds
data.pair
string; Required within parent
Perpetual contract pair like BTC/USDT
meta.cached
boolean; Required within parent
Whether this response was served from cache
meta.credits_used
integer; Required within parent; format: int64
Credits deducted for this request
meta.empty_reason
string; Optional within parent
Hint explaining why the data array is empty, when applicable
Coverage, units and freshness
Keep raw and normalized funding rates distinct. Contract counts and USD open interest are separate measures; next settlement time is source-reported.
Inspect any returned observation time, cache status, watermark, pagination and errors using their documented meanings. A successful request alone does not establish complete coverage. Where no freshness or completeness guarantee is documented, treat it as unknown. Saved Examples are historical and viewing them does not refresh data or execute a new call.
Data source and references
Surf supplies this endpoint through its Data API. Response contract and deployed Tool inputs reviewed on 2026-10-03 against official OpenAPI v0.2.102. This is a contract review date, not a data observation time. Coverage depends on the selected endpoint and request.
Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0072 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
Check Bitcoin contract funding
Example request: On [Binance], tell me whether holders of [Bitcoin] contracts priced in [Tether] pay or receive funding, and how much value remains in open contracts.
Example request: Show the funding information and value of open [Ethereum] contracts priced in [Tether] on [OKX].
On [Binance], check whether holders of [Bitcoin] contracts priced in [Tether] are paying or receiving funding, and show the value of contracts traders still hold.
View Solana contract data
Example request: On [Bybit], show whether holders of [Solana] contracts priced in [Tether] pay or receive funding.
Questions about this tool.
Inputs, results and details to know before running it.
Name the coin and the currency used for its price, such as [Bitcoin] priced in [Tether]. You may name an exchange, such as [Binance]; otherwise [Binance] is used. This Tool checks one perpetual contract at a time. Funding is a recurring payment between people holding opposite sides of a contract; the result shows whether it is paid or received. It also shows how many contracts or how much value remains open, when available. This is one lookup, not a history. You do not need to enter a market code; if a coin or currency name is unclear, I will ask.
Returns funding-rate fields, settlement context and available open-interest values for one perpetual contract.
Keep raw and normalized funding rates distinct. Contract counts and USD open interest are separate measures; next settlement time is source-reported.
Use one Toolmu account and a shared prepaid balance across available Tools. Pay per use; no separate supplier subscription is required. The current execution ceiling for this Tool is 0.0072 Toolmu credits per call. This is a maximum, not the settled charge. Before execution, get the current Tool contract and check availability, the latest maximumCredits, your balance and budget. Supplier response credits_used, when present, describes supplier API credits and is not the Toolmu customer charge.
Ask your agent to Inspect a perpetual contract's current funding and open interest. Provide the required inputs above. If Toolmu is already connected, reuse that connection; otherwise use the setup instructions on this page. Before a paid execution, the agent must read the current Tool contract and check availability, the credit ceiling, balance, budget and your authorization. It should then execute the Tool and explain the returned fields and limitations.
Inspect any returned observation time, cache status, watermark, pagination and errors using their documented meanings. A successful request alone does not establish complete coverage. Where no freshness or completeness guarantee is documented, treat it as unknown. Saved Examples are historical and viewing them does not refresh data or execute a new call.
