One prompt, one job

vectr agent sends a natural-language prompt to the agent API, waits for the job, and prints either an answer or a transaction to sign. Requires a logged-in key.

Usage

vectr agent "what did my launches earn this week"
vectr agent "build a 0.01 ETH buy of 0x…" --json
vectr agent "deeper analysis please" --model claude-opus-4-7

Flag	Effect
--json	Print the raw job result — status, response, richData — instead of formatted text. The scripting surface
--model <id>	Model override — defaults to claude-sonnet-4-6; premium models selectable

--json
Effect
Print the raw job result — status, response, richData — instead of formatted text. The scripting surface
--model <id>
Effect
Model override — defaults to claude-sonnet-4-6; premium models selectable

What happens

The command posts an /agent/job, polls every 1.5 seconds until the job settles, then prints the response. When the job produced a transaction it prints a --- Transaction --- block with the action and details, and points you to vectr.bot/terminal — the CLI never signs anything.

…agent's answer text…

--- Transaction ---
Action : Buy 0.01 ETH of EXAMPLE
Details: est. 12,400 EX at current curve price, 1% slippage
Sign this transaction in the Vectr terminal: vectr.bot/terminal

The example above is illustrative — token names, amounts and prices in it are not live market data.

Exit codes

Code	Meaning
0	Job completed — answer or transaction printed
1	Job failed or cancelled, the request errored, or you're not logged in

0
Meaning
Job completed — answer or transaction printed
1
Meaning
Job failed or cancelled, the request errored, or you're not logged in

Agent time is job time

A prompt is a job, not a request — it runs tool calls server-side until the turn settles. Prompts that trigger reads finish fast; ones that build transactions take as long as the agent needs to plan them.