SPLICE

Documentation

Your fees, programmable.

SPLICE launches a coin on Pump.fun and builds programs into its creator fee: burn, pay holders, lotteries, AI managers, custom recipes. Everything here is backed by a public API you can call right now.

Live API console

Real requests
GET/api/tokens/4W3pyBh8DuqomNaJQkQ8KNtxLAZQEBgNwW6QhjXPmn7R/trades

Works for any Pump.fun coin.

Pick an endpoint and send a request. The response appears here.

§ 01

Overview

A normal Pump.fun coin, with one change: its creator fees have a job.

Every trade on Pump.fun pays a small creator fee. Normally it all goes to whoever launched the coin. On SPLICE you write a fee spec at launch: keep some, send some to any wallet, and hand the rest to programs that burn supply, pay holders, run lotteries or let an AI decide. Every action is an on-chain transaction listed on the coin's page.

The coin trades on Pump.fun exactly like any other: same bonding curve, same graduation. Only where the creator fee ends up is different.

  1. 01TradeSomeone buys or sells on Pump.fun
  2. 02Creator feePump.fun sets aside the creator share
  3. 03Fee configPump.fun’s fee-sharing config routes it
  4. 04Fee walletCollected every hour
  5. 05ExecuteSwap · credit · burn · buy · send
§ 02

Quickstart

Two requests and one wallet approval. Click any step to inspect it.

Launch sequence

Your app
SPLICE API
Wallet
Solana

Step 1Send name, ticker, image and your fee spec. The server pins metadata to IPFS and derives the coin’s fee wallet.

fetch("/api/launch/prepare", { method: "POST", body })
import { VersionedTransaction } from '@solana/web3.js'

const API = 'https://splicepad.com'
const wallet = window.phantom.solana // any wallet with signAllTransactions

// 1. Describe the coin and what its fees do.
const form = new FormData()
form.append('image', file) // PNG, JPG, GIF or WebP, under 3.5 MB
form.append('data', JSON.stringify({
  name: 'Burn Machine',
  symbol: 'BURN',
  description: 'Every trade buys the coin back and burns it.',
  launcher: wallet.publicKey.toBase58(),
  spec: {
    quoteMint: 'So11111111111111111111111111111111111111112',
    pkg: 'extensions',
    extensions: [{ id: 'buy_burn', weight: 10000, config: { burnBps: 100 } }],
    buySol: 0.1,
  },
}))

// 2. The server builds the transactions.
const prepared = await fetch(`${API}/api/launch/prepare`, { method: 'POST', body: form })
if (!prepared.ok) throw new Error((await prepared.json()).error)
const { mint, txs } = await prepared.json()

// 3. One approval signs all of them.
// feeShare / buy are null when the spec doesn't need them
const roles = (['create', 'feeShare', 'buy'] as const).filter((r) => txs[r])
const unsigned = roles.map((r) => VersionedTransaction.deserialize(Buffer.from(txs[r], 'base64')))
const signed = await wallet.signAllTransactions(unsigned)

// 4. The server verifies and relays them in order.
const body = { mint, txs: Object.fromEntries(roles.map((r, i) => [r, Buffer.from(signed[i].serialize()).toString('base64')])) }
const confirmed = await fetch(`${API}/api/launch/confirm`, {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify(body),
}).then((r) => r.json())

console.log(`Live: ${API}/token/${confirmed.mint}`, confirmed.feeShare) // "shared"
  1. 1

    Prepare

    Metadata and image are pinned to IPFS through Pump.fun, a fresh mint is generated and the coin’s fee wallet is derived from it.
  2. 2

    Sign once

    Create sends 0.01 SOL of fuel to the fee wallet so programs can pay their own network fees. The fee split and an optional buy (up to 10 SOL) are signed in the same approval.
  3. 3

    Verified relay

    The server rejects any signed transaction that differs from what it built (wallet guard instructions like Phantom’s are allowed), then sends them in order.
