Skip to main content

Developers

Blank lets you launch Solana tokens straight from your own app. The tokens you create through the SDK behave exactly like the ones launched on blank.build: same token pages, same discovery feed, same trading flow, same fees, same staking, same graduation. Most apps only ever need one call:
const result = await blank.launch.create(input, wallet);
That single call asks Blank to build the launch transactions, asks the creator’s wallet to sign them, and submits the signed bundle. There are lower-level HTTP endpoints behind the scenes (documented for backend adapters and debugging), but you should not need to touch them.
The SDK is the supported integration surface. Raw HTTP endpoints are documented for backend adapters and debugging, but most integrations should not need them.

What you can do today

  • Launch a token on the network Blank is running on.
  • Split creator fees across up to five wallets at launch.
  • Enable creator-side fee allocations in the launch bundle with staking.shareBps, buybackBurn.shareBps, and liquidityCompounding.shareBps.
  • Use server-side API keys to launch from your app backend or automation. Each Blank account can keep up to three active keys.
  • Show API-launched tokens as normal Blank tokens (they get a small “API” badge, nothing else).
  • Top up staking pools with creator-funded bonuses.
  • Export exact current holders and stakers for tokens your API-key account controls.
  • Read public fee status and the live Solana config (program IDs, limits, etc.).
Fee splits and allocation shares use basis points (bps). 100 bps = 1%, so 10,000 bps = 100%. A creator split of 7,000 / 3,000 means 70% / 30%; staking, buyback, and liquidity-compounding shares cannot exceed 10,000 bps combined.

Base URLs

  • API: https://api.blank.build
  • App: https://blank.build
Before writing any low-level Solana code, hit the public manifest endpoint to read the active program IDs, IDL URLs, and size limits. That way nothing is hardcoded against a stale program version.