Examples
03 / 03Prompts that map to real tools
Every example below runs against mainnet today. Answers come back inline; anything that moves funds comes back as a transaction to confirm.
Research — no key needed
"What's the current ETH price on Robinhood Chain?" → vectr_get_price
"Show me the top 10 tokens by market cap." → vectr_get_tokens
"Find tokens with 'robin' in the name." → vectr_search_token
"Give me the curve state for 0x…" → vectr_get_tokenAgent prompts — key required
"What's in my portfolio and what did it cost me?" → portfolio read
"Buy 0.01 ETH of 0x… — build the transaction" → unsigned tx → terminal
"Set a limit buy on 0x… at 20% below current price" → order created server-side
"Claim my creator fees on the tokens I launched" → unsigned tx → terminal
"Launch a token called Robinbot, ticker RBT, paired
with ETH — describe it and build the launch" → unsigned tx → terminalThe agent composes from its own tool set — market reads, portfolio, order management, transaction builders — so one prompt can chain steps: "check the price, and if it's under X, build me a buy."
Reading the response
| Answer ends with | Meaning |
|---|---|
| Plain text | A read or an answer — nothing else happened |
| "Transaction ready — sign it at vectr.bot/terminal" | An unsigned transaction exists. Open the terminal, review it, confirm — nothing is on-chain yet |
| Error: API 401 / 403 | Missing or invalid VECTR_API_KEY — or a read-only key asked to write |
- Plain text
- Meaning
- A read or an answer — nothing else happened
- "Transaction ready — sign it at vectr.bot/terminal"
- Meaning
- An unsigned transaction exists. Open the terminal, review it, confirm — nothing is on-chain yet
- Error: API 401 / 403
- Meaning
- Missing or invalid VECTR_API_KEY — or a read-only key asked to write
The transaction preview is the safety check
Read the Action and Details lines the tool prints before opening the terminal — they tell you what you're about to sign. If they don't match what you asked for, don't confirm it.