§ 03

Fee spec

One object decides where every lamport of creator fee goes. Drag the sliders.

The launch wallet20%
Burn + holders in SOL70%
Any Solana address10%
burn 60% · holders 40%

Programs share one Pump.fun shareholder slot, so you can stack as many as you like behind it.

POST /api/launch/prepare · body
{
  "spec": {
    "quoteMint": "So11111111111111111111111111111111111111112",
    "pkg": "custom",
    "creatorBps": 2000,
    "potBps": 7000,
    "wallets": [
      {
        "address": "<PARTNER_WALLET>",
        "bps": 1000
      }
    ],
    "extensions": [
      {
        "id": "buy_burn",
        "weight": 4200,
        "config": {
          "burnBps": 100
        }
      },
      {
        "id": "earn_sol",
        "weight": 2800,
        "config": {}
      }
    ],
    "buySol": 0.25
  }
}

Written into Pump.fun's fee-sharing config

  • <YOUR_WALLET>2000 bps
  • <FEE_WALLET>7000 bps
  • <PARTNER_WALLET>1000 bps

pkg picks the shape: creator (everything to you), holders (Pump.fun's native holder rewards), extensions (everything to programs) or custom. In a custom spec, creatorBps, each wallet's bps and every program's weight are basis points of all fees and must add up to 10,000.

{
  "quoteMint": "So11111111111111111111111111111111111111112",
  "pkg": "extensions",
  "extensions": [
    { "id": "buy_burn", "weight": 10000, "config": { "burnBps": 100 } }
  ],
  "buySol": 0
}
§ 04

Fee routing

Routing is done by Pump.fun itself, not by a promise from us.

Pump.fun has a native fee-sharing config: a per-coin account listing who receives the creator fee. At launch the config is created with your shareholders, and Pump.fun pays them on every distribution.

Programs

One slot → the coin's fee wallet

All programs share a single shareholder slot. The engine collects into it and splits the pot by weight.

You and wallets

Paid straight from Pump.fun

Your share and partner wallets are written into the config. SPLICE never holds these fees.

§ 05

The engine

At five past every hour, each live coin runs one cycle. Recipes tick every minute.

  1. 1

    Pick due coins

    Confirmed, correctly routed, and not run in the last 50 minutes. Each coin is claimed before it runs, so two runs never overlap.
  2. 2

    Collect

    If at least 0.005 SOL of creator fees is waiting on Pump.fun, the fee wallet triggers the distribution and receives it.
  3. 3

    Split the pot

    Spendable = balance − 0.008 SOL reserve − anything owed to holders. Each program gets its weight’s share.
  4. 4

    Wait or act

    Below 0.02 SOL a program waits for more fees instead of wasting network fees on dust.
  5. 5

    Log everything

    Every collect, swap, credit, burn, buy and transfer is recorded with its signature and shown on the coin page.
Engine parameters
ScheduleHourly at :05 · recipes every minute
Minimum collect0.005 SOL
Reserve kept0.008 SOL

Pays transaction fees and token-account rent.

Minimum to act0.02 SOL
SwapsJupiter

Buybacks allow up to 5% slippage.

§ 06

Programs

Every program and the exact rule the engine applies. Filter, search, launch.

30 of 30 programs

M-01

Earn SOL

Rewards

Creator fees are paid out to holders in SOL.

  • SOL already credited but not yet claimed is set aside first; it belongs to holders and is never spent again.
  • The rest is credited pro rata to eligible holders. Nothing is swapped.
{ "id": "earn_sol" }Launch with it
M-02

Earn BTC

Rewards

Creator fees are swapped to cbBTC and paid out to holders.

  • The spendable balance is swapped SOL → cbBTC on Jupiter, then the cbBTC received is credited pro rata.
  • Swap and credit are logged as separate events with their own transactions.
{ "id": "earn_btc" }Launch with it
M-03

Earn ZEC

Rewards

Creator fees are swapped to ZEC and paid out to holders.

  • The spendable balance is swapped SOL → ZEC (Solana SPL ZEC) on Jupiter, then credited pro rata.
  • Holders claim ZEC to their Solana wallet.
{ "id": "earn_zec" }Launch with it
M-04

Earn USDC

Rewards

Creator fees are swapped to USDC and paid out to holders.

  • The spendable balance is swapped SOL → USDC on Jupiter, then credited pro rata.
  • Useful when holders want a stable payout.
{ "id": "earn_usdc" }Launch with it
M-05

Buy & Burn

Supply

Creator fees buy the token back and burn it.

  • The configured share is swapped SOL → your token on Jupiter with 5% max slippage.
  • Every token received is burned in the following transaction; the burn transaction is the receipt.
  • Anything not used for buybacks (above 0.001 SOL) is sent to the launch wallet.
{ "id": "buy_burn" }Launch with it
M-06

NFT Sweep

Supply

Creator fees accumulate and buy the floor of an NFT collection.

  • The collection floor is read from Magic Eden each cycle.
  • When the spendable balance covers the cheapest listing, it is bought and held by the module wallet.
  • Until then, fees keep accumulating — no partial buys.
{ "id": "nft_sweep" }Launch with it
M-07

DCA

Allocation

Every cycle, fees are swapped into one asset and sent to a wallet.

  • The full spendable balance is swapped into the chosen asset each cycle.
  • The asset is sent to the destination wallet, or to the launch wallet if none was set.
{ "id": "dca" }Launch with it
M-08

Holder Lottery

Games

Fees build a pot. One holder wins it, weighted by balance.

  • Fees build up until the draw interval has passed since the last draw (or since launch).
  • Eligible holders are snapshotted; the launch wallet is excluded as well.
  • A winner is picked weighted by balance from a finalized blockhash, and the whole pot is sent in SOL.
{ "id": "lottery" }Launch with it
M-09

Creator Fee Split

Allocation

Fees are split between up to 10 wallets, enforced by Pump.fun itself.

  • Recipients are written straight into Pump.fun’s fee-sharing config at launch — the module wallet never holds these fees.
  • The engine only triggers Pump.fun’s permissionless distribution each hour; Pump.fun pays every recipient.
{ "id": "split" }Launch with it
M-10

Treasury Builder

Allocation

Fees are collected into a treasury, part held in SOL and part in USDC.

  • The configured share is swapped SOL → USDC on Jupiter.
  • USDC and the remaining SOL are sent to the treasury wallet in one transaction.
{ "id": "treasury" }Launch with it
M-11

Earn ETH

Rewards

Creator fees are swapped to ETH and paid out to holders.

  • The spendable balance is swapped SOL → ETH (Wormhole, 8 decimals) on Jupiter, then credited pro rata.
  • Holders claim ETH to their Solana wallet.
{ "id": "earn_eth" }Launch with it
M-12

Earn JUP

Rewards

Creator fees are swapped to JUP and paid out to holders.

  • The spendable balance is swapped SOL → JUP on Jupiter, then credited pro rata.
  • Holders claim JUP to their Solana wallet.
{ "id": "earn_jup" }Launch with it
M-13

Earn BONK

Rewards

Creator fees are swapped to BONK and paid out to holders.

  • The spendable balance is swapped SOL → BONK on Jupiter, then credited pro rata.
  • The minimum claim is 100 BONK.
{ "id": "earn_bonk" }Launch with it
M-14

Earn WIF

Rewards

Creator fees are swapped to WIF and paid out to holders.

  • The spendable balance is swapped SOL → WIF on Jupiter, then credited pro rata.
  • Holders claim WIF to their Solana wallet.
{ "id": "earn_wif" }Launch with it
M-15

Whale Club

Rewards

Only the biggest holders get paid — the top N wallets share the fees in SOL.

  • Unclaimed SOL already credited is set aside first, exactly like Earn SOL.
  • Holders are ranked by balance (the launch wallet excluded) and only the top N are credited, pro rata among themselves.
{ "id": "whale_club" }Launch with it
M-16

Multi-Raffle

Games

Fees build a pot, then several holders win an equal slice of it.

  • Fees build up until the draw interval has passed since the last raffle (or since launch).
  • Distinct winners are picked one by one, weighted by balance, each seeded by the same finalized blockhash plus its index.
  • The pot is split equally and every winner is paid in a single transaction. If a slice would be below rent, the draw waits.
{ "id": "raffle" }Launch with it
M-17

Fee Stream

Allocation

Every cycle, all fees are streamed in SOL to one wallet — a charity, a DAO, a dev fund.

  • The full spendable balance is sent in SOL to the destination wallet every cycle.
  • Nothing is swapped or held back beyond the fee reserve.
{ "id": "stream" }Launch with it
M-18

Burn + Earn

Hybrid

One cycle, two outcomes: part of the fees burns supply, part pays holders in SOL.

  • The burn share buys the token on Jupiter (5% max slippage) and burns everything received.
  • The holder share is credited pro rata in SOL; unclaimed SOL is always reserved.
  • If no holder is eligible yet, the holder share waits in the wallet. Only the remainder above both shares goes to the launch wallet.
{ "id": "combo" }Launch with it
M-19

Flat Dividend

Rewards

Every holder above the minimum gets the exact same SOL, whatever the size of their bag.

  • Every eligible holder (creator, curve and module wallet excluded) gets the same SOL credit, regardless of balance.
  • Unclaimed SOL is reserved and never spent again.
{ "id": "flat_dividend" }Launch with it
M-20

Shrimp Fund

Rewards

Only the small holders get paid. Whales are excluded by rule.

  • Only wallets between the minimum and the maximum holding are credited, one equal share each.
  • Wallets above the cap get nothing from this program for that cycle.
{ "id": "shrimp_fund" }Launch with it
M-21

Biggest Buyer

Games

The wallet that bought the most in the window takes the whole pot.

  • Draws on a timer. Buys in the window are read from Pump.fun’s public trade feed (latest 40 trades) and summed per wallet.
  • The creator, the bonding curve and the module wallet can never win.
{ "id": "top_buyer" }Launch with it
M-22

Last Buyer Wins

Games

A countdown that every buy resets. When nobody buys before it hits zero, the last buyer takes the pot.

  • Every hour the latest buy is read from Pump.fun’s trade feed. If it is older than the timer, that buyer wins.
  • Each winning buy is paid once: its transaction id is stored with the payout.
{ "id": "last_buyer" }Launch with it
M-23

Buyback Vault

Supply

Fees buy the token and lock it in the program wallet, which has no sell instruction.

  • The spendable balance buys the token on Jupiter (5% max slippage).
  • Tokens stay in the module wallet. The engine has no sell or transfer path for them.
{ "id": "buy_vault" }Launch with it
M-24

Cross Burn

Supply

Fees buy a different coin and burn it. Tribute, rivalry or alliance.

  • The spendable balance buys the target coin on Jupiter (5% max slippage), then every token received is burned.
  • Works for classic SPL and Token-2022 coins Jupiter can route to.
{ "id": "cross_burn" }Launch with it
M-25

Index Fund

Allocation

Every hour, fees are spread across BTC, ETH, USDC and SOL and sent to one wallet.

  • The balance is cut into four legs: three are swapped to cbBTC, ETH and USDC, one stays SOL.
  • All four legs are sent to the destination in one transaction.
{ "id": "index_fund" }Launch with it
M-26

Creator Salary

Allocation

The creator takes a fixed daily salary. Everything above it buys the coin and burns it.

  • The creator is paid until the sum of salary payouts in the last 24 hours reaches the daily salary.
  • Everything above it buys the token and burns it in the same cycle.
{ "id": "salary_cap" }Launch with it
M-27

AI Fund Manager

AI

A model you pick reads the market every hour and decides how much to burn, pay holders, keep or pay you.

  • The model receives a pre-formatted brief: price, 1h/6h/24h change, 24h range, recent buy/sell flow, holder count and pot size, plus your rules.
  • It answers {burn, holders, creator, keep, reason}. The creator share is clamped to your limit in code; anything above it is kept.
  • If the model fails, a fallback model answers. If no key is configured, the pot waits untouched.
{ "id": "ai_manager" }Launch with it
M-28

AI Dip Buyer

AI

Fees pile up while a model watches the chart. It fires the buyback and burn when it sees a dip.

  • Each hour the model answers buy or wait from 5-minute candles and recent trades.
  • On buy the whole pot is bought and burned. Once the max wait is reached the engine buys without asking.
{ "id": "ai_dip" }Launch with it
M-29

AI Dividend Picker

AI

Every hour a model picks which asset holders are paid in: SOL, BTC, ETH, USDC, JUP, BONK or WIF.

  • The model picks one of SOL, BTC, ETH, USDC, JUP, BONK, WIF. Any other answer is rejected.
  • That asset is bought on Jupiter and credited pro rata, exactly like the Earn programs.
{ "id": "ai_dividend" }Launch with it
M-30

AI Judge

AI

A model reviews every buyer in the window and awards the pot to the best trade, with a written verdict.

  • Only wallets that bought in the window are listed (25 max), with their buys and sells.
  • The engine rejects any winner that is not on the list, so the model cannot send the pot elsewhere.
{ "id": "ai_judge" }Launch with it
§ 07

AI programs

A model reads the market and decides. Code enforces the limits.

4 programs hand one decision to a model you pick: how to split the pot, when to buy a dip, which asset to pay holders in, or who won a buying contest. The model only ever returns a choice. Amounts, destinations and caps are enforced in code, and any answer outside the allowed set is rejected.

Every run is recorded as a session: the data fetched, the exact brief and prompt the model read, its raw answer with timing, and what was executed. The coin page replays it; the API returns it.

curl "https://splicepad.com/api/tokens/<MINT>/thoughts"
§ 08

Recipes

Wire your own program from blocks: When → If → Do.

A recipe is a graph. Triggers start it, conditions and logic route the value, and actions spend it. Build one on the recipe canvas, describe it in English and let the AI draw it, or send the JSON yourself. Every recipe can be replayed on a real coin's last week first.

{
  "version": 1,
  "nodes": [
    { "id": "t",    "type": "schedule",   "data": { "minutes": 60 } },
    { "id": "s",    "type": "split",      "data": { "ways": 2, "a": 70, "b": 30 } },
    { "id": "dip",  "type": "if",         "data": { "match": "all", "clauses": [
      { "metric": "price_change", "op": "lt", "value": -10, "window": 60 }
    ] } },
    { "id": "buy",  "type": "buy",        "data": { "target": "self" } },
    { "id": "burn", "type": "burn",       "data": {} },
    { "id": "pay",  "type": "distribute", "data": {} }
  ],
  "edges": [
    { "id": "e1", "source": "t",   "sourceHandle": "out", "target": "s" },
    { "id": "e2", "source": "s",   "sourceHandle": "a",   "target": "dip" },
    { "id": "e3", "source": "dip", "sourceHandle": "yes", "target": "buy" },
    { "id": "e4", "source": "buy", "sourceHandle": "out", "target": "burn" },
    { "id": "e5", "source": "s",   "sourceHandle": "b",   "target": "pay" }
  ]
}
Blocks
TriggersEvery, On trades, Fees reach, Market cap crosses, Price drops, Price pumps, New all-time high, Volume exceeds, Holders reach, Graduates, Buy pressure, Wallet trades, Webhook
ConditionsIf, Ask AI
LogicSplit, Cap, Cooldown, First X, then
ActionsSend, Buy, Burn, Keep, Pay holders, Lottery, Run program, Notify

Webhook triggers

A webhook trigger fires its branch when your server calls it, so anything off-chain (a game result, a sales milestone, a vote) can spend fees. The key is shown only to the creator on the coin page.

curl -X POST "https://splicepad.com/api/hooks/<MINT>/<NODE_ID>" \
  -H "x-splice-key: <KEY_FROM_COIN_PAGE>"
After launch, a recipe is…
ImmutableThe recipe is frozen at launch, forever.
TimelockedThe creator can change it; every change waits 24 hours in public first.
MultisigChanges need M of N signer wallets to approve.
Creator editableThe creator can change it instantly. Fastest, least trust.
§ 09

Holder rewards

How holder programs decide who gets what. Drag the sliders.

Each cycle reads every wallet holding the token, skips the bonding curve, the fee wallet and anyone below the coin's minimum holding, and splits the amount in proportion to balance.

Credits go into a ledger rather than thousands of hourly transfers, which would burn the rewards on network fees. They add up until you claim.

Example pro-rata payout
WalletHoldingShareCredited
Bonding curve612,000,000skipped · curve—
7xKp…a91Q38,000,00057.45%0.689342 SOL
Hn2c…Rt4v21,500,00032.50%0.390023 SOL
Module wallet9,000,000skipped · module wallet—
4bWe…p0Lm6,200,0009.37%0.112472 SOL
Qz8u…Ke3s450,0000.68%0.008163 SOL
Dd1r…Yy7n80,000skipped · below minimum—

Example wallets. 4 of 7 addresses qualify; payouts are rounded down to the smallest unit, so the module never credits more than it holds.

§ 10

Claiming

Prove you own the wallet with a signed message. The fee wallet pays the network fee.

  1. 1

    Look up your balance

    Paste your wallet on the Claim page, or call the balances endpoint.
  2. 2

    Sign a message

    A short text naming the token, wallet, asset and time. Not a transaction, costs nothing.
  3. 3

    Get paid

    The full available balance is sent to the wallet that signed. One claim per token and asset can be in flight at a time.
import bs58 from 'bs58'

const time = new Date().toISOString()
const message = [
  'SPLICE claim',
  `mint: ${mint}`,
  `wallet: ${wallet}`,
  `asset: ${asset}`, // SOL | BTC | ZEC | USDC
  `time: ${time}`,
].join('\n')

const { signature } = await window.phantom.solana.signMessage(
  new TextEncoder().encode(message),
  'utf8',
)

const res = await fetch('https://splicepad.com/api/claim', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({ mint, wallet, asset, time, signature: bs58.encode(signature) }),
})
console.log(await res.json())
curl "https://splicepad.com/api/claim?wallet=<YOUR_WALLET>"
Minimum claim per asset
Minimum SOL0.001 SOL
Minimum cbBTC0.00001 cbBTC
Minimum ETH0.00001 ETH
Minimum ZEC0.001 ZEC
Minimum USDC0.1 USDC
Minimum JUP0.1 JUP
Minimum BONK100 BONK
Minimum WIF0.1 WIF
§ 11

