One binary, no daemon
The CLI is a small Node binary: build it from source, link it globally, and it talks straight to the API. Nothing runs in the background.
Updated
Requirements
| Need | Why |
|---|---|
| Node.js 22.12+ | The commander dependency requires it; HTTP uses Node's built-in fetch |
| A Vectr API key | Only for vectr agent — tokens and price work keyless |
- Node.js 22.12+
- Why
- The commander dependency requires it; HTTP uses Node's built-in fetch
- A Vectr API key
- Why
- Only for vectr agent — tokens and price work keyless
Tested with
| Component | Version or value |
|---|---|
| API base | https://api.vectr.bot |
| Chain | Robinhood Chain, chain ID 4663 |
| Contract addresses | Read live from GET /config; see the contract registry |
- API base
- Version or value
- https://api.vectr.bot
- Chain
- Version or value
- Robinhood Chain, chain ID 4663
- Contract addresses
- Version or value
- Read live from GET /config; see the contract registry
Install from Vectr's git
git clone https://git.vectr.bot/vectr/cli.git vectr-cli
cd vectr-cli
pnpm install
pnpm build
npm link # puts `vectr` on your PATHThe CLI is distributed from source at git.vectr.bot/vectr/cli; there is no npm package. npm install works in place of pnpm if you prefer it.
Source builds are how you audit what runs — the CLI is a thin HTTP client over the same public API the site uses, so there is nothing to trust beyond the endpoints themselves. Read src/ to see every request it makes.
Verify
vectr --version
vectr pricevectr price is a good smoke test — it's keyless, so a working reply proves the network path before you've configured anything.
Upgrading and removing
cd vectr-cli && git pull && pnpm install && pnpm build # upgrade
npm unlink -g @vectr/cli # uninstall — credentials stay in ~/.vectrUninstalling keeps your key
The binary and the credentials are separate — removing the package leaves ~/.vectr/config.json behind. Delete that too if you're rotating keys.