How Vectr works: from launch to a funded agent

Pick a name, symbol and pairing asset, sign one transaction, and the Factory deploys your token and its bonding curve on Robinhood Chain. Launching is free — you pay gas only — and trading starts at the very next block. A fixed 1B supply mints to the curve contract: 800M sells on the curve, 200M is held back for the graduation liquidity position. No presale, no team allocation is set for you — if you want a stake, you buy in on the open curve like everyone else.

The token trades against its curve contract, not an order book. Every buy moves the price up along the curve; every sell moves it down. Price discovery is continuous and fully on-chain, so there is always a counterparty from the first swap.

Every bonding-curve swap carries a 0.97% fee: 0.30% to the creator, 0.67% to the platform. 0.30% of each bonding-curve swap accrues to the token's fee recipient in the market's pairing asset and stays claimable in the FeeCollector until claimed. Accrued fees never expire. 0.67% of each bonding-curve swap goes to Vectr's platform wallets in the same transaction.

Claim from the token page, your profile, the Terminal, or straight from the contract. Fees arrive in the pairing asset — ETH for classic pairs, the Stock Token for memestocks, the stablecoin or crypto asset for those pairs. The fee recipient can be transferred, and already-accrued fees stay claimable.

When the curve's raise hits its threshold, the token graduates: the raised liquidity and remaining supply migrate into a Uniswap V3 pool at the 1.00% fee tier. From then on the token trades like any other pool asset — and accrued curve fees stay claimable.

This is the point of Vectr: launch a token, point an AI agent at the creator fees, and the market funds the agent that runs it. Creator fees can fund the agent that runs the market: claim them and top up its credits. Automatic fee-to-inference settlement through the Vectr LLM Gateway is coming soon. Agents trade on the same rails, through the Terminal, API, CLI or MCP. Agent-built transactions require your confirmation by default. Scheduled orders and read-write API keys can execute automatically, only within the controls you authorise.