Skip to main content

Deploy

POST 
/token-launches/deploy

Launch a new token on Robinhood Chain (default), Base, Arbitrum One, or Arc. Returns the deployed token address, its pool, and the on-chain fee-beneficiary breakdown. Every Bankr wallet—including Standard, Bankr Club, partner, and provisioned wallets—can make up to three counted launch attempts per rolling 24 hours. On Base all three are eligible for gas sponsorship when the wallet is otherwise eligible; on Robinhood Chain, Arbitrum and Arc retail launches are not gas-sponsored by default.

Authentication — two modes (same endpoint):

  • User API key (X-API-Key: bk_usr_{keyId}_{secret}, or Authorization: Bearer <same>) — deploys from the wallet that owns the API key, which must be read-write with Token Launch API access. feeRecipient is optional; defaults to your wallet. When the key has an allowed-recipients list, the resolved fee recipient must be on it. The signing wallet is limited to 3 counted launch attempts per rolling 24 hours, including provisioned partner wallets.
  • Partner key (X-Partner-Key: bk_ptr_{keyId}_{secret}) — deploys from your partner wallet on behalf of an end user. feeRecipient is required (tells the API where the creator fee should go). The org deployment wallet has the same 3-per-rolling-24-hours wallet cap and remains subject to the partner-specific per-fee-recipient limits of 1/minute, 20/24h, 1 concurrent. Partner fee share is included in the response's feeDistribution.

The server distinguishes user vs partner auth by header, not by token content: X-API-Key / Authorization: Bearer → user key flow; X-Partner-Key → partner flow. Partner keys are never accepted via Bearer.

Quota accounting: a launch slot is released whenever the deploy provably never reached the chain — validation, resolution, pricing and metadata pinning all release the slot they reserved. Submit-stage failures release it only when nothing can have been broadcast; a signer error or timeout that leaves that in doubt keeps the slot counted rather than risk handing back a launch that landed. Completed launches, launches still in flight, and failures that may have gone out all count. The per-fee-recipient daily cap and the duplicate-name caps use the same rule. Simulations never reserve or consume a slot, but carry their own cap of 20 simulations per wallet per rolling 24 hours (non-partner only); exceeding it returns 429. Separately, deploys not made with a partner key — provisioned wallets using their own API key included — are capped at roughly 10 successful deploys per 24 hours per client IP (counted per API process, window starting at the first counted deploy); exceeding it returns 429.

Retail launch-wallet requirements: Bankr may require Standard and Bankr Club wallets to be at least 24 hours old and to hold a minimum native ETH balance on the launch chain; both are runtime controls (even with both off, Arc launches need 0.5 USDC, Arc's gas token, and unsponsored chains need gas). When enabled, a failing launch answers TOKEN_LAUNCH_WALLET_TOO_NEW / TOKEN_LAUNCH_MIN_BALANCE_REQUIRED before quota reservation, metadata pinning, or transaction submission, and retail simulations check wallet age but skip the balance minimum. A wallet that signed up with email waits 72 hours regardless; an X, Farcaster or Telegram account linked after signup counts only once it has been linked for 72 hours, so linking does not shorten the wait. Validated active partner-organization and provisioned-wallet launch paths are exempt.

These gates run on every launch path — chat, social, /agent/prompt and REST alike. Launching is also unavailable from some regions. A launch blocked by a region gate answers 403 with code TOKEN_LAUNCH_NOT_AVAILABLE and the deliberately generic "Token launches are not available for this wallet right now". The email wait answers with the same code and a message giving the hours left and how to launch sooner.

Fee recipient types (feeRecipient.type):

  • wallet — raw EVM address
  • x — Twitter/X username (resolves to Bankr wallet)
  • farcaster — Farcaster username (resolves to verified EVM address)
  • ens — ENS name (resolves to underlying address)

Chain selection: launches default to Robinhood Chain (chain ID 4663, explorer robin.etherscan.io) when chain is omitted. Pass chain: "base" to deploy on Base, chain: "arbitrum" to deploy on Arbitrum One (chain ID 42161, WETH-paired only), or chain: "arc" to deploy on Arc (chain ID 5042). Arc launches run on Bankr Launch v3 (provider: bankr_v3) and are quoted in native USDC, the chain's only launch quote and its gas token; the other chains default to Doppler, and the response's provider says which one a launch used. Partner-key deploys are Base-only — a partner launch with chain: "robinhood", chain: "arbitrum" or chain: "arc" is rejected.

Bankr Launch v3 (Arc): options go in launchV3 — a dev buy, creator vesting (off by default), fees to holders and the creator fee mode. quoteOnlyFees, degenMode and disableVesting are Doppler-only, so setting one to true there answers 400; pairedTokenAddress and pairedStockAddress have no effect. The response adds pool, devBuyOut, percentOfSupplyBps, escrow, split and creatorFeeMode, and its feeDistribution lists creator and bankr. The launch wallet pays gas in USDC and needs at least 0.5 USDC plus any dev buy.

Early balance cap: non-partner Doppler launches limit each wallet to 2% of total supply for the first five minutes. A buy or transfer that would leave the recipient above 2% fails until the cap expires. Partner launches—including deploys from provisioned partner wallets—are exempt. The expiry is encoded on-chain at launch, so existing tokens retain their original expiry. This balance cap is separate from the 14-second anti-snipe fee decay.

Additional quote tokens: user-key launches can pass pairedTokenAddress to quote the launch pool in a fixed allowlisted token instead of WETH. On Base (chain: "base"): BNKR (0x22af33fe49fd1fa80c7149773dde5890d3c76f3b), ba3Pump (0x5577a294ae5a21446a11b0e4100ca83803995720, Bankr-bridged PUMP from Solana), cbHYPE (0xB200000000000000000000451d033a5000cb479e), cbZEC (0xB2000000000000000000008501b13360000cb2EC), or TAO (0xf3081494b87e8d5fb7960f066e931d1d0e6e3d67, Bittensor on Base). On Robinhood Chain (chain: "robinhood"): BNKR (0x178E54df3D091EE4D0B2534742eF9e3692b76526, the Robinhood Chain BNKR contract — a different address from Base BNKR) or musebook (0x91A2DAe9699f0B82540B5886b0d8759C22820bA3, a Bankr-launched token). Each address is valid only on its own chain; pairedTokenAddress is unavailable on Arbitrum and for partner-key deploys, and cannot be combined with pairedStockAddress.

Quote-only fees (Doppler): pass quoteOnlyFees: true to collect all creator fees in the quote token (e.g. WETH) instead of a mix of the launched token and quote token. The creator's total take is identical either way. Fixed at launch.

Degen mode (Doppler): pass degenMode: true to start the token at a $2,500 market cap instead of the standard starting market cap. Supply, fee schedule and vesting are unchanged — only the starting valuation moves. Fixed at launch, and rejected with 400 on partner-key deploys.

Creator vesting (Doppler): 15% of supply vests to the fee recipient over 1 year with a 30-day cliff unless you pass disableVesting: true. Partner-key deploys never vest.

Simulation mode: pass simulateOnly: true to get the predicted token address and fee distribution without broadcasting a transaction or reserving launch quota. Response status becomes 200 OK and txHash is omitted. Retail simulations still run the wallet-age check, but the minimum-balance check stays off, and they are capped at 20 per wallet per rolling 24 hours (partner deploy paths exempt). A wallet already at its 3 counted launch attempts is refused a simulation too, with the same 429 a real deploy would get — simulating still consumes no slot.

Request​

Responses​

Simulation succeeded (simulateOnly: true). No transaction was broadcast.