Token Launch Surface

Launch tokens and collect builder rewards from one operator surface

Use one page to move from token idea to real launch flow: upload metadata and image together, create on pump.fun or letsbonk.fun through the same API-key model used by Corto lightning, then come back to the same surface to claim the reward path that belongs to that platform.

Why teams use this: launch flow, metadata upload, optional dev buy, and reward claim stay in one place instead of being split across separate scripts and one-off forms.

Platform difference: pump uses cashback claim, while letsbonk uses LaunchLab creator fee claim. The builder keeps one operator workflow, but the response stays explicit about which platform-specific claim path actually ran.

Create Builder

Metadata, image, and create transaction

Execution mode API Key * Platform

Ordinary mode uses X-API-Key. Agent mode uses X-Agent-Execution-Key and requires X-Idempotency-Key.

Name Symbol Description

Website (opt.) Twitter (opt.)

Telegram (opt.)

Image

+ Select image Drag and drop or click to choose

Supports PNG, JPG, WEBP up to 2 MB.

Migrate type

Pump cashback accounting Enabled only for pump create flow. letsbonk does not expose this switch and uses migrate mode instead.

Dev wallet buy Optional initial buy in the same create flow for pump.fun and letsbonk.fun.

Loading platform capabilities...

Request Preview

Create request snippets

Change create fields — request example updates automatically.

Snippet follows the current create form values and selected language.

Response

Create response

Status: —

{}

Claim Builder

Claim cashback or creator fee

Request Preview

Claim request snippets

Change claim fields — request example updates automatically.

Snippet follows the current claim form values and selected language.

Response

Claim response

Status: —

{}