Lottery fairness

The draw is seeded by the chain, not by us.

When a draw is due, eligible holders are snapshotted (the launch wallet is excluded) and a recent finalized blockhash is taken. sha256(blockhash:mint) picks the wallet where that number lands on the stacked balances. One ticket per token.

The blockhash, winner and entrant count are logged with the payout, so anyone can re-run the draw.

Verify a draw
import { createHash } from 'node:crypto'

// The lottery event records the seed blockhash, the winner and the entrant count.
// Rebuild the eligible holders (wallet + raw token amount) at the draw's slot,
// in the same order, and the same seed must land on the same winner.
function pick(holders: { owner: string; amount: bigint }[], blockhash: string, mint: string) {
  const supply = holders.reduce((s, h) => s + h.amount, 0n)
  const digest = createHash('sha256').update(`${blockhash}:${mint}`).digest('hex')
  const r = BigInt('0x' + digest) % supply

  let acc = 0n
  for (const h of holders) {
    acc += h.amount
    if (r < acc) return h.owner
  }
}
§ 12

Custody & trust

What is enforced by Pump.fun, and what runs on our servers.

Enforced on chain

  • Who receives creator fees (Pump.fun's fee-sharing config).
  • Your share and partner wallets: fully non-custodial.
  • Every action's transaction, visible on Solscan.

Run by SPLICE

  • Fee wallet keys, derived per coin from a server secret.
  • The engine, recipes and the holder credit ledger.
  • Claim payouts from the fee wallet.
§ 13

API reference

Public, keyless JSON. Amounts are strings in base units. Errors are { error: string }.

  • POST/api/launch/prepare

    Build a launch

    Multipart: image file + data JSON (name, symbol, description, launcher, spec, links).

    8/min
  • POST/api/launch/confirm

    Verify and relay

    Body: { mint, txs: { create, feeShare?, buy? } } signed, base64.

    12/min
  • GET/api/quotes

    Quote pairs

    Every mint Pump.fun accepts as a curve quote, with metadata.

  • GET/api/tokens/[mint]/trades

    Recent trades

    Latest 40 trades for any Pump.fun coin.

  • GET/api/tokens/[mint]/candles?tf=

    Price candles

    1m, 5m, 15m, 1h, 4h or 1d. SPLICE coins only.

  • GET/api/tokens/[mint]/position?wallet=

    A wallet’s position

    Holdings and rewards for one coin.

    60/min
  • GET/api/tokens/[mint]/thoughts

    AI sessions

    Recorded runs of the coin’s AI programs.

  • GET/api/tokens/[mint]/recipe

    Recipe + governance

    The live graph, policy and pending proposals.

  • POST/api/recipes/compile

    English → recipe

    Body: { prompt, model? }. Returns a validated graph.

    8/min
  • POST/api/recipes/backtest

    Replay a recipe

    Runs a graph over a real coin’s recent candles.

    12/min
  • POST/api/hooks/[mint]/[node]

    Fire a webhook trigger

    Header x-splice-key or ?key=.

    6/min
  • GET/api/claim?wallet=

    Claimable balances

    Per token and asset. Add &mint= for one token.

    60/min
  • POST/api/claim

    Claim

    Body: mint, wallet, asset, time, signature (base58).

    10/min
curl "https://splicepad.com/api/tokens/<MINT>/trades"
curl "https://splicepad.com/api/tokens/<MINT>/candles?tf=5m"  # 1m 5m 15m 1h 4h 1d
§ 14

Limits

The numbers that shape every launch and payout.

Limits
Ticker2–10 letters or numbers
ImagePNG, JPG, GIF or WebP, under 3.5 MB
Initial buy0 – 10 SOL
Fee wallet fuel0.01 SOL

Paid by the launcher, used by programs for network fees.

Pump.fun shareholdersUp to 10

All programs share one slot, so you can stack as many as you like.

Lottery interval1 – 168 hours
Rate limitsPer IP, see API reference
§ 15

FAQ

Can I change the spec after launch?
The Pump.fun shareholders are fixed at launch. A recipe’s graph can change later if you chose a timelock, creator or multisig policy.
What happens when the coin graduates?
Creator fees keep flowing through Pump.fun’s fee-sharing config after migration, so programs keep running.
Do I need to hold forever to keep my rewards?
No. Credits are yours once recorded. Selling stops future credits, not ones you already earned.
Why was nothing paid this hour?
Either less than 0.005 SOL of fees was waiting, or the spendable balance was under 0.02 SOL. It carries over.
Do I need an API key?
No. Every endpoint on this page is public and keyless, with per-IP rate limits.