The agent builds it — a person ships it
Ask the agent to launch a token and it composes the factory transaction: name, ticker, pairing, metadata. The wallet owner reviews and signs — the agent cannot.
Updated
The flow
| Step | Who does it |
|---|---|
| Describe the token — name, ticker, pairing asset | You, in a prompt |
| Upload metadata, compose launch params from live config | The agent, via build_launch_transaction |
| Review the transaction preview — Action and Details | You |
| Sign and broadcast in the Vectr terminal, or submit it with a read-write key | You |
| Token deploys, curve opens, indexer picks it up | The chain and the indexer |
- Describe the token — name, ticker, pairing asset
- Who does it
- You, in a prompt
- Upload metadata, compose launch params from live config
- Who does it
- The agent, via build_launch_transaction
- Review the transaction preview — Action and Details
- Who does it
- You
- Sign and broadcast in the Vectr terminal, or submit it with a read-write key
- Who does it
- You
- Token deploys, curve opens, indexer picks it up
- Who does it
- The chain and the indexer
vectr agent "launch a token called Robinbot, ticker RBT, paired with ETH"What the agent decides for you
The agent reads live config — supply split, curve parameters, enabled pairing assets — and fills in everything you didn't specify. Supply comes from platform config, not the prompt: the full supply mints to the curve contract, the curve portion sells on the bonding curve, and the LP reserve moves into the locked Uniswap position at graduation.
There is no creator or team allocation minted up front — if the launching wallet wants a position, it buys on the open curve like anyone else, or as the optional first buy in the launch transaction.
Constraints the chain enforces
| Rule | Enforced by |
|---|---|
| Daily launch cap per wallet (tiered) | The backend — the current limits are in GET /config under subscription.tiers |
| Pairing asset must be whitelisted | The factory whitelist — the agent only offers enabled ones |
| Graduation threshold is per-asset | Factory config — the agent reads it, never invents it |
- Daily launch cap per wallet (tiered)
- Enforced by
- The backend — the current limits are in GET /config under subscription.tiers
- Pairing asset must be whitelisted
- Enforced by
- The factory whitelist — the agent only offers enabled ones
- Graduation threshold is per-asset
- Enforced by
- Factory config — the agent reads it, never invents it
From the CLI
There is no vectr launch command: a launch is a prompt to vectr agent. The agent returns the transaction as a --- Transaction --- block marked not signed, with a preview of what will deploy. Check that you can launch today first: the cap is per wallet per day, tiered by plan, and served in GET /config.
To ship it, submit the transaction through POST /wallet/sign-and-submit with a read-write key and txType: "launch": the signer checks the calldata against that type (see authentication). Or ask the same thing in the Terminal and confirm it there. Either way the wallet that signs becomes the creator.
Prompts are not parametric: "paired with ETH" works, exact curve internals from a sentence do not. For full control, launch from the UI or call the factory directly; see Integrate: Launch.
A launch is irreversible
Once the factory transaction lands, the token exists — name, ticker and pairing are set on the deployed contract. There is no edit and no refund. Check the preview, then sign.