# Crypto ETF Flow Tracker — BTC ETH Spot ETF Daily Net Inflows A business tool your agent can run on one prepaid apifare key. Page: https://apifare.com/tools/gochujang/crypto-etf-flow-tracker ## What you need An apifare key with credits (sign up: POST https://apifare.com/v1/signup {"email": "..."}; new accounts get 500 free credits). No other account or key. ## Inputs - `etfTypes` (array): ETF Types (e.g. ["us-btc-spot","us-eth-spot"]) - `daysBack` (integer): Days Back (e.g. 30) - `lookbackDays` (integer): Lookback (days) [deprecated — use daysBack] (e.g. 30) - `sortBy` (string): Sort By (e.g. "date_desc") - `alertOutflowUsd` (integer): Telegram Alert: Daily Outflow Threshold (USD) - `alertInflowUsd` (integer): Telegram Alert: Daily Inflow Threshold (USD) The most relevant fields; the search result's input_schema lists all of them. ## Price 5 credits reserved per run, settled to the run's true cost, never more than 20 credits (1 credit = $0.01). Failed runs are refunded. Exact numbers: https://apifare.com/capabilities ## Run it 1. Find it: MCP search_apis, or GET https://apifare.com/v1/search?q=Crypto%20ETF%20Flow%20Tracker%20%E2%80%94%20BTC%20ETH%20Spot%20ETF%20Daily%20Net%20Inflows with Authorization: Bearer . Take the result named "Crypto ETF Flow Tracker — BTC ETH Spot ETF Daily Net Inflows"; it carries a proxy_route. 2. Run it: MCP proxy_call with that proxy_route and the input JSON (apifare-mcp over stdio), or POST the proxy_route over HTTP with the input JSON as the body and the same Authorization header. 3. On HTTP 402, relay the body's human_readable field to your human verbatim, wait, then retry the same call. Every other error and its fix: https://apifare.com/errors.md