On this page
- Install
- Nothing: HTTPS + JSON, your session as the key
- Endpoints
- 54, plus one Server-Sent Events stream
- Languages
- Any: recipes in Python and JavaScript below
- MCP
- 20 tools for AI clients
- Trading
- Quotes and your paper desk; real trades in the terminal
- Community
- The BLIX Discord, with your account
Access comes with your account. Sign in to BLIX with Google, open Developers, and your API session and the MCP connector command are shown there, ready to copy. Everything below assumes you are signed in. Questions: the Discord.
pump.fun from the command line
export BLIX_SESSION="<from your Developers page>"
B=https://blixvip.com; C="cookie: blix_wait=$BLIX_SESSION"
# every pump.fun launch, as it happens
curl -sN $B/api/stream -H "$C" | grep --line-buffered -A1 "event: launch"
# the final stretch, as a table
curl -s $B/api/pulse -H "$C" | jq -r '.stretch[] | [.symbol, .mcap, (.progress*100|round), .hl.h] | @tsv'
# who holds a coin, and did the dev sell
curl -s "$B/api/holders/<mint>?top=10" -H "$C" | jq '{dev, snipers, bundle, top10}'
# a real quote for a 0.5 SOL buy
curl -s "$B/api/quote?mint=<mint>&side=buy&amount=0.5&slip=300" -H "$C"A pump.fun "SDK" in twenty lines
Because the API is HTTPS and JSON, a client is a thin wrapper. JavaScript (Node 20+):
const BLIX = "https://blixvip.com";
const H = { cookie: `blix_wait=${process.env.BLIX_SESSION}` }; // from https://blixvip.com/developers
const get = (p) => fetch(BLIX + p, { headers: H }).then((r) => r.json());
export const pulse = () => get("/api/pulse");
export const coin = (mint) => get("/api/token/" + mint);
export const holders = (mint, top = 25) => get("/api/holders/" + mint + "?top=" + top);
export const candles = (mint, tf = 60) => get("/api/candles/" + mint + "?tf=" + tf);
export const quote = (mint, side, amount, slip = 300) =>
get("/api/quote?mint=" + mint + "&side=" + side + "&amount=" + amount + "&slip=" + slip);
// live launches: the stream is Server-Sent Events over plain HTTPS
export async function onLaunch(fn) {
const res = await fetch(BLIX + "/api/stream", { headers: H });
let buf = "", event = "";
for await (const chunk of res.body.pipeThrough(new TextDecoderStream())) {
buf += chunk;
for (const line of buf.split("\n").slice(0, -1)) {
if (line.startsWith("event:")) event = line.slice(6).trim();
else if (line.startsWith("data:") && event === "launch") fn(JSON.parse(line.slice(5)));
}
buf = buf.slice(buf.lastIndexOf("\n") + 1);
}
}The same in Python is on the pump.fun API in Python page, and TypeScript details on pump.fun API in JavaScript.
What else is out there
| Option | What it is | Trading |
|---|---|---|
| BLIX API and MCP connector | pump.fun and PumpSwap decoded from the chain, holders, candles, quotes, AI reads, with your account | Your paper desk; real trades in the terminal |
| PumpPortal | Third-party pump.fun data and trading API; launch stream free, trade streams and trading metered | Yes, 0.5–1% a trade |
| Program IDLs and community decoders | Scripts that read pump.fun's TradeEvent and CreateEvent yourself | Varies; many ask for your private key |
Never paste a private key into a "pump.fun SDK" you have not read. BLIX never asks for one: the API reads the chain and quotes Jupiter, and the only desk it has is paper.
How BLIX decodes pump.fun
BLIX subscribes to the pump.fun program's logs over a Solana websocket and decodes the Anchor events itself: TradeEvent (mint, SOL and token amounts, buy or sell, trader, the virtual and real reserves after the trade) and CreateEvent (name, symbol, metadata URI, mint, bonding curve, creator). PumpSwap pools and Raydium LaunchLab are read the same way. That is why the API has holders from a coin's first trade and bonding progress to the block.
The BLIX community
Every account comes with the BLIX Discord: the people trading on the terminal, the narratives as they form, feature drops before they are announced, and the team answering questions. Join the Discord once you have signed up.
More for developers
BLIX is independent and not affiliated with pump.fun or PumpPortal. Facts about pump.fun or PumpPortal were checked against public sources on October 10, 2026 and can change.
Frequently asked questions
Is there an official pump.fun SDK?
No. pump.fun publishes no SDK, API keys or developer docs as of October 10, 2026. Everything called a pump.fun SDK is third-party. BLIX reads the chain directly and serves it with your account.
Is there a pump.fun CLI?
BLIX has no separate binary: the API is HTTPS, so curl and jq are the CLI, and AI command-line tools (Claude Code, Codex, Gemini CLI) can drive it through the MCP connector.
Which languages can use it?
Any language with an HTTP client. Python and JavaScript recipes are on their own pages; Go, Rust and shell work the same way.
Can I trade with it?
The API quotes trades through Jupiter and runs your paper desk; it never signs a transaction. Real trading is in the terminal, by you.
How do I get access?
Create a BLIX account and open Developers for your session.

