@vike-io/cli 0.16.1 → 0.17.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.17.1
+
+### Patch Changes
+
+- 35213ce: `hl market --view funding_rates`: every perp's latest funding rate, or with `--symbol` one perp's hourly history, HIP-3 markets such as `xyz:CL` included. The view is now listed in the help, `--order desc|asc` is new, and `--sort` takes `oi`, `rate` or `abs_rate` on this view.
+
+## 0.17.0
+
+### Minor Changes
+
+- 17d2b82: `alerts create` / `alerts edit` take the four Polymarket alert types (`--type pm_wallet_trade | pm_market_trade | pm_price_move | pm_resolution`) and the market with `--condition-id`; `--direction` also applies to `pm_price_move`. Every alert type can now be e-mailed (`--channel email`). The `vike-alerts-setup` skill documents the Polymarket alerts, e-mail for Hyperliquid and Polymarket alerts, and the server's cap of 200 active alerts per account.
+
 ## 0.16.1
 
 ### Patch Changes

package/README.md

@@ -145,7 +145,7 @@ Every data command is one `tools/call` to the MCP server. `vike-data <group> --h
 | `vike-data hl` | `cohort-metrics <symbol>`, `segments`, `wallet <address>`, `wallet-activity <address>`, `wallet-trades <address>`, `leaderboard`, `liquidations`, `market`, `orders`, `twaps`, `ledger`, `leverage-changes`, `stats`, `hype-holders`, `builders`, `vaults`, `vault <vault>`, `archive`; a tool with several views takes `--view` | `hl_cohort_metrics`, `hl_segments`, `hl_wallet`, `hl_wallet_activity`, `hl_wallet_trades`, `hl_leaderboard`, `hl_liquidations`, `hl_market`, `hl_orders`, `hl_twaps`, `hl_ledger`, `hl_leverage_changes`, `hl_stats`, `hl_hype_holders`, `hl_builders`, `hl_vaults`, `hl_vault`, `hl_archive` |
 | `vike-data candles` | `hl <symbol>` (Hyperliquid perp or spot, from executed fills; `--view export`, or `--view latest` for the newest bar of every symbol), `polymarket <token_id>` (one outcome token); live bars: `stream hl --channel hl.candles` | `hl_ohlcv`, `polymarket_ohlcv` |
 | `vike-data polymarket` (`pm`) | `markets`, `market <condition_id>`, `wallet <address>`, `smart-money`, `leaderboard`, `market-trades <condition_id>`, `tape`, `orderbook <token_id>`, `market-stats <token_id>`, `settlement <condition_id>`, `settlements`, `archive` | `polymarket_markets`, `polymarket_market_detail`, `polymarket_wallet`, `polymarket_smart_money`, `polymarket_leaderboard`, `polymarket_market_trades`, `polymarket_tape`, `polymarket_orderbook`, `polymarket_market_stats`, `polymarket_settlement`, `polymarket_settlements_bulk`, `polymarket_archive` |
-| `vike-data alerts` | `list`, `channels`, `create`, `edit`, `delete`, `events`, `resend`, `register-webhook`, `test-webhook`, `rotate-secret`: transfer alerts (a token or one wallet, on eth, bsc, base, hyperevm) and Hyperliquid alerts (`--type hl_wallet`, `hl_cohort_fill`, `hl_liquidation`, `hl_cohort_bias`, `hl_liq_proximity`), by email or an HTTPS webhook, HMAC-signed | `alerts_*` |
+| `vike-data alerts` | `list`, `channels`, `create`, `edit`, `delete`, `events`, `resend`, `register-webhook`, `test-webhook`, `rotate-secret`: transfer alerts (a token or one wallet, on eth, bsc, base, hyperevm) Hyperliquid alerts (`--type hl_wallet`, `hl_cohort_fill`, `hl_liquidation`, `hl_cohort_bias`, `hl_liq_proximity`) and Polymarket alerts (`--type pm_wallet_trade`, `pm_market_trade`, `pm_price_move`, `pm_resolution`), by email or an HTTPS webhook, HMAC-signed; at most 200 active alerts per account | `alerts_*` |
 | `vike-data stream <path>` | live events from `wss://stream.vike.io/v1/stream/<path>` (`hl`, `hl-cohorts`, `onchain`, `polymarket`) as NDJSON: `--channel` (one or more), `--filter key=value`, `--cursor` | WebSocket, not MCP |
 | `vike-data stream` | `info`, `check <channel>` (the server's validator), `events <channel>` (stored events, 3 days), `connections` (yours) | `stream_info`, `stream_check_filter`, `stream_events`, `stream_connections` |
 | `vike-data search <q>` | tokens, wallets and entities, HL traders, vaults, builders, Polymarket wallets and markets by name, symbol, address or ENS name | `search` |

package/package.json

@@ -3,7 +3,7 @@
   "publishConfig": {
     "access": "public"
   },
-  "version": "0.16.1",
+  "version": "0.17.1",
   "description": "CLI, agent skills and MCP client for the free Vike Data API: a Polymarket full-L2 order-book archive in Parquet (CC BY 4.0), Hyperliquid positions, fills and cohorts, and labelled Ethereum/BNB wallets",
   "type": "module",
   "main": "src/index.js",

package/skills/vike/SKILL.md

@@ -7,7 +7,7 @@ description: "Use this skill whenever the user asks any question about on-chain
 
 This skill is for anyone who asks an AI agent about crypto data: who is buying a token, what a wallet holds, what Hyperliquid or Polymarket traders are doing right now. It tells the agent which vike tool answers which question and how to read the result, so it does not guess or invent numbers. It reads its data from vike.io and needs a free vike API key.
 
-What the platform has: wallet and token analytics on Ethereum, BSC, Base and HyperEVM (each tool's chain list is under "What each tool really returns"), multi-source wallet labels, CEX perpetual funding and cross-venue spreads, Hyperliquid wallets, cohorts, leaderboards, liquidations, markets, builders, vaults and candles, Polymarket markets, traders, tape, order books, settlements and the Parquet archive, transfer and Hyperliquid alerts, and live event streams over WebSocket. 70 tools in one MCP server.
+What the platform has: wallet and token analytics on Ethereum, BSC, Base and HyperEVM (each tool's chain list is under "What each tool really returns"), multi-source wallet labels, CEX perpetual funding and cross-venue spreads, Hyperliquid wallets, cohorts, leaderboards, liquidations, markets, builders, vaults and candles, Polymarket markets, traders, tape, order books, settlements and the Parquet archive, transfer, Hyperliquid and Polymarket alerts, and live event streams over WebSocket. 70 tools in one MCP server.
 
 **MCP endpoint for all calls:** `https://data.vike.io/mcp` (JSON-RPC 2.0)
 **Or use the CLI:** `npm install -g @vike-io/cli` → `vike-data <command>`
@@ -235,16 +235,16 @@ Every `hl` command takes `--view` (the first view is the default) and only the f
 | `polymarket_smart_money` | MARKETS where the profitable-wallet cohort is flowing (`flows`) or bought below the mid (`mispricings`); not a list of top traders |
 
 ### Alerts
-Create + manage on-chain transfer alerts and Hyperliquid alerts, delivered by email or an HTTPS webhook.
+Create + manage on-chain transfer alerts, Hyperliquid alerts and Polymarket alerts, delivered by email or an HTTPS webhook.
 
 | Tool | Does |
 |---|---|
 | `alerts_list`, `alerts_list_channels` | list rules / enabled channels |
-| `alerts_create`, `alerts_edit`, `alerts_delete` | manage a rule: transfer (token and/or one `address`, chain `eth`/`bsc`/`base`/`hyperevm`, USD thresholds) or Hyperliquid (`--type hl_wallet`, `hl_cohort_fill`, `hl_liquidation`, `hl_cohort_bias`, `hl_liq_proximity`) |
+| `alerts_create`, `alerts_edit`, `alerts_delete` | manage a rule: transfer (token and/or one `address`, chain `eth`/`bsc`/`base`/`hyperevm`, USD thresholds) or Hyperliquid (`--type hl_wallet`, `hl_cohort_fill`, `hl_liquidation`, `hl_cohort_bias`, `hl_liq_proximity`) or Polymarket (`--type pm_wallet_trade`, `pm_market_trade`, `pm_price_move`, `pm_resolution`) |
 | `alerts_events`, `alerts_resend_delivery` | what fired and each delivery's status (15 days); send one again |
 | `alerts_register_webhook`, `alerts_test_webhook`, `alerts_rotate_webhook_secret` | an HTTPS webhook (HMAC-signed deliveries): register, test, rotate its secret |
 
-A token-wide transfer alert fires on ANY transfer of the token above the USD threshold on that chain; an address alert on every transfer of that wallet. Every match is recorded in `alerts events` (15 days) whatever the channels; a transfer alert left with no enabled channel e-mails the account address. Hyperliquid alerts go to a webhook or are read with `alerts events`; only `hl_wallet` may also use email. There is no price or funding alert, no Discord (off) and no Telegram delivery. For a live feed without a rule, use `vike-data stream`.
+A token-wide transfer alert fires on ANY transfer of the token above the USD threshold on that chain; an address alert on every transfer of that wallet. Every match is recorded in `alerts events` (15 days) whatever the channels; a transfer alert left with no enabled channel e-mails the account address. Hyperliquid and Polymarket alerts go to email (one mail per pass, at most 10 a day except `hl_wallet`), a webhook, or are read with `alerts events`. An account has at most 200 active alerts in all (any mix of on-chain, Hyperliquid, Polymarket); pausing frees a slot. There is no token price or funding alert (a Polymarket market's price moves: `pm_price_move`), no Discord (off) and no Telegram delivery. For a live feed without a rule, use `vike-data stream`.
 
 ---
 

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

@@ -1,6 +1,6 @@
 ---
 name: vike-alerts-setup
-description: Create, list, edit, and delete alerts - on-chain transfer alerts (a token, one wallet, USD thresholds; eth, bsc, base, hyperevm) and Hyperliquid alerts (a wallet's fills, cohort fills, liquidations, cohort bias, liquidation proximity) - and read the events they produced. Delivered by email or an HTTPS webhook. Use when the user asks "alert me when X" / "watch for big transfers" / "notify on whale moves" / "tell me when this wallet trades".
+description: Create, list, edit, and delete alerts - on-chain transfer alerts (a token, one wallet, USD thresholds; eth, bsc, base, hyperevm) Hyperliquid alerts (a wallet's fills, cohort fills, liquidations, cohort bias, liquidation proximity) and Polymarket alerts (a wallet's trades, big trades in a market, price moves, a market resolving) - and read the events they produced. Delivered by email or an HTTPS webhook. Use when the user asks "alert me when X" / "watch for big transfers" / "notify on whale moves" / "tell me when this wallet trades".
 allowed-tools: Bash(vike-data:*)
 ---
 
@@ -12,7 +12,7 @@ allowed-tools: Bash(vike-data:*)
 vike-data alerts channels --json
 ```
 
-Returns enabled email + webhook channels. **A channel kind the user has no enabled channel of is dropped from a transfer alert, and a transfer alert left with no channel e-mails the account address.** Whatever the channels, every match is recorded and read with `vike-data alerts events` (kept 15 days). A Hyperliquid alert is delivered by a registered webhook (`vike-alerts-webhook`; asking for one the user has not registered is an error) or only read with `alerts events`; `hl_wallet` alone may also use `--channel email`.
+Returns enabled email + webhook channels. **A channel kind the user has no enabled channel of is dropped from a transfer alert, and a transfer alert left with no channel e-mails the account address.** Whatever the channels, every match is recorded and read with `vike-data alerts events` (kept 15 days). A Hyperliquid or Polymarket alert is delivered by `--channel email` (one mail per pass listing its events; after 10 events in a UTC day no more mail, except `hl_wallet`), by a registered webhook (`vike-alerts-webhook`; asking for one the user has not registered is an error), or only read with `alerts events`.
 
 ## CRUD
 
@@ -43,7 +43,7 @@ vike-data alerts create --label "Treasury in" --chain base \
   --address 0x1111111111111111111111111111111111111111 --address-role to --channel email
 ```
 
-Hyperliquid alerts (`--type`; leave out `--chain`, `--address`, `--max-usd`; delivered by `--channel webhook` (`hl_wallet` also `email`, at most one mail per pass), or with no channel read them with `vike-data alerts events`):
+Hyperliquid alerts (`--type`; leave out `--chain`, `--address`, `--max-usd`; delivered by `--channel email` and/or `webhook`, or with no channel read them with `vike-data alerts events`):
 
 | `--type` | Fires on | Flags |
 |---|---|---|
@@ -58,6 +58,20 @@ vike-data alerts create --label "BTC smart money flips" --type hl_cohort_bias \
   --token BTC --index smi --threshold 0 --band 0.1 --channel webhook
 ```
 
+Polymarket alerts (`--type`; leave out `--chain`, `--address`, `--max-usd`; the same channels). `--wallet` is the proxy wallet the site shows at `vike.io/polymarket/wallet/<address>`; `--condition-id` is the market (`0x` + 64 hex: the id in `vike.io/polymarket/market/<id>`, or find it with `vike-data polymarket markets --view search --query <slug>`):
+
+| `--type` | Fires on | Flags |
+|---|---|---|
+| `pm_wallet_trade` | every trade of one wallet | `--wallet` (required), optional `--condition-id` (one market), `--min-usd` |
+| `pm_market_trade` | big trades in one market | `--condition-id` and `--min-usd` >= 1000 (both required) |
+| `pm_price_move` | the market's price moving sharply | `--condition-id` (required), `--direction up\|down\|both` |
+| `pm_resolution` | the market resolving | `--condition-id` (required) |
+
+```bash
+vike-data alerts create --label "Whale bets on this market" --type pm_market_trade \
+  --condition-id 0x... --min-usd 5000 --channel email
+```
+
 ### Edit (partial update — only fields you pass are changed)
 
 ```bash
@@ -87,9 +101,10 @@ Never delete or hard-delete an alert on your own initiative, to "clean up" or to
 ## Notes + gotchas
 
 - Transfer chains: **eth**, **bsc**, **base**, **hyperevm**, one per alert. For several, create several alerts.
-- **A transfer alert watches a token, one wallet, or both.** Without `--address` it fires on ANY transfer of that token on that chain whose USD value crosses the thresholds. With `--address` it fires on every transfer that wallet sent (`from`), received (`to`) or either (`any`); without `--min-usd` that includes dust and unpriced tokens. "Alert me when whale 0xABCD sells" is `--address 0xABCD --address-role from`; on Hyperliquid it is `--type hl_wallet --wallet 0xABCD --actions close reduce`. There are no price or funding alerts, and delivery is email or an HTTPS webhook (Discord is off; no Telegram).
+- **A transfer alert watches a token, one wallet, or both.** Without `--address` it fires on ANY transfer of that token on that chain whose USD value crosses the thresholds. With `--address` it fires on every transfer that wallet sent (`from`), received (`to`) or either (`any`); without `--min-usd` that includes dust and unpriced tokens. "Alert me when whale 0xABCD sells" is `--address 0xABCD --address-role from`; on Hyperliquid it is `--type hl_wallet --wallet 0xABCD --actions close reduce`. There are no token price or funding alerts (a Polymarket market's price: `pm_price_move`), and delivery is email or an HTTPS webhook (Discord is off; no Telegram).
 - Thresholds are in **USD value** of the transfer at fire time, not token quantity.
-- `--cooldown` is the minimum gap between notifications of a token-wide transfer alert (default 60 min). Address alerts and Hyperliquid alerts notify on every event and ignore it.
+- **At most 200 active alerts per account**, any mix of on-chain, Hyperliquid and Polymarket; the 201st is refused at create or resume. Pausing frees a slot.
+- `--cooldown` is the minimum gap between notifications of a token-wide transfer alert (default 60 min). Address alerts, Hyperliquid and Polymarket alerts notify on every event and ignore it.
 - Tokens are matched by symbol (UPPERCASE). For cross-chain symbols like `USDC` that exist on multiple chains, be explicit with `--chain`.
 - A transfer alert whose channels are not set up is not silent: it falls back to e-mailing the account address, and every match is in `alerts events`. Run `vike-data alerts channels` first so the user gets the delivery they expect.
 

package/src/commands/alerts.js

@@ -4,18 +4,19 @@ import { parseBool, parseInt10 } from '../util.js';
 import { addTool } from './tool-command.js';
 
 // What a rule watches beyond token and USD bounds: a transfer alert's address, and the Hyperliquid
-// parameters. Which alert type takes which is the server's to check; it names the fix.
+// and Polymarket parameters. Which alert type takes which is the server's to check; it names the fix.
 const TARGET_OPTIONS = [
   ['--address <a>', 'transfer: one wallet to watch (0x + 40 hex), sent or received'],
   ['--address-role <r>', 'transfer: any | from | to (default any; needs --address)'],
-  ['--wallet <a>', 'Hyperliquid account (0x + 40 hex): required by hl_wallet and hl_liq_proximity, optional for hl_liquidation'],
+  ['--wallet <a>', 'Hyperliquid account or Polymarket wallet (0x + 40 hex): required by hl_wallet, hl_liq_proximity and pm_wallet_trade, optional for hl_liquidation'],
+  ['--condition-id <id>', 'Polymarket market (0x + 64 hex): required by pm_market_trade, pm_price_move and pm_resolution, optional for pm_wallet_trade'],
   ['--actions <a...>', 'hl_wallet: open close flip increase reduce (default all but reduce)'],
   ['--pnl-cohorts <c...>', 'hl_cohort_fill, hl_liquidation: PnL cohorts, e.g. "3x smart" "2x smart"'],
   ['--size-cohorts <c...>', 'hl_cohort_fill, hl_liquidation: size cohorts, e.g. "4x whale" whale'],
   ['--index <i>', 'hl_cohort_bias (required): smi | wsi | smart_bias | whale_bias | smi_wsi_gap'],
   ['--threshold <n>', 'hl_cohort_bias: level to cross (default 0); hl_liq_proximity: share of the way to liquidation, 0-1 (default 0.8)'],
   ['--band <n>', 'hl_cohort_bias, hl_liq_proximity: hysteresis, > 0 (default 0.1)'],
-  ['--direction <d>', 'hl_cohort_bias: up | down | both (default both)'],
+  ['--direction <d>', 'hl_cohort_bias, pm_price_move: up | down | both (default both)'],
 ];
 
 // `--pnl-cohorts ''` clears the list: send [] (the server refuses ['']).
@@ -33,13 +34,14 @@ function targetArgs(opts) {
     threshold: opts.threshold,
     band: opts.band,
     direction: opts.direction,
+    condition_id: opts.conditionId,
   };
 }
 
 export function registerAlerts(program) {
   const cmd = program
     .command('alerts')
-    .description('Manage alerts: on-chain transfers and Hyperliquid fills, liquidations, cohort bias and liquidation proximity');
+    .description('Manage alerts: on-chain transfers, Hyperliquid fills, liquidations, cohort bias and liquidation proximity, and Polymarket trades, price moves and resolutions (at most 200 active per account)');
 
   cmd
     .command('list')
@@ -83,17 +85,17 @@ export function registerAlerts(program) {
 
   const create = cmd
     .command('create')
-    .description('Create an alert: an on-chain transfer alert (default) or a Hyperliquid alert (--type)')
+    .description('Create an alert: an on-chain transfer alert (default), a Hyperliquid or a Polymarket alert (--type)')
     .requiredOption('--label <l>', 'Alert label (user-visible name)')
-    .option('--type <t>', 'transfer | hl_wallet | hl_cohort_fill | hl_liquidation | hl_cohort_bias | hl_liq_proximity (default transfer)')
+    .option('--type <t>', 'transfer | hl_wallet | hl_cohort_fill | hl_liquidation | hl_cohort_bias | hl_liq_proximity | pm_wallet_trade | pm_market_trade | pm_price_move | pm_resolution (default transfer)')
     .option('--token <sym>', 'transfer: token ticker, UPPERCASE (e.g. USDC); Hyperliquid: the coin (BTC, kPEPE), required by hl_cohort_bias')
     // No default chain: a Hyperliquid alert refuses one.
     .option('--chain <c>', 'transfer only: eth | bsc | base | hyperevm (default eth)')
-    .option('--min-usd <n>', 'transfer: minimum USD value; Hyperliquid: fill or liquidation floor (hl_cohort_fill: required, >= 10000)')
+    .option('--min-usd <n>', 'transfer: minimum USD value; Hyperliquid, Polymarket: fill, liquidation or trade floor (hl_cohort_fill: required, >= 10000; pm_market_trade: required, >= 1000)')
     .option('--max-usd <n>', 'transfer only: maximum USD value');
   for (const [flags, text] of TARGET_OPTIONS) create.option(flags, text);
   create
-    .option('--channel <c...>', 'Notification channel(s): email, webhook (Hyperliquid: webhook, or none and read them with `alerts events`)')
+    .option('--channel <c...>', 'Notification channel(s): email, webhook, for every alert type (or none: read them with `alerts events`)')
     .option('--cooldown <min>', 'Token-wide transfer alerts: minimum gap between notifications (minutes)', '60')
     .option('--json', 'Emit JSON')
     .action(async (opts) => {

package/src/commands/hl.js

@@ -108,15 +108,16 @@ export function registerHl(program) {
 
   addTool(hl, 'market', {
     tool: 'hl_market',
-    desc: 'Open interest per symbol, one symbol\'s hourly series, size breakdown, positions, indices or large fills',
+    desc: 'Open interest per symbol, one symbol\'s hourly series, size breakdown, positions, indices, large fills or funding rates',
     options: [
-      view(['open_interest', 'symbol_metrics', 'size_breakdown', 'positions', 'indices', 'large_fills', 'hourly']),
-      ['--symbol <s>', 'One symbol (required by every view but open_interest, positions and hourly)'],
+      view(['open_interest', 'symbol_metrics', 'size_breakdown', 'positions', 'indices', 'large_fills', 'hourly', 'funding_rates']),
+      ['--symbol <s>', 'One symbol (required by every view but open_interest, positions, hourly and funding_rates; on funding_rates it switches the board of every perp to that perp\'s hourly history)'],
       ['--symbols <list>', 'hourly: comma-separated perps, at most 64 (close, open interest, funding, premium)'],
       ['--days <n>', 'hourly: days back from --end, 1-400 (default 120)'],
       WALLET, AXIS, COHORT, OPENED, START, END,
       ['--open-only <bool>', 'positions: true (default) = latest open; false needs --start'],
-      ['--sort <s>', 'positions: size = biggest positions of one --symbol first'],
+      ['--sort <s>', 'positions: size = biggest positions of one --symbol first; funding_rates (the board): oi (default) | rate | abs_rate'],
+      ['--order <o>', 'funding_rates: desc (default: the board largest first, a history newest hour first) | asc'],
       ['--resolution <r>', 'positions history: 5m | 1h'],
       ['--label-basis <b>', 'symbol_metrics: current'],
       ['--hours <n>', 'indices: window in hours; large_fills: look-back, max 24'],