The command surface this project actually has. Every command is a script in package.json and every endpoint below is a route in src/app/api, with the fields its zod schema really validates. Nothing here is illustrative.
npm run devNext dev server on http://localhost:3000
npm run buildproduction build — the same command Vercel runs
npm startserve the production build (PORT=<n> to move it)
npm run linteslint, must be exit 0 before any commit
npm testnode --test over tests/*.test.ts
npm run grindthe vanity mint grinder, same engine as the Grinder tab
npm run grind -- --start moon --end pumpmint starting with 'moon' and ending with 'pump'
npm run grind -- --end pump --ignore-case --count 3 --out ./keysthree keypairs, case-insensitive, written as standard 64-byte keypair JSON (solana-keygen / Phantom importable)
npm run grind -- --start A --jsonmachine-readable, includes the secret key
npm run grind -- --start moon --end pump --max 20000000 --jsonraise the per-keypair attempt ceiling
base58 has no 0, O, I or l. A pattern longer than six characters is refused rather than run: 587 ≈ 2.2e12 combinations is not a foreground job. Without --json the secret key is never printed.
/api/pinno walletPins the token image (fetched from a URL) and then the metadata JSON to IPFS via Pinata, and returns the uri that goes into create_v2. Mandatory: pump.fun no longer accepts direct metadata uploads. Touches no wallet and no chain.
{
name: string (1..32), symbol: string (1..13),
description?: string (<=2000), imageUrl: string (url),
twitter? telegram? website? discord?: url
}{ ok: true, imageUri, metadataUri, uri }curl -sX POST $APP/api/pin -H 'content-type: application/json' \
-d '{"name":"Moon","symbol":"MOON","imageUrl":"https://example.com/moon.png"}'/api/launch/prepareself-signedBuilds the create_v2 transaction and SIMULATES it. Never sends, never sees a private key. The blockhash is returned with the transaction so a stale one is visible instead of signed blindly.
{
mint, name, symbol, uri, creator, user: base58 (32..44),
mayhemMode?: boolean
}{ ok, transaction (base64), blockhash, simulation } | 400 { error, detail[] }curl -sX POST $APP/api/launch/prepare -H 'content-type: application/json' \
-d '{"mint":"<mint>","name":"Moon","symbol":"MOON","uri":"<uri>","creator":"<wallet>","user":"<wallet>"}'/api/launch/sponsoredsponsored · double-gatedThe treasury pays and signs; the caller only names the wallet that receives its share. Double-gated: TREASURY_LIVE=true in the environment AND live:true in the body. Without both it returns a fully simulated plan and sends nothing.
{
name (1..32), symbol (1..13), uri (1..200),
feeReceiver?: base58, mint?: base58, live?: boolean
}{ ok, mode: "sponsored", sent, signatures[], plan } | { ok, mode: "dry-run", plan }curl -sX POST $APP/api/launch/sponsored -H 'content-type: application/json' \
-d '{"name":"Moon","symbol":"MOON","uri":"<uri>","feeReceiver":"<wallet>","live":false}'/api/shield/launchself-signedThe Shield tab's whole launch: optional sourceMint, the split, the mode, and the three signed transactions. mode self = the user's wallet signs; mode sponsored = the treasury signs. Records the launch in the registry only after confirmation.
{
name, symbol, description?, imageUri: url,
mode: "self" | "sponsored",
sourceMint?, user?, feeWallet?, mint?: base58,
socials?: { twitter?, telegram?, website?: url }
}{ ok: true, mint, mode, signatures[], feeShare } | 422 { ok:false, error:"invalid_launch_input", issues[] }curl -sX POST $APP/api/shield/launch -H 'content-type: application/json' \
-d '{"name":"Moon","symbol":"MOON","imageUri":"<uri>","mode":"self","user":"<wallet>"}'/api/recreateno walletThe brain behind the Shield tab. Reads a real token, proposes an optimised relaunch, renders artwork with Pollinations (flux.1-schnell, server-side so the key never reaches the browser), pins that artwork to IPFS and states the fee split. Deliberately does not pin metadata, sign or send.
{ mint: base58 (32..44), withImage?: boolean } // withImage:false = plan only, no image spend{ ok: true, plan, imageUri?, split }curl -sX POST $APP/api/recreate -H 'content-type: application/json' \
-d '{"mint":"<existing mint>","withImage":false}'/api/registryno walletEvery launch recorded through this platform, newest first. The write side is called only after a launch has actually confirmed, so the board can never list a coin that was merely planned.
?limit=1..200 (default 100){ ok, configured, total, count, launches[], links }curl -s "$APP/api/registry?limit=10"/api/registryno walletRecords one launch. Called by the client after a self launch confirms, and by the sponsored route after it sends.
{
mint, name, symbol, metadataUri,
mode: "self" | "sponsored",
payer, creator, feeWallet?, sourceMint?: base58,
userBps: int 0..10000, platformBps: int 0..10000,
imageUri?: url, signatures: string[] (<=5)
}{ ok: true, total }curl -sX POST $APP/api/registry -H 'content-type: application/json' \
-d '{"mint":"<mint>","name":"Moon","symbol":"MOON","metadataUri":"<uri>","mode":"self","payer":"<w>","creator":"<w>","userBps":7000,"platformBps":3000}'/api/token/[mint]no walletFull snapshot of one token: on-chain state, market data and links. Powers the Explore lookup and the per-token previews.
path param: mint{ ok: true, token: { mint, name, symbol, supply, holders, market, links } }curl -s "$APP/api/token/<mint>"/api/treasuryno walletTreasury address, balance and live flag — read-only. The keypair is never returned, only the public address and its balance.
{ ok, address, balanceSol, live }curl -s "$APP/api/treasury"/api/agent/chatno walletThe platform agent. Takes the conversation so far and answers with the project's own brain: launch flows, fee sharing, treasury controls.
{ message (1..2000), history?: { role: "user"|"assistant", content (<=4000) }[] }{ ok: true, reply, tools? }curl -sX POST $APP/api/agent/chat -H 'content-type: application/json' \
-d '{"message":"what is the default fee split?"}'/api/agent/knowledgeno walletThe knowledge the agent was built from: launch flows, fee-sharing rules, treasury controls. This is what makes /agents answer about THIS project instead of in generalities.
{ ok, entries, knowledge }curl -s "$APP/api/agent/knowledge"$APP is your deployment origin — https://pumplaunchbot.vercel.app in production. Routes marked self-signed return an unsigned transaction for a wallet to sign; sponsored routes are refused unless TREASURY_LIVE=true and the body says live:true.
SOLANA_RPC_URL · NEXT_PUBLIC_SOLANA_RPC_URL · NEXT_PUBLIC_SOLANA_CLUSTER
the private RPC is server-only: shipping an API key to the browser is how keys leak
PINATA_JWT · PINATA_API_KEY · PINATA_API_SECRET · PINATA_GATEWAY
metadata and artwork pinning
TREASURY_KEYPAIR_ENCRYPTED · TREASURY_KEYPAIR_PASSPHRASE · PLATFORM_TREASURY_PUBKEY · NEXT_PUBLIC_PLATFORM_TREASURY_PUBKEY · TREASURY_LIVE
the keypair is stored encrypted and never returned by any route
FEE_SHARE_USER_BPS · FEE_SHARE_PLATFORM_BPS
defaults 7000 / 3000 (70% / 30%)
UPSTASH_REDIS_REST_URL · UPSTASH_REDIS_REST_TOKEN
the board's store; pipelining goes to /pipeline, not the base URL
SOLANATRACKER_API_KEY · SOLSCAN_API_KEY
live lifecycle feed and token lookups
AI_BASE_URL · AI_API_KEY · AI_MODEL
the platform agent's model — River, OpenAI-compatible
POLLINATIONS_API_KEY · POLLINATIONS_IMAGE_MODEL · POLLINATIONS_EDIT_MODEL
generated server-side; the key never reaches the browser
NEXT_PUBLIC_APP_URL · NEXT_PUBLIC_ENABLE_SEND
NEXT_PUBLIC_APP_URL must be inlined at build time; NEXT_PUBLIC_ENABLE_SEND is the client-side send switch
.env.example in the repo is the full list. Secrets stay in environment variables or encrypted storage; nothing in this project writes a key to a page, a log line or a client bundle.