The Vectr CLI gives you the agent, prices and token data from your terminal. Ask questions, script the answers, pipe them into anything that runs a command.
Three steps and you’re in.
Grab the CLI with your package manager, or build it from source.
The package publishes at launch. Until then, use the Source tab.
Create an API key on your profile. It is shown once — save it somewhere safe.
Keys act as your wallet, fenced in by the rules on your Security tab.
Point the CLI at the backend once, then talk to the agent.
Four commands. That’s the whole surface.
Node 18 or newer, on macOS, Linux or Windows.
Every method installs the same vectr binary.
The package publishes at launch. Until then, use the Source tab.
--help lists the commands. Neither of these touches the network.
No install needed for a one-off, once the package is live:
price and tokens read public data and need no key. Anything that reaches the agent does.
The CLI sends your key as an X-API-Key header on every request. Create one on your profile, save it locally, and point the CLI at the backend — it defaults to localhost.
vectr login --key vectr_xxxx --url https://api.vectr.botA key acts as your wallet. Keep it out of git and revoke it the moment it leaks.
Signatures, flags and what each one prints.
vectr agent <prompt> [--json] [--model <id>]
Opens a job, polls it until it settles, then prints the answer. Trades come back as a prepared transaction instead of a receipt.
vectr agent "what tokens are trending?"Thinking...MOON leads the curve at $0.0843, up 34% today.AGENT and PULSE follow, both graduated this week.
vectr price
USD price of the chain's native coin. Labelled with whatever symbol the backend reports, so it follows the chain.
vectr priceETH $4,182.40
vectr tokens [-n <limit>] [--search <query>]
Top tokens by market cap, or a name and symbol search. Graduated tokens are tagged in the output.
vectr tokens -n 3# Symbol Price (USD) Name1 MOON $0.0843 Moonshot [graduated]2 AGENT $0.0312 Agent Coin3 PULSE $0.0129 Pulse
vectr login --key <key> [--url <url>]
Writes the key to the local config. Run it again to swap keys or point the CLI at a different backend.
vectr login --key vectr_xxxx --url https://api.vectr.botLogged in.
The agent is a command, so it composes like one.
Anything the terminal understands works here too.
--json prints the whole job object. Commands exit non-zero when a job fails.
One JSON file, written by vectr login.
Edit the file directly or re-run vectr login. Switching environments is a matter of swapping the key and URL together, since keys are per backend.
{
"apiKey": "vectr_...",
"apiUrl": "https://api.vectr.bot"
}Every error the CLI can print, and what it means.
Not logged in. Run: vectr login --key <your-api-key>
No key in the config. Create one on your profile, then run vectr login. Only agent needs it — price and tokens do not.
Invalid key format — keys start with vectr_
The key was mistyped or truncated. Copy it again from the API keys tab; it is only shown once, so create a fresh one if it is lost.
401: X-API-Key header required
The CLI reached the backend without a key. Usually means the config was written to a different home directory than the one the shell is using.
401: Invalid or revoked API key
The key was revoked, or it belongs to a different backend than the one in --url. Keys are per environment.
403: IP <address> is not in this key's allowlist
The key has an IP allowlist that does not include this machine. Edit it on the Security tab of your profile.
fetch failed / ECONNREFUSED 127.0.0.1:3001
The CLI defaults to localhost. Point it at the real backend: vectr login --key vectr_xxxx --url https://api.vectr.bot
403: Not your job
The job id belongs to another wallet. Each key can only read jobs it created.
Ready to build?
The CLI and the MCP server hit the same endpoints, with the same guardrails.