Review crypto ETF flow history for a supported asset. Returns ETF flow time points with recorded USD flows, asset prices, settlement status and available ETF breakdowns. 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 ETF flow history
Review crypto ETF flow history for a supported asset. Returns ETF flow time points with recorded USD flows, asset prices, settlement status and available ETF breakdowns. 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 ETF flow time points with recorded USD flows, asset prices, settlement status and available ETF breakdowns. Use the settlement flag and timestamps to distinguish provisional observations from settled records. Coverage follows supported assets.
Start with your task
Ask about money moving into or out of crypto ETFs (funds traded on a stock exchange) for [Bitcoin, Ethereum, XRP, Solana, or Hyperliquid]. Add [a date range, such as January 1 to March 31, 2026] if you want; I’ll handle the coin name and dates.
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 or date string (YYYY-MM-DD). Example: 2026-03-01.
Minimum length
1
fromqueryParams.from
string
Optional
Start of time range. Accepts Unix seconds or date string (YYYY-MM-DD). Example: 2026-01-01.
Minimum length
1
orderqueryParams.order
string
Optional
Sort order. Example: desc. Defaults to "desc".
Default
desc
Options
asc, desc
symbolqueryParams.symbol
string
Required
Token symbol. Can be BTC, ETH, XRP, SOL, or HYPE. Example: BTC.
Options
BTC, ETH, XRP, SOL, HYPE
sort_byqueryParams.sort_by
string
Optional
Field to sort results by. Example: timestamp. Defaults to "timestamp".
Review crypto ETF flow history for a supported asset
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 or date string (YYYY-MM-DD). Example: 2026-03-01.
queryParams.from (Optional): Start of time range. Accepts Unix seconds or date string (YYYY-MM-DD). Example: 2026-01-01.
queryParams.order (Optional): Sort order. Example: desc. Defaults to "desc".
queryParams.symbol (Required): Token symbol. Can be BTC, ETH, XRP, SOL, or HYPE. Example: BTC.
queryParams.sort_by (Optional): Field to sort results by. Example: timestamp. Defaults to "timestamp".
What this Tool returns
Returns ETF flow time points with recorded USD flows, asset prices, settlement status and available ETF breakdowns.
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.[].etfs
array | null; Optional within parent
Flow breakdown by individual ETF ticker
data.[].etfs.[].flow_usd
number; Required within parent; format: double
Daily net flow in USD for this ticker
data.[].etfs.[].ticker
string; Required within parent
ETF ticker symbol like `IBIT`, `GBTC`, or `ETHA`
data.[].flow_usd
number; Required within parent; format: double
Daily net flow in USD (positive=inflow, negative=outflow)
data.[].price_usd
number; Required within parent; format: double
Token price in USD at close of day
data.[].project_id
string; Optional within parent
Surf project UUID of the underlying, for frontend entity linking. Empty when unmapped.
data.[].settled
boolean; Required within parent
Whether this trading day is final. Current-day rows may still be pending upstream settlement.
data.[].symbol
string; Optional within parent
Underlying token symbol like `BTC`, `ETH`, `XRP`, `SOL`, or `HYPE`
data.[].timestamp
integer; Required within parent; format: int64
Unix timestamp in seconds (midnight UTC for the trading day)
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
Use the settlement flag and timestamps to distinguish provisional observations from settled records. Coverage follows supported assets.
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.
Bitcoin fund flows
Example request: [Show how much money moved into or out of Bitcoin ETFs from January 1 to March 31, 2026].
Example request: [How much money moved into or out of Ethereum ETFs during January 2026?].
Ask about money moving into or out of crypto ETFs (funds traded on a stock exchange) for [Bitcoin, Ethereum, XRP, Solana, or Hyperliquid]. Add [a date range, such as January 1 to March 31, 2026] if you want; I’ll handle the coin name and dates.
XRP fund flows
Example request: [Show XRP ETF flows from January through June 2026].
Questions about this tool.
Inputs, results and details to know before running it.
queryParams.to (Optional): End of time range. Accepts Unix seconds or date string (YYYY-MM-DD). Example: 2026-03-01. queryParams.from (Optional): Start of time range. Accepts Unix seconds or date string (YYYY-MM-DD). Example: 2026-01-01. queryParams.order (Optional): Sort order. Example: desc. Defaults to "desc". queryParams.symbol (Required): Token symbol. Can be BTC, ETH, XRP, SOL, or HYPE. Example: BTC. queryParams.sort_by (Optional): Field to sort results by. Example: timestamp. Defaults to "timestamp".
Returns ETF flow time points with recorded USD flows, asset prices, settlement status and available ETF breakdowns.
Use the settlement flag and timestamps to distinguish provisional observations from settled records. Coverage follows supported assets.
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 crypto ETF flow history for a supported asset. 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.
