vike-corelisted

# 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 →