A launch is a prompt — the signature is still yours
There is no vectr launch command. Launching goes through vectr agent: describe the token, the agent builds the factory transaction, you confirm it in the terminal.
The prompt
vectr agent "launch a token called Robinbot, ticker RBT, paired with ETH"The agent fills in what it can — metadata, the pairing asset, the launch parameters — and returns an unsigned transaction plus a preview of what will be deployed. Read that preview; it's the last checkpoint before the chain.
Name, ticker and pairing are the required decisions. Everything else — supply, curve parameters, metadata URI — comes from the platform's live config.
The guardrails you hit
Launches are rate-limited per wallet per day — the cap differs between free and Pro tiers and is served live in GET /config. Check eligibility first with GET /launch/daily-limit/:wallet, or just ask: vectr agent "can I launch right now".
Confirming
The transaction prints as a --- Transaction --- block pointing to vectr.bot/terminal — sign it there under the account the key belongs to. From that point the launch is a normal on-chain transaction: the token deploys, the curve opens, and it indexes into the site within a sync.
Prompts aren't parametric
The agent interprets natural language — "paired with ETH" is fine, but don't expect exact control of curve internals from a sentence. For full parameter control, launch from the UI or call the factory directly — see Integrate → Launch.