Login & keys
02 / 10One key, one file
Login writes your API key to ~/.vectr/config.json and every command picks it up from there — no environment juggling.
Get a key
Sign in on vectr.bot, open your profile, and create a key under API keys. Keys start with vectr_ and are shown once at creation. For a CLI that only researches, create it read-only.
Log in
vectr login --key vectr_…- -k, --key <key>
- The API key — must start with vectr_, anything else is rejected
- --url <url>
- Custom API base — https://api.vectr.bot for mainnet; the default is a localhost dev backend
vectr login --key vectr_… --url https://api.vectr.botWhat gets stored
{ "apiKey": "vectr_…", "apiUrl": "https://api.vectr.bot" }That's the entire credential store — a JSON file in your home directory. Guard it like any private key: don't commit it, don't paste it, and chmod it to 600 on shared machines.
Which commands need it
| Command | Needs the key? |
|---|---|
| vectr agent | Yes — jobs are scoped to the key's wallet; without one it exits with a login hint |
| vectr tokens | No — public data, though it sends the key if present |
| vectr price | No |
| vectr login | Is the key |
- vectr agent
- Needs the key?
- Yes — jobs are scoped to the key's wallet; without one it exits with a login hint
- vectr tokens
- Needs the key?
- No — public data, though it sends the key if present
- vectr price
- Needs the key?
- No
- vectr login
- Needs the key?
- Is the key
Rotating is two steps
Revoke the old key in your profile, then vectr login again — the file is overwritten, and the revoked key dies immediately server-side.