pump.fun trading API: what a bot can use today

By BLIX · Updated 2026-10-12 · APIs, live data and MCP

API and MCP access come with every BLIX account · sign in with Google · checked October 10, 2026

pump.fun itself

Programs and IDLs published; no hosted trade API

PumpPortal

Local 0.5% a trade; Lightning (custodial) 1%; trade stream needs a funded key

pumpdev.io

A PumpPortal clone: 0.25% client-side, 0.5% custodial; small, unlicensed

Jupiter

Free routing across launchpads; integrators add their own fee

BLIX

2% (1.6% invited), local-sign only, staked sends, data + AI + stream on the same key

Community

The BLIX Discord, with your account

Side by side

Sources: PumpPortal, pumpdev.io's published code and pricing, Jupiter developer docs and pump.fun's published program interfaces, checked October 10, 2026. Request shapes are the ones each service documents on that date; check its docs for the current field list before you ship.

The same request to PumpPortal and to BLIX

PumpPortal's trade-local answers with the raw transaction bytes and nothing else; BLIX's build answers with the transaction and the quote it was built from, so a bot can refuse a fill it does not like before it signs. Both are signed by you.

# The same buy, 0.1 SOL of one coin, asked of each service.

# PumpPortal trade-local (no key; its 0.5% fee is inside the transaction it returns, as raw bytes to sign)
curl -s https://pumpportal.fun/api/trade-local -H "content-type: application/json" \
  -d '{"publicKey":"'$WALLET'","action":"buy","mint":"'$MINT'","amount":0.1,"denominatedInSol":"true","slippage":3,"priorityFee":0.0001,"pool":"pump"}' \
  --output tx.bin

# BLIX build (your key; Blix's fee inside; JSON with the quote beside the base64 transaction)
curl -s https://blixvip.com/api/v1/trade/build -H "authorization: Bearer $BLIX_KEY" -H "content-type: application/json" \
  -d '{"wallet":"'$WALLET'","mint":"'$MINT'","side":"buy","sol":0.1,"slippageBps":300}'
# → { "transaction": "<base64>", "quote": { "tokensOutUi": …, "feeSol": 0.002, "priorityFeeSol": 0.0001, "marketCapSol": … }, "validForMs": 90000 }

Moving a PumpPortal bot over

1. Trades. Where you posted to trade-local, post to https://blixvip.com/api/v1/trade/build with wallet, mint, side and sol or pct; sign the returned transaction exactly as before and post the signed bytes to /api/v1/trade/send instead of your own RPC. The answer carries the signature, status, slot and landing time.
2. Slippage and fees. PumpPortal's slippage is a percentage; BLIX's slippageBps is basis points (3% = 300). PumpPortal's priorityFee and BLIX's priorityFeeSol are both SOL per transaction.
3. Stream. Point the WebSocket at wss://blixvip.com/api/v1/stream with your key; subscribeNewToken, subscribeTokenTrade, subscribeAccountTrade and subscribeMigration work as they did, and the trade event's fields keep their names.
4. Filters. Before a buy, read GET /api/holders/<mint> (dev share and whether the dev sold, snipers, bundles, top-10 share) and the row's AI call from GET /api/pulse; both are on the same key.

The trade API itself is documented once: the four calls, the flow in curl, what a trade costs, the rules, limits and what is live and what is next.

More on the trade API

BLIX is independent and not affiliated with pump.fun, PumpPortal, pumpdev.io or Jupiter. Facts about pump.fun, PumpPortal, pumpdev.io or Jupiter were checked against public sources on October 10, 2026 and can change.

Memecoins are extremely risky and most go to zero. Nothing on this page is financial advice.

Frequently asked questions