https://router.raze.bot/launch it builds the transactions that deploy a token on a launchpad: the create, with the creator’s buy inside it, then one buy per other wallet. Like the rest of the router it never signs for your wallets and never sends. You sign each transaction with its wallet and broadcast them as you like: one by one, as Jito bundles, in batches.
Solana
Pump.fun, Raydium LaunchLab (LetsBonk, USD1, StonkFun…), Meteora DBC through Bags
Robinhood Chain
pons.family V2 and V1
Routes
Same host as the swap routes,
https://router.raze.bot, and the same rule: your Raze API key on every request (x-api-key, Authorization: Bearer or ?apiKey=). Each request spends credits, and counts against your account’s rate a second together with the API and the router.
Chains and launchpads
Chain and platform names ignore case and punctuation (
Pump.fun is pump). Launchpads that are catalogued but not built yet (for example surge on Solana, hood.fun on Robinhood Chain, fourmeme on BNB Chain) answer 501 not_implemented. An unknown chain or platform is 400.
Response shape
Launch answers in its own envelope,{ ok, data, error, nextCursor }, not in the swap routes’ error shape:
error.message is meant for people, not a stable identifier. Responses carry Cache-Control: no-store.
The Solana transaction plan
One shape for every Solana launch, up to 50 wallets (wallets[0], the creator, included):
legs[i] says who signs transactions[i]:
kindiscreateorbuy. A wallet that buys nothing gets no transaction, sowalletIndexcan skip.- The buys are priced along the bonding curve in the order returned: send them in that order, or the later buys’ slippage bounds no longer hold.
- A Jito tip (
jitoTipSol> 0) rides the last buy only, never the create. With no buy transaction there is no tip. - A product fee (
feeWallet+feeBps, both or neither) is paid by each buyer inside its own transaction, as a share of what that buy spends.
v1 transactions
Every Solana transaction is v1 (SIMD-0385), like the swap routes’ (see Transactions): up to 4,096 bytes, no address lookup tables, and the compute budget inside the message (computeUnitLimit, the priority fee from computeUnitPrice, and the loaded-data limit). Your signer must be able to sign v1 transactions. transactions are base58 strings, or base64 with "encoding": "base64".
The one exception is the Bags launch transaction (platform: "meteora"), which Bags builds and partly signs as v0: its legs[0].version is 0.
The mint’s signature is already in the create, and the blockhash is fetched at build time. If the transactions expire before you send them, build again: the mint’s signature covers the blockhash, so you cannot swap in a new one.
Mint keys
The mint signs the create, so the builder needs the mint’s secret:mintKey: the mint’s 64-byte secret, base58. Use it for a vanity mint you generated yourself.- No
mintKey: a mint is generated and returned asmint. Its secret is not returned (the create is already signed). - A 32-byte public key is refused on Pump.fun and LaunchLab. Pump.fun’s own vanity mints are signed by pump.fun’s API, which signs only v0 transactions.
…BAGS vanity): see Bags.
RPC
Send your RPC in the body asrpcUrl (alias rpc). Raze’s server calls it for every chain read of the build (balances, the launchpad’s config, the blockhash), so use an endpoint that accepts calls from a server.
- Solana: required. A Solana launch without it answers
400 rpcUrl is required. - Robinhood Chain: optional. It must answer chain id 4663, or the build is refused; without it a public Robinhood Chain node is used.
Metadata
token: { name, symbol, description, image } (plus twitter, telegram, website). With token.metadataUri (or uri) set to an http, https or ipfs URL, nothing is uploaded. Without it, the builder downloads the image (JPEG, PNG, GIF or WebP, within 10 s) and uploads the image and the metadata JSON to Raze’s IPFS node. An image that is already an /ipfs/<cid> URL is not downloaded again.