Examples
03 / 03

Prompts that map to real tools

Every example below runs against mainnet today. Answers come back inline; trades come back as unsigned transactions, and orders need a read-write key.

Updated

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_token

Agent 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, you submit it
"Set a limit buy on 0x… at 20% below current price"     → order created (read-write key)
"Claim my creator fees on the tokens I launched"        → unsigned tx, you submit it
"Launch a token called Nightshift, ticker NIGHT, paired
 with ETH — describe it and build the launch"           → unsigned tx, you submit it

The 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

  • Plain text
    Meaning
    A read or an answer — nothing else happened
  • --- Transaction (unsigned) ---
    Meaning
    An unsigned transaction exists and nothing is on-chain yet. Submit it from the wallet that owns it, or ask the same thing in the Terminal to review and confirm it there
  • Agent job failed: 401 Unauthorized: …
    Meaning
    VECTR_API_KEY is missing, mistyped or revoked
  • …is not available to a read-only API key
    Meaning
    The prompt asked for an order or auto top-up with a read-only key; use a read-write key

The transaction preview is the safety check

Read the transaction the tool prints (to, value, data) before you submit it: it is exactly what you would sign. If it doesn't match what you asked for, don't submit it.