Everything around a launch, except the launch

These endpoints prepare a launch — metadata, image, gas, eligibility. The launch itself is one on-chain transaction, built by the agent or the factory contract.

Metadata and media

POST /launch/metadata: Upload token metadata → IPFS. Body: name, symbol, description?, imageUrl?, twitter?, telegram?, website?, subjectHandle?
POST /launch/upload-image: Multipart image upload → IPFS. Field: file, max 5 MB

curl -X POST https://api.vectr.bot/launch/metadata \
  -H "Content-Type: application/json" \
  -d '{"name":"Example","symbol":"EX","description":"Docs example"}'

Upload the image first, then pass its URL into metadata. The returned token URI is what the launch transaction stores.

Eligibility and cost

GET /launch/estimate-fee?from=: Gas estimate for a launch from a given wallet
GET /launch/daily-limit/:wallet: Whether the wallet can launch — a per-day cap, tiered by subscription

curl https://api.vectr.bot/launch/daily-limit/0x…

The limit is per wallet and per day

Free and Pro tiers get different daily caps — the current numbers are served live under subscription.tiers.*.launchesPerDay in GET /config. Check the limit before composing, not after the refusal.

The launch transaction itself

There is no POST /launch — launching is a factory contract call, either composed in the UI or built by the agent's build_launch_transaction tool and confirmed by the wallet owner. The on-chain sequence — parameters, event, indexing — is documented in Integrate → Launch, and the end-to-end walkthrough in Agents → Launch a token.