@vike-io/cli 0.5.0

package/CHANGELOG.md

@@ -0,0 +1,23 @@
+# Changelog
+
+All notable changes are documented here. Entries follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
+
+## 0.5.0 — initial public release
+
+AI-agent CLI for vike.io on-chain analytics, perpetuals, options flow, and prediction-market data across 11 chains.
+
+**15 command groups, 29 backing MCP tools, 33 SKILL.md playbooks** for Claude Code, OpenClaw, Cursor, GitHub Copilot, and other agent runtimes.
+
+```
+vike token   search | transfers | chart | holders
+vike wallet  summary | discover | counterparties | pnl-history | balances | ens
+vike perp    funding | spreads | top-traders
+vike options flow
+vike polymarket markets | market | wallet | smart-money
+vike funds | labels | defi
+vike web     search | fetch
+vike alerts  list | channels | create | edit | delete | register-webhook
+vike init | doctor | schema | whoami | login | logout
+```
+
+Skill discovery: agents auto-discover skills from the `skills/` folder. Manual install: `npx skills add vike-io/vike-cli`.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 vike.io
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,98 @@
+# @vike-io/cli
+
+> Repo + package: `@vike-io/cli` (npm) · `vike-io/vike-cli` (GitHub) · binary: `vike`
+
+[![npm version](https://img.shields.io/npm/v/@vike-io/cli.svg)](https://www.npmjs.com/package/@vike-io/cli)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Node](https://img.shields.io/badge/node-%3E%3D20-brightgreen.svg)](https://nodejs.org)
+
+> **Command-line interface for the [vike.io](https://vike.io) API.** On-chain analytics, perpetuals, options flow, and prediction-market data across 11 chains — designed to be driven by AI agents (Claude Code, OpenClaw) as well as humans.
+
+## Install
+
+```bash
+npm install -g @vike-io/cli
+```
+
+## Quick start
+
+```bash
+vike init                      # interactive: paste API key, verify connection
+vike doctor                    # confirm everything works
+vike token search BTC          # your first query
+```
+
+Get an API key at [vike.io/api/keys](https://vike.io/api/keys).
+
+## Commands at a glance
+
+```
+vike token   search | transfers | chart
+vike wallet  summary | discover
+vike perp    funding | spreads | top-traders
+vike options flow
+vike alerts  list | channels | create | edit | delete
+vike init | doctor | schema | whoami | login | logout
+```
+
+Run `vike schema --pretty` for the full command + flag reference.
+
+## What it does
+
+| Domain | What you can ask |
+|---|---|
+| **Tokens** | Resolve symbols → addresses, see top buyers/sellers, pull OHLCV |
+| **Wallets** | Aggregate metrics per wallet, leaderboards by volume / PnL / netflow |
+| **Perps** | Funding rates + cross-venue spreads across Binance / Bybit / OKX / Aster / Hyperliquid |
+| **Hyperliquid** | Top-trader leaderboard with PnL / ROI / win-rate filters |
+| **Options** | Deribit flow for BTC / ETH / SOL with put-call ratios |
+| **Alerts** | Create transfer alerts; deliver to email or Discord |
+
+## For AI agents
+
+This package ships **skill playbooks** under [`skills/`](skills/) — markdown files designed to be loaded by AI coding agents (Claude Code, OpenClaw, Cursor) so they know when and how to invoke each command.
+
+Skill entry points:
+- `vike-core` — install + auth + conventions (read first)
+- `vike-router` — decide which skill applies
+- `vike-token-research`, `vike-smart-money-discovery`, `vike-perp-funding-arb`, `vike-perp-screener`, `vike-hl-top-traders`, `vike-hl-trader-profile`, `vike-cross-venue-perps`, `vike-options-flow`, `vike-alerts-setup` — task playbooks
+- Per-tool skills for each command
+
+In Claude Code, the bundled skills are auto-discovered after `npm install -g @vike-io/cli`. In other harnesses, point the agent at the `skills/` folder of this package.
+
+## Auth
+
+Three ways to provide your key, in order of precedence:
+
+```bash
+export VIKE_API_KEY=vk_...     # env (wins over everything)
+vike login --api-key vk_...    # saved to ~/.vike/config.json
+vike init                      # interactive
+```
+
+## Environment
+
+| Variable | Default | Purpose |
+|---|---|---|
+| `VIKE_API_KEY` | — | API key (overrides saved config) |
+| `VIKE_MCP_URL` | `https://vike.io/mcp` | MCP endpoint (override for staging/local) |
+
+## Output formatting
+
+By default, table output for humans (TTY) and JSON when piped:
+
+```bash
+vike token search BTC                  # pretty table
+vike token search BTC --json           # JSON
+vike token search BTC | jq '.'         # auto-JSON when piped
+```
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+## Links
+
+- Homepage: [vike.io](https://vike.io)
+- Issues: [github.com/vike-io/vike-cli/issues](https://github.com/vike-io/vike-cli/issues)
+- API docs: [vike.io/api](https://vike.io/api)

package/package.json

@@ -0,0 +1,73 @@
+{
+  "name": "@vike-io/cli",
+  "publishConfig": {
+    "access": "public"
+  },
+  "version": "0.5.0",
+  "description": "AI-agent CLI for vike.io on-chain analytics, perps, options, and prediction markets across 11 chains",
+  "type": "module",
+  "main": "src/index.js",
+  "bin": {
+    "vike": "./src/index.js"
+  },
+  "files": [
+    "src/**/*.js",
+    "scripts/postinstall.js",
+    "skills/**",
+    "CHANGELOG.md"
+  ],
+  "scripts": {
+    "postinstall": "node scripts/postinstall.js",
+    "start": "node src/index.js",
+    "test": "vitest run --passWithNoTests",
+    "test:watch": "vitest",
+    "lint": "eslint .",
+    "lint:fix": "eslint . --fix",
+    "changeset": "changeset",
+    "changeset:version": "changeset version",
+    "changeset:publish": "changeset publish",
+    "sync-schema": "node scripts/sync-schema.js"
+  },
+  "keywords": [
+    "vike",
+    "crypto",
+    "blockchain",
+    "mcp",
+    "ai-agent",
+    "claude-code",
+    "openclaw",
+    "smart-money",
+    "onchain",
+    "perps",
+    "hyperliquid",
+    "options",
+    "deribit",
+    "polymarket",
+    "prediction-markets",
+    "defi",
+    "ethereum",
+    "bsc",
+    "base"
+  ],
+  "author": "vike.io",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/vike-io/vike-cli.git"
+  },
+  "bugs": {
+    "url": "https://github.com/vike-io/vike-cli/issues"
+  },
+  "homepage": "https://vike.io",
+  "engines": {
+    "node": ">=20.0.0"
+  },
+  "dependencies": {
+    "commander": "^12.1.0"
+  },
+  "devDependencies": {
+    "@changesets/cli": "^2.27.9",
+    "eslint": "^9.15.0",
+    "vitest": "^2.1.5"
+  }
+}

package/scripts/postinstall.js

@@ -0,0 +1,20 @@
+// Postinstall — print a friendly setup hint when the user installs vike-cli.
+// Silent in CI environments to avoid log noise.
+
+if (process.env.CI || process.env.npm_config_loglevel === 'silent') {
+  process.exit(0);
+}
+
+const lines = [
+  '',
+  '  @vike-io/cli installed.',
+  '',
+  '  Next steps:',
+  '    vike init                  — interactive setup',
+  '    vike doctor                — verify your install',
+  '    vike token search BTC      — your first query',
+  '',
+  '  Docs: https://vike.io/api',
+  '',
+];
+process.stdout.write(lines.join('\n'));

package/skills/vike-alerts-setup/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: vike-alerts-setup
+description: Create, list, edit, and delete on-chain transfer alerts. Alerts fire when a token transfer crosses USD thresholds you set and deliver to email or Discord. Use when the user asks "alert me when X" / "watch for big transfers" / "notify on whale moves".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-alerts-setup
+
+## Pre-check: what channels does the user have set up?
+
+```bash
+vike alerts channels --json
+```
+
+Returns enabled email + Discord channels. **If a user creates an alert with a channel they haven't verified, the alert is saved but won't fire notifications.** Always check first.
+
+## CRUD
+
+### List
+
+```bash
+vike alerts list --json                    # active alerts
+vike alerts list --include-inactive --json # also paused/deleted
+```
+
+### Create
+
+```bash
+vike alerts create \
+  --label "Big USDC moves" \
+  --token USDC \
+  --chain eth \
+  --min-usd 1000000 \
+  --channel email \
+  --cooldown 60
+```
+
+Required: `--label`. Common: `--token`, `--chain eth|bsc`, `--min-usd`, `--channel email|discord` (can repeat).
+
+### Edit (partial update — only fields you pass are changed)
+
+```bash
+vike alerts edit 42 --min-usd 5000000          # raise threshold
+vike alerts edit 42 --active false             # pause
+vike alerts edit 42 --channel email --channel discord  # add second channel
+```
+
+### Delete
+
+```bash
+vike alerts delete 42                          # soft-delete (pauses, keeps history)
+vike alerts delete 42 --hard                   # permanently remove
+```
+
+## Notes + gotchas
+
+- Currently chains supported: **eth** and **bsc** only. For both, create two alerts.
+- Thresholds are in **USD value** of the transfer at fire time, not token quantity.
+- `--cooldown` is per-alert minimum gap between triggers (default 60 min). Useful to avoid spam during high-volume hours.
+- Tokens are matched by symbol (UPPERCASE). For cross-chain symbols like `USDC` that exist on multiple chains, be explicit with `--chain`.
+- Alerts created without a verified channel will be **silently inactive at fire time** — there is no automatic warning. Use `vike alerts channels` first.
+
+## Confirmation flow with the user
+
+Before creating an alert, summarize back what will be created:
+
+> Creating alert "**Big USDC moves**": will fire when a USDC transfer on **eth** exceeds **$1M**, delivered via **email**, with a 60-minute cooldown. OK to proceed?
+
+Wait for confirmation, then run `vike alerts create`.
+
+## Anti-patterns
+
+- Don't create more than 5 alerts in one batch without confirmation — users almost always over-set on the first try.
+- Don't quote thresholds as token amounts ("alert when 1000 ETH moves"). The system thresholds on USD only.
+- If `min-usd` is < 10000, warn the user — they'll get spammed.

package/skills/vike-alerts-webhook/SKILL.md

@@ -0,0 +1,84 @@
+---
+name: vike-alerts-webhook
+description: Register an HTTPS webhook as an alert delivery channel — get HMAC-signed POST notifications when alerts fire. Use when the user has a server / bot / Slack integration and wants programmatic alert delivery instead of email/Discord.
+allowed-tools: Bash(vike:*)
+---
+
+# vike-alerts-webhook
+
+## Registration
+
+```bash
+vike alerts register-webhook <https://your-server.com/vike-hook>
+  [--secret <16+ char HMAC secret>]
+  [--json]
+```
+
+The secret is **optional but strongly recommended** — without it we still POST, but the recipient has no way to verify it came from us.
+
+## Example
+
+```bash
+# Generate a strong secret first
+openssl rand -hex 32
+# → 7f5c8b...  (paste below)
+
+vike alerts register-webhook https://api.mycoolbot.com/vike-alert \
+  --secret 7f5c8b... \
+  --json
+# → { "ok": true, "channel_id": 42, "url_preview": "https://api.myc...", "signed": true }
+```
+
+Then create an alert and reference the channel — webhooks fire alongside email/discord. (Currently the `alerts create` flow doesn't accept channel IDs directly; webhooks fire if they're the user's enabled channels.)
+
+## What we POST to your URL
+
+```http
+POST /vike-hook HTTP/1.1
+Content-Type: application/json
+User-Agent: vike-alerts/1.0
+X-Vike-Timestamp: 1716658923
+X-Vike-Signature: t=1716658923,sig=a3f8b2c...
+
+{"alert_id":42,"alert_label":"Big USDC moves","alert_type":"transfer","triggered_at":"2026-05-25T17:42:00+00:00","chain":"eth","token":"USDC","value_usd":1234567.89,"from_address":"0x...","to_address":"0x...","tx_hash":"0x..."}
+```
+
+## How to verify the signature (Python)
+
+```python
+import hmac, hashlib, time
+
+def verify(secret, headers, body):
+    sig_header = headers.get("X-Vike-Signature", "")
+    parts = dict(p.split("=", 1) for p in sig_header.split(","))
+    ts, sig = parts.get("t"), parts.get("sig")
+    if not ts or not sig:
+        return False
+    # Reject replays older than 5 min
+    if abs(time.time() - int(ts)) > 300:
+        return False
+    expected = hmac.new(
+        secret.encode(), f"{ts}.{body.decode()}".encode(), hashlib.sha256
+    ).hexdigest()
+    return hmac.compare_digest(expected, sig)
+```
+
+## Anti-patterns
+
+- **Don't** skip the secret. Anyone who knows your webhook URL can spoof alerts without it.
+- **Don't** trust the body without verifying the signature. The URL doesn't authenticate the sender; the HMAC does.
+- **Don't** use HTTP (only HTTPS) in production — the body is sensitive.
+- **Don't** respond slowly — we time out after 10s. If your handler does heavy work, queue it (push to a job queue, return 200 immediately).
+
+## Security checklist for your handler
+
+1. Verify the HMAC signature in constant time (`hmac.compare_digest`, not `==`)
+2. Reject if `X-Vike-Timestamp` is more than ~5 min old (replay protection)
+3. Return `200` quickly; queue work async
+4. Log full body for unsigned-but-suspicious requests
+5. Rotate the secret if you suspect compromise — re-register a new channel
+
+## Pairs well with
+
+- `vike alerts create` — create the alert that fires to your webhook
+- `vike alerts list` / `vike alerts channels` — confirm registration

package/skills/vike-core/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: vike-core
+description: Install-first skill — authentication, setup, and CLI conventions for the vike toolkit. Use when you see any `vike <cmd>` reference or the user mentions on-chain analytics, Hyperliquid perps, options flow, or prediction markets.
+metadata:
+  openclaw:
+    requires:
+      env: [VIKE_API_KEY]
+      bins: [vike]
+    primaryEnv: VIKE_API_KEY
+    install:
+      - kind: node
+        package: "@vike-io/cli"
+        bins: [vike]
+allowed-tools: Bash(vike:*)
+---
+
+# vike-core
+
+Install + auth + conventions. Read this first; every other `vike-*` skill assumes it.
+
+## Install
+
+```bash
+npm install -g @vike-io/cli
+```
+
+## Authenticate (one of these)
+
+```bash
+vike init                          # interactive: prompt for API key + verify
+vike login --api-key vk_...        # non-interactive
+export VIKE_API_KEY=vk_...         # env (wins over saved config)
+```
+
+Get an API key at https://vike.io/api/keys
+
+## Verify
+
+```bash
+vike doctor                        # Node version + API key + endpoint reachability + tool count
+vike whoami                        # which key is in use (masked)
+vike schema --pretty               # full command list with flags
+```
+
+## Conventions
+
+- All commands accept `--json` for pipe-friendly output. Without it, you get a human-readable table.
+- Addresses: pass full 0x-prefixed hex (42 chars). Never truncate when reporting back to the user.
+- USD amounts: integers/decimals (e.g. `--min-usd 10000`).
+- Chain identifiers: `eth`, `bsc`, `base`, `arb`, `hyper`, `btc`, `sol`, `tron`, `xmr`, `zec`, `dash` (depending on the command — some only support a subset).
+- Time windows: `24h`, `7d`, `30d`, `90d`, `all` (per command; check `vike <cmd> --help`).
+
+## Errors
+
+- `No API key` → run `vike init` or set `VIKE_API_KEY`.
+- `MCP error -32000: Hourly rate limit exceeded` → you hit the per-key cap; wait or upgrade your plan.
+- `Network error` / timeout → check `vike doctor`; the endpoint is `https://vike.io/mcp`.
+- `503` from a tool → upstream data source temporarily down; retry in 30s.
+
+## Cost awareness
+
+Each tool call consumes credits against your API key quota. Cheap calls: `token search`, `wallet summary`, `alerts list`. Heavier: `wallet discover`, `hl_perp_top_traders` (large result sets).
+
+## When to use a router skill vs a task skill
+
+- **Router skills** (`vike-router`, topic-level) — when the user is exploring or unsure which command they need.
+- **Task skills** (`vike-smart-money-discovery`, `vike-perp-funding-arb`, etc.) — when the user has a specific question that maps to a known workflow.

package/skills/vike-cross-venue-perps/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: vike-cross-venue-perps
+description: Compare a single perp symbol across all venues — funding, price, spreads. Use when the user asks "where to trade X" / "compare BTC perp across exchanges" / "best venue for ETH long".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-cross-venue-perps
+
+Per-symbol cross-venue analysis.
+
+## Steps
+
+1. Per-venue funding
+   ```bash
+   vike perp funding --symbol <SYM> --json
+   ```
+2. Per-venue spread
+   ```bash
+   vike perp spreads --symbol <SYM> --json
+   ```
+
+## Report template
+
+> **`<SYM>` perp — venue comparison**
+>
+> | Venue | Mark price | Funding (daily %) | Bid-ask edge |
+> |---|---|---|---|
+> | Binance | ... | ... | ... |
+> | Bybit | ... | ... | ... |
+> | OKX | ... | ... | ... |
+> | Aster | ... | ... | ... |
+> | Hyperliquid | ... | ... | ... |
+>
+> **Best venue to long**: `<X>` (lowest funding paid)
+> **Best venue to short**: `<Y>` (highest funding received)
+> **Arb edge**: long-short spread = X%/day
+
+## Reading
+
+- Negative funding on venue → shorts pay longs (longs receive). Good place to be long.
+- Positive funding → longs pay shorts. Good place to be short.
+- A wide divergence (>0.5%/day) between two venues with similar liquidity = arb edge worth quantifying.
+
+## Anti-patterns
+
+- Don't blindly pick the venue with lowest funding without checking liquidity — Hyperliquid funding looks great on small alts but the book might be thin.
+- Funding flips frequently; the read here is "as of now", not a forecast.
+
+## Pairs well with
+
+- `vike-perp-funding-arb` for the full opportunity list across all symbols
+- `vike-perp-screener` for market overview

package/skills/vike-defi-positions/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: vike-defi-positions
+description: DeFi protocol positions for a wallet across all DeBank-supported chains (Aave, Uniswap LP, Curve, Pendle, EigenLayer, etc.) — net USD, asset USD, debt USD per protocol. Use when the user asks "what DeFi positions does this wallet have" / "is wallet X farming yields" / "show me the protocol breakdown for Y".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-defi-positions
+
+## Command
+
+```bash
+vike defi <address> [--json]
+```
+
+## Example
+
+```bash
+vike defi 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045   # vitalik.eth
+```
+
+## Output shape
+
+```json
+{
+  "address": "0x...",
+  "total_balance": {
+    "total_usd": 12345.67,
+    "chains": [
+      { "chain": "eth",    "usd": 9000.00 },
+      { "chain": "arb",    "usd": 2000.00 },
+      { "chain": "base",   "usd": 1345.67 }
+    ]
+  },
+  "protocols": [
+    { "protocol": "Aave V3",      "chain": "eth",  "net_usd": 5000.00, "asset_usd": 8000.00, "debt_usd": 3000.00, "positions": 2 },
+    { "protocol": "Uniswap V3",   "chain": "eth",  "net_usd": 2500.00, "asset_usd": 2500.00, "debt_usd": 0.00,    "positions": 4 },
+    ...
+  ]
+}
+```
+
+## Reading
+
+- `net_usd = asset_usd - debt_usd` — what the position is actually worth
+- A protocol row with `debt_usd > 0` means the wallet is **borrowing** (Aave / Compound / Morpho). High debt + low asset = leveraged.
+- `positions` count tells you how many active positions inside one protocol (e.g. 4 Uniswap LP positions)
+- `total_balance.total_usd` includes both DeFi positions AND wallet token balances; the `protocols` array is DeFi-only
+
+## Anti-patterns
+
+- DeBank may not cover every L2/protocol — a missing protocol doesn't mean the wallet has no position there
+- The `chain` field uses DeBank's IDs (`eth`, `bsc`, `matic`, `arb`, `op`, `base`, etc.) — translate to user-friendly names when reporting
+- Stale data: DeBank refresh varies; freshly-opened positions may not show for 5-15 min
+- If you get `balance_error` or `positions_error`, the DeBank API is rate-limited / down — retry once, then surface the error honestly
+
+## Pairs well with
+
+- `vike labels <addr>` — combine label provenance with DeFi positions for a full institutional view
+- `vike wallet summary <addr>` — on-chain transfer activity vs DeFi positions for the same wallet

package/skills/vike-fund-holdings/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: vike-fund-holdings
+description: Top labeled fund / market-maker / treasury / CEX wallets ranked by recent net inflow USD. Use when the user asks "what are funds buying" / "which whales are accumulating" / "track institutional flows".
+allowed-tools: Bash(vike:*)
+---
+
+# vike-fund-holdings
+
+## Command
+
+```bash
+vike funds [--kind funds|cex|mm|treasury] [--window 7d|30d|90d|180d|all] [--limit N] [--json]
+```
+
+## Examples
+
+```bash
+vike funds --kind funds --window 30d --limit 10
+vike funds --kind cex --window 7d --limit 20
+vike funds --kind treasury --window 90d
+vike funds --kind mm --window 30d
+```
+
+## Kind filters
+
+| Kind | Includes |
+|---|---|
+| `funds` (default) | Treasury wallets + market-makers + custody anchors + Fund / Hedge / VC / Foundation / DAO categories |
+| `cex` | Exchanges (Binance, Coinbase, Bybit, OKX, etc.) |
+| `mm` | Market-makers (Wintermute, GSR, Jump, etc.) |
+| `treasury` | DAO + corporate treasury wallets |
+
+## Output columns
+
+`wallet`, `entity`, `label` (raw provider tag, when available), `wallet_type`, `confidence`, `net_flow_usd` (window), `volume_usd` (window), `tx_count` (window)
+
+## Reading
+
+- **Sort is descending by net_flow_usd** — top accumulators come first
+- A wallet with `entity = "Binance"` and `wallet_type = "cex"` showing massive net inflow = users depositing TO Binance (bearish for prices on the way in), or Binance moving inventory internally
+- `confidence = "High"` rows have multi-source label agreement; `Low` rows are heuristic-only
+- Negative `net_flow_usd` in a list sorted descending = no accumulators above this row; everyone is net-selling
+
+## Anti-patterns
+
+- Don't quote "Binance bought $50M of X" from this view — it's wallet-level flow, not per-token attribution. For per-token, use `vike token holders` then filter for CEX labels.
+- Treasury wallets often have huge one-time inflows (e.g. ICO unlocks); a single 30d window can be misleading. Check `--window all` for context.
+
+## Pairs well with
+
+- `vike labels <addr>` — drill into any specific wallet's full label cascade
+- `vike token holders <addr>` — see which of these wallets hold a specific token
+- `vike-smart-money-discovery` — find unlabeled smart wallets vs labeled funds