# Institutional Crypto Flows — Bitcoin ETF Tracker (`gochujang/institutional-crypto-flows`) Actor

Track institutional Bitcoin flows from public data. Daily ETF inflows/outflows per fund (IBIT, FBTC, ARKB, BITB, BTCO, etc.), 7d/30d cumulative flows, flow trend, market signal, and net institutional sentiment. Fallback to corporate BTC treasury data. No API key required.

- **URL**: https://apify.com/gochujang/institutional-crypto-flows.md
- **Developed by:** [Hojun Lee](https://apify.com/gochujang) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 actor starts

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Institutional Crypto Flows — Bitcoin ETF & Corporate Treasury Tracker

**Institutional Crypto Flows** tracks **daily Bitcoin ETF flows** for all US spot ETFs (IBIT, FBTC, BITB, ARKB, GBTC, and 10+ others) using Farside Investors data — the most widely cited public source for institutional BTC demand. Get per-fund daily flows, 7d/30d cumulative flows, flow trend classification, consecutive streak counts, and market-level institutional sentiment. No API key required.

Bitcoin ETF flows are the most direct institutional demand signal available: when BlackRock's IBIT sees $500M+ of daily inflows, institutions are actively accumulating. This actor structures that daily signal for trading bots, portfolio dashboards, and macro research.

***

### Why use Institutional Crypto Flows?

1. **Institutional accumulation/distribution signal** — Total daily ETF net flow is the cleanest measure of institutional BTC demand. Consecutive inflow streaks with growing volumes = accumulation regime; outflows = distribution. Use as a macro filter for position sizing.
2. **ETF market share analysis** — Track which fund (IBIT vs FBTC vs ARKB) dominates flows each week. BlackRock's IBIT dominance vs Fidelity's FBTC growth tells a story about institutional preference and AUM trajectory.
3. **Streak-based momentum** — `consecutive_inflow_days` streaks above 5–7 days have historically preceded BTC price acceleration. Monitor streak lengths as momentum indicators.
4. **Flow-based reversal detection** — When `strong_outflow` appears after a run of inflows, it often precedes price correction. The `flow_trend` field gives you this classification automatically.
5. **Corporate treasury monitoring** — Falls back to bitcointreasuries.net data when Farside is unavailable, providing corporate (MicroStrategy, etc.) and government BTC holdings as an alternative institutional demand lens.

***

### How to use

1. Open the actor on Apify Store and click **Try for free**.
2. Set `daysBack` to control the lookback window for 7d/30d aggregation (default 30 days).
3. Enable `includeAggregates` (default on) for the SUMMARY market-level record.
4. Click **Start**. Returns one record per ETF plus a SUMMARY record with market-level totals.

***

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `daysBack` | integer | `30` | Days of history for 7d/30d aggregates (max 90) |
| `includeAggregates` | boolean | `true` | Write SUMMARY with market-level totals and sentiment |
| `includeFallbackTreasuries` | boolean | `true` | Fall back to bitcointreasuries.net if Farside is unreachable |
| `strongFlowThresholdM` | integer | `100` | USD million threshold for `strong_inflow`/`strong_outflow` classification |

***

### Output

**Per-ETF record:**

```json
{
  "etf_ticker": "IBIT",
  "issuer_name": "BlackRock",
  "flow_today_usd": 524000000,
  "flow_today_btc": 7.4,
  "flow_7d_total_usd": 2100000000,
  "flow_30d_total_usd": 6800000000,
  "aum_usd": 52000000000,
  "consecutive_inflow_days": 8,
  "consecutive_outflow_days": 0,
  "flow_trend": "strong_inflow",
  "market_signal": "accumulation",
  "data_points_available": 120,
  "data_source": "farside.co.uk",
  "fetched_at": "2026-08-29T14:00:00Z"
}
```

**SUMMARY record (market-level aggregates):**

```json
{
  "total_btc_etf_flow_today": 450000000,
  "total_btc_etf_flow_7d": 1200000000,
  "dominant_etf": "IBIT",
  "dominant_issuer": "BlackRock",
  "net_institutional_sentiment": "bullish",
  "strong_inflow_etfs": ["IBIT", "FBTC"],
  "strong_outflow_etfs": ["GBTC"]
}
```

#### Output fields

| Field | Type | Description |
|-------|------|-------------|
| `etf_ticker` | string | Fund ticker (IBIT, FBTC, BITB, ARKB, BTCO, GBTC, etc.) |
| `issuer_name` | string | Asset manager (BlackRock, Fidelity, Bitwise, ARK, etc.) |
| `flow_today_usd` | float | Net USD flow today (positive = inflow, negative = outflow) |
| `flow_7d_total_usd` | float | 7-day cumulative net flow (USD) |
| `flow_30d_total_usd` | float | 30-day cumulative net flow (USD) |
| `aum_usd` | float | Estimated AUM (cumulative net inflows since inception) |
| `consecutive_inflow_days` | integer | Current streak of positive flow days |
| `consecutive_outflow_days` | integer | Current streak of negative flow days |
| `flow_trend` | string | `strong_inflow`, `inflow`, `neutral`, `outflow`, `strong_outflow` |
| `market_signal` | string | `accumulation`, `distribution`, or `neutral` |

***

### ETFs tracked

| Ticker | Issuer | Notes |
|--------|--------|-------|
| IBIT | BlackRock | Largest by AUM |
| FBTC | Fidelity | Second largest |
| BITB | Bitwise | — |
| ARKB | ARK Invest | — |
| GBTC | Grayscale | Converted trust, often has outflows |
| BTCO | Invesco | — |
| HODL | VanEck | — |
| BRRR | Valkyrie | — |
| EZBC | Franklin Templeton | — |
| + others | — | All Farside-tracked ETFs |

***

### Cost estimation

**Pay-Per-Event: $0.001 per actor start + $0.005 per ETF tracked.**

| Use case | ETFs | Estimated cost |
|----------|------|----------------|
| Full ETF sweep (~13 ETFs) | 13 | ~$0.066/run |
| Daily monitoring | 13/day | ~$0.066/day |
| Weekly trend report | 13 × 7 | ~$0.46/week |

***

### FAQ

**Is Farside data official or scraped?**
Farside Investors publishes the data publicly on their website as a free service to the crypto research community. This actor scrapes their published HTML tables — no authentication or API key required.

**How current is the flow data?**
Farside updates daily after US market close. The actor fetches whatever is available at time of run; for same-day data, run after ~6–8pm ET.

**What's the difference between `flow_today_usd` and AUM?**
`flow_today_usd` is the net new money in/out on a single day. `aum_usd` is the cumulative sum of all historical net flows since ETF inception — a proxy for total assets held.

**Does GBTC always show outflows?**
GBTC (Grayscale) was originally a closed-end trust that converted to an ETF in January 2024. It charged higher fees than newer competitors, causing sustained outflows as investors rotated to lower-fee alternatives (IBIT, FBTC). This is a structural trend, not a signal to short GBTC specifically.

***

### Related actors

- [Crypto ETF Flow Tracker](https://apify.com/gochujang/crypto-etf-flow-tracker) — Similar actor with different data sourcing for cross-validation
- [Bitcoin Network Health Dashboard](https://apify.com/gochujang/bitcoin-network-health) — On-chain Bitcoin metrics (complements ETF demand data)
- [Crypto Whale Flow Monitor](https://apify.com/gochujang/crypto-whale-flow-monitor) — Exchange-level on-chain flows for the same institutional demand analysis

### Feedback

If this actor is useful, a quick review helps other institutional crypto traders find it: [Leave a review on Apify Store](https://apify.com/gochujang/institutional-crypto-flows#reviews)

***

**Keywords:** Bitcoin ETF flows, institutional crypto flows, IBIT inflows, BlackRock Bitcoin ETF, Fidelity FBTC flows, spot Bitcoin ETF tracker, ETF flow data, institutional BTC demand, crypto ETF inflows outflows, Farside Investors data, Bitcoin accumulation signal, ETF market share tracker, BTC treasury holdings

# Actor input Schema

## `daysBack` (type: `integer`):

Number of past trading days to include in flow history for 7d/30d aggregates. Min 1, max 90.

## `includeAggregates` (type: `boolean`):

When true, a SUMMARY key-value record is written with total_btc_etf_flow_today, total_btc_etf_flow_7d, dominant_etf, and net_institutional_sentiment.

## `includeFallbackTreasuries` (type: `boolean`):

If farside.co.uk is unreachable, fall back to scraping bitcointreasuries.net for corporate BTC holdings data.

## `strongFlowThresholdM` (type: `integer`):

Daily net flow (absolute value, in millions USD) required for 'strong_inflow' or 'strong_outflow' trend labels. Default 100.

## Actor input object example

```json
{
  "daysBack": 30,
  "includeAggregates": true,
  "includeFallbackTreasuries": true,
  "strongFlowThresholdM": 100
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("gochujang/institutional-crypto-flows").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("gochujang/institutional-crypto-flows").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call gochujang/institutional-crypto-flows --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gochujang/institutional-crypto-flows"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/puN6bnBneXXe9EoYq/builds/5QicVg68Sjd2P1hWx/openapi.json