Review a trading pair's historical long and short position ratio. Returns historical long/short ratios with exchange, pair and time-point references. 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
Crypto long short ratio history · Surf
Review a trading pair's historical long and short position ratio. Returns historical long/short ratios with exchange, pair and time-point references. 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 historical long/short ratios with exchange, pair and time-point references. A ratio is not a percentage or a count of all traders. Interpret it within the source exchange's covered market.
Start with your task
Show how the market has leaned toward [Bitcoin] rising or falling on [Binance], using [Tether] prices every [4 hours] since [2026-09-01].
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
fromqueryParams.from
string
Optional
Start of time range. Accepts Unix seconds or date string (YYYY-MM-DD, ISO8601). Binance only retains the last 30 days of data; other exchanges may have different limits. Example: 2026-03-01.
Minimum length
1
pairqueryParams.pair
string
Required
Trading pair (e.g. BTC/USDT). Example: BTC/USDT.
Minimum length
1
limitqueryParams.limit
integer
Optional
Max number of records. For longer history, paginate using the last returned timestamp as the next from value. Example: 50. Defaults to 50.
Default
50
Minimum
1
Maximum
500
exchangequeryParams.exchange
string
Optional
Exchange identifier. Example: binance. Defaults to "binance".
Default
binance
Options
binance, okx, bybit, bitget
intervalqueryParams.interval
string
Optional
Bucket size for each point in the series: 1h, 4h, or 1d. This endpoint uses interval only; it does NOT accept time_range. Use from + limit to control the window. Example: 1h. Defaults to "1h".
Default
1h
Options
1h, 4h, 1d
View raw JSON
{
"type": "object",
"required": [
"queryParams"
],
"properties": {
"queryParams": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"pair"
],
"~standard": {
"vendor": "zod",
"version": 1,
"jsonSchema": {}
},
"properties": {
"from": {
"type": "string",
"minLength": 1,
"description": "Start of time range. Accepts Unix seconds or date string (YYYY-MM-DD, ISO8601). Binance only retains the last 30 days of data; other exchanges may have different limits. Example: 2026-03-01."
},
"pair": {
"type": "string",
"minLength": 1,
"description": "Trading pair (e.g. BTC/USDT). Example: BTC/USDT."
},
"limit": {
"type": "integer",
"default": 50,
"maximum": 500,
"minimum": 1,
"description": "Max number of records. For longer history, paginate using the last returned timestamp as the next from value. Example: 50. Defaults to 50."
},
"exchange": {
"enum": [
"binance",
"okx",
"bybit",
"bitget"
],
"type": "string",
"default": "binance",
"description": "Exchange identifier. Example: binance. Defaults to \"binance\"."
},
"interval": {
"enum": [
"1h",
"4h",
"1d"
],
"type": "string",
"default": "1h",
"description": "Bucket size for each point in the series: 1h, 4h, or 1d. This endpoint uses interval only; it does NOT accept time_range. Use from + limit to control the window. Example: 1h. Defaults to \"1h\"."
}
},
"additionalProperties": false
}
},
"additionalProperties": false
}
Result schema
Output fields have not been documented yet.
Hourly Bitcoin comparison
Example request: Show how the market on [Binance] leaned toward [Bitcoin] rising or falling, using [Tether] prices.
Tell me which coin you mean and which currency to use for its price, such as [Bitcoin] measured in [Tether]. [Binance] is used by default, or name [OKX], [Bybit] or [Bitget]. The history is shown once an hour by default; ask for [4-hour] or [daily] records to change this. You may also give a start date. [Binance] keeps only the latest [30 days] of history; other platforms may cover a different period.
Returns historical long/short ratios with exchange, pair and time-point references.
A ratio is not a percentage or a count of all traders. Interpret it within the source exchange's covered market.
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 Review a trading pair's historical long and short position ratio. 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.