Review liquidation totals across historical time buckets. Returns historical long and short liquidation USD totals, with contributing and excluded exchange context. 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.0144 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.0144 credits / call
The final charge is based on confirmed usage. Unused reserved credits return to your available balance.
Surf
Crypto Liquidation History Chart by Token | Surf
Review liquidation totals across historical time buckets. Returns historical long and short liquidation USD totals, with contributing and excluded exchange context. 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.0144 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 and short liquidation USD totals, with contributing and excluded exchange context. Keep excluded exchanges visible; a bucket's total is not necessarily a complete worldwide liquidation total.
Start with your task
Show the dollar value of [Bitcoin] trades automatically closed on [Binance] from [October 1–7, 2026], grouped by [hourly]. Explain whether positions expected prices to rise or fall and name any exchanges left out; totals may not cover every exchange.
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
symbol
toqueryParams.to
string
Optional
End of time range. Accepts Unix seconds (1706745600) or date string (2024-02-01). Example: 2024-02-01.
Minimum length
1
fromqueryParams.from
string
Optional
Start of time range. Accepts Unix seconds (1704067200) or date string (2024-01-01). Example: 2024-01-01.
Minimum length
1
limitqueryParams.limit
integer
Optional
Results per page. Example: 500. Defaults to 500.
Default
500
Minimum
1
Maximum
4500
symbolqueryParams.symbol
string
Required
Token ticker symbol like BTC or ETH. Example: BTC.
Minimum length
1
exchangequeryParams.exchange
string
Optional
Exchange name. Can be Binance, OKX, Bybit, Bitget, Hyperliquid, Gate, HTX, Bitmex, Bitfinex, CoinEx, Aster, or Lighter. Example: Binance. Defaults to "Binance".
Candlestick interval — bucket size for each point in the liquidation chart series: 1m, 3m, 5m, 15m, 30m, 1h, 4h, 6h, 8h, 12h, 1d, or 1w. This endpoint uses interval only; it does NOT accept time_range. Use from/to to bound the series. Example: 1h. Defaults to "1h".
Default
1h
Options
1m, 3m, 5m, 15m, 30m, 1h, 4h, 6h, 8h, 12h, 1d, 1w
View raw JSON
{
"type": "object",
"required": [
"queryParams"
],
"properties": {
"queryParams": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"symbol"
],
"~standard": {
"vendor": "zod",
"version": 1,
"jsonSchema": {}
},
"properties": {
"to": {
"type": "string",
"minLength": 1,
"description": "End of time range. Accepts Unix seconds (1706745600) or date string (2024-02-01). Example: 2024-02-01."
},
"from": {
"type": "string",
"minLength": 1,
"description": "Start of time range. Accepts Unix seconds (1704067200) or date string (2024-01-01). Example: 2024-01-01."
},
"limit": {
"type": "integer",
"default": 500,
"maximum": 4500,
"minimum": 1,
"description": "Results per page. Example: 500. Defaults to 500."
},
"symbol": {
"type": "string",
"minLength": 1,
"description": "Token ticker symbol like BTC or ETH. Example: BTC."
},
"exchange": {
"enum": [
"Binance",
"OKX",
"Bybit",
"Bitget",
"Hyperliquid",
"Gate",
"HTX",
"Bitmex",
"Bitfinex",
"CoinEx",
"Aster",
"Lighter"
],
"type": "string",
"default": "Binance",
"description": "Exchange name. Can be Binance, OKX, Bybit, Bitget, Hyperliquid, Gate, HTX, Bitmex, Bitfinex, CoinEx, Aster, or Lighter. Example: Binance. Defaults to \"Binance\"."
},
"interval": {
"enum": [
"1m",
"3m",
"5m",
"15m",
"30m",
"1h",
"4h",
"6h",
"8h",
"12h",
"1d",
"1w"
],
"type": "string",
"default": "1h",
"description": "Candlestick interval — bucket size for each point in the liquidation chart series: 1m, 3m, 5m, 15m, 30m, 1h, 4h, 6h, 8h, 12h, 1d, or 1w. This endpoint uses interval only; it does NOT accept time_range. Use from/to to bound the series. Example: 1h. Defaults to \"1h\"."
}
},
"additionalProperties": false
}
},
"additionalProperties": false
}
Result schema
Output fields have not been documented yet.
Additional notes
Review liquidation totals across historical time buckets
How to use this Tool
Use the deployed input fields below. Required fields must be supplied; optional filters narrow the result.
queryParams.to (Optional): End of time range. Accepts Unix seconds (1706745600) or date string (2024-02-01). Example: 2024-02-01.
queryParams.from (Optional): Start of time range. Accepts Unix seconds (1704067200) or date string (2024-01-01). Example: 2024-01-01.
queryParams.limit (Optional): Results per page. Example: 500. Defaults to 500.
queryParams.symbol (Required): Token ticker symbol like BTC or ETH. Example: BTC.
queryParams.exchange (Optional): Exchange name. Can be Binance, OKX, Bybit, Bitget, Hyperliquid, Gate, HTX, Bitmex, Bitfinex, CoinEx, Aster, or Lighter. Example: Binance. Defaults to "Binance".
queryParams.interval (Optional): Candlestick interval — bucket size for each point in the liquidation chart series: 1m, 3m, 5m, 15m, 30m, 1h, 4h, 6h, 8h, 12h, 1d, or 1w. This endpoint uses interval only; it does NOT accept time_range. Use from/to to bound the series. Example: 1h. Defaults to "1h".
What this Tool returns
Returns historical long and short liquidation USD totals, with contributing and excluded exchange context.
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.[].contributing_exchanges
array | null; Optional within parent
Exchanges that contributed to this liquidation point
data.[].excluded_exchanges
array | null; Optional within parent
Requested exchanges omitted because liquidation data is unavailable
data.[].long_liquidation_usd
number; Required within parent; format: double
Long-side aggregated liquidation volume (USD)
data.[].short_liquidation_usd
number; Required within parent; format: double
Short-side aggregated liquidation volume (USD)
data.[].timestamp
integer; Required within parent; format: int64
Unix timestamp in seconds
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 excluded exchanges visible; a bucket's total is not necessarily a complete worldwide liquidation total.
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.0144 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.
Use a familiar coin and exchange
Example request: Show [Bitcoin] trade values automatically closed on [Binance] from [October 1, 2026] to [October 7, 2026], grouped by [hourly]. Name any exchanges left out.
Example request: For [Ethereum] on [Bybit], show automatically closed trade totals from [October 1, 2026] to [October 7, 2026], grouped by [daily points]. Explain whether the positions expected prices to rise or fall.
Show the dollar value of [Bitcoin] trades automatically closed on [Binance] from [October 1–7, 2026], grouped by [hourly]. Explain whether positions expected prices to rise or fall and name any exchanges left out; totals may not cover every exchange.
Review a longer period
Example request: Show [Solana] trade values automatically closed on [OKX] from [September 1, 2026] to [October 1, 2026], grouped by [weekly points]. Note that the totals may not cover every exchange.
Questions about this tool.
Inputs, results and details to know before running it.
queryParams.to (Optional): End of time range. Accepts Unix seconds (1706745600) or date string (2024-02-01). Example: 2024-02-01. queryParams.from (Optional): Start of time range. Accepts Unix seconds (1704067200) or date string (2024-01-01). Example: 2024-01-01. queryParams.limit (Optional): Results per page. Example: 500. Defaults to 500. queryParams.symbol (Required): Token ticker symbol like BTC or ETH. Example: BTC. queryParams.exchange (Optional): Exchange name. Can be Binance, OKX, Bybit, Bitget, Hyperliquid, Gate, HTX, Bitmex, Bitfinex, CoinEx, Aster, or Lighter. Example: Binance. Defaults to "Binance". queryParams.interval (Optional): Candlestick interval — bucket size for each point in the liquidation chart series: 1m, 3m, 5m, 15m, 30m, 1h, 4h, 6h, 8h, 12h, 1d, or 1w. This endpoint uses interval only; it does NOT accept time_range. Use from/to to bound the series. Example: 1h. Defaults to "1h".
Returns historical long and short liquidation USD totals, with contributing and excluded exchange context.
Keep excluded exchanges visible; a bucket's total is not necessarily a complete worldwide liquidation total.
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.0144 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 liquidation totals across historical time buckets. 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.
