Skip to main content
POST https://router.raze.bot/launch/sol with platform, wallets, the amounts, token and rpcUrl. The transaction plan is the same on every platform.

Common fields

Unknown fields are ignored.

Pump.fun

platform: "pump" (the default).
  • Quote: quoteMint SOL (default), the USDC mint, or another mint pump.fun allows as a quote. Spell SOL exactly SOL; other tickers are refused.
  • Amounts: a wallet past the end of amounts buys amounts[0], and with no amounts at all every wallet buys 0.01 SOL. Send 0 for a wallet that must not buy. Every buyer after the creator spends a small random amount less than asked (up to 2%), so the buys do not look identical.
  • Slippage: each buy spends exactly its amount and takes at least the tokens it is priced at, less slippageBps (default 99%).
  • Past the curve: a buy that empties the bonding curve buys the rest from the pool its migration opens, at that pool’s price. On a Mayhem Mode coin such a buy is refused.
  • Mayhem Mode: mayhem: true (or mayhemMode, pumpType). Only with a SOL or USDC quote.
  • Holder rewards: holderReward: true creates a coin whose creator fee goes to holders (permanent).
  • Flat creator fee: creatorFeeBps, up to the maximum pump.fun’s program allows (300 bps at the time of writing), on a coin quoted in another of pump.fun’s quote mints. On a SOL or USDC coin pump.fun ignores it and the coin pays the standard schedule.
  • Cashback coins are deprecated: cashBack: true is refused.
  • Display creator: offchainCreator sets the creator shown on pump.fun, only on a launch with no buy.
The answer carries mint, transactions and legs.

Raydium LaunchLab

platform: "raydium" (or letsbonk, launchlab) builds a LetsBonk coin quoted in SOL. Choose another platform config with bonkType: Or pass the config address as platformConfig. platform: "usd1" is the same builder quoted in USD1.
platform: "bonk" alone is refused with 400 unknown bonkType "bonk". Use raydium or letsbonk, with bonkType for the other platforms.
The builder checks the curve against the launchpad’s live rules (minimum raise, sell rate, supply) and the creator’s SOL balance before building, and refuses with 502 and the reason. A buyer whose turn comes after the raise is full is refused too. A wallet with no amount simply does not buy. The answer adds pool, the LaunchLab pool of the new mint.

Meteora DBC through Bags

platform: "meteora" (or bags) launches through Bags, in two calls, with Raze’s Bags API key: you need no Bags account.
1

Provision

The first call (no feeShareConfigKey) reserves a …BAGS mint on Bags (irreversible) and answers mint, config, metadataUri and stages: the fee-share config transactions. Sign and land them.
2

Launch

Call again with feeShareConfigKey (the config from step 1), mintPubkey (the reserved mint) and token.metadataUri. The answer is the launch: Bags’ transaction first (v0, partly signed by Bags), then one v1 buy per other wallet.
  • SOL quote only. Every wallet after the creator must buy a non-zero amount.
  • feeClaimers (alias bagsFeeClaimers): { provider, username, bps } (providers twitter, tiktok, kick, github, instagram, onlyfans, solana; share in percent instead of bps also works) sharing the coin’s trading fees; the creator keeps the rest. At most 15 recipients on chain, the creator’s remainder included: 14 claimers when the creator keeps a share, 15 when their shares add up to 10,000 bps.
  • A Jito tip needs at least one buy transaction to ride on.
  • Each buy is priced on the pool as the buy before it leaves it, the creator’s first. On any DBC config whose fee has a dynamic part, Bags’ or another passed as feeShareConfigKey, only the first buy can be priced, and a launch with more is refused. None of Bags’ own configs has one.