BLIX

AI-powered memecoin terminal

How to build a Solana trading bot

A memecoin bot is three parts: data (what is launching and who holds it), a rule (what to buy and when to leave), and execution (signing and sending). Most tutorials start with execution and never get the data right. This guide starts from live data (the BLIX API, included with your account), builds a rule you can test at real quotes without risking SOL, and only then talks about execution. Python and JavaScript.

The BLIX memecoin trading terminalExplore the BLIX terminal ↗

By BLIX · Updated · APIs, live data and MCP

On this page
  1. 1. Data: your BLIX account
  2. 2. A rule worth testing
  3. 3. Test it at real quotes, with paper money
  4. 4. Use the signals with a record
  5. 5. Execution, when you are ready
  6. Mistakes that cost money
  7. More for bot builders
  8. The BLIX community

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

1. Data: your BLIX 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.

# your session is on https://blixvip.com/developers once you are signed in
export BLIX_SESSION="<from your Developers page>"
curl -s https://blixvip.com/api/pulse -H "cookie: blix_wait=$BLIX_SESSION" | head -c 600

You now have every pump.fun launch (launch events on the stream), the Pulse (/api/pulse), every coin's holders with dev, sniper and bundle tags (/api/holders), candles, real Jupiter quotes, signals and the AI's reads.

2. A rule worth testing

Start with a rule that avoids the obvious losers rather than one that predicts winners:

# python: clean final-stretch coins with real buyers
import os, requests, time
BLIX = "https://blixvip.com"; CK = {"blix_wait": os.environ["BLIX_SESSION"]}
def clean(mint):
    h = requests.get(f"{BLIX}/api/holders/{mint}", params={"top": 10}, cookies=CK).json()
    return (not h.get("partial") and h["bundle"]["pct"] < 15 and h["snipers"]["pct"] < 15
            and h["dev"]["pct"] < 5 and h["dev"]["sold"] != "all" and h["top10"] < 35)
def candidates():
    for c in requests.get(f"{BLIX}/api/pulse", cookies=CK).json()["stretch"]:
        if c["hl"]["h"] >= 60 and c["traders"] >= 40 and c["ai"]["grade"] in ("A", "B") and clean(c["mint"]):
            yield c

3. Test it at real quotes, with paper money

Your paper desk fills at the real Jupiter quote with slippage and runs take profit, stop loss and trailing stop on the server. Your bot opens positions; BLIX closes them by the rule; /api/paper and /api/picks show the result.

seen = set()
while True:
    for c in candidates():
        if c["mint"] in seen: continue
        seen.add(c["mint"])
        r = requests.post(f"{BLIX}/api/paper/quoted", json={"mint": c["mint"], "sol": 0.25, "tp": 2.0, "sl": 40, "trail": 25}, cookies=CK).json()
        print("paper buy", c["symbol"], r)
    time.sleep(5)

Run it for a week. Compare with GET /api/perf (how each signal type does) and GET /api/picks (how BLIX's own picks rule does by stage and reason). Most first rules lose; the point is to find out at zero cost.

4. Use the signals with a record

Instead of inventing rules, subscribe to signal events on the stream and act only on the types whose record is good: smart-wallet buys, AI buy calls, dev sells to exit. The record per type is on /api/perf, and a positive signal is never raised on a coin that failed safety.

5. Execution, when you are ready

The BLIX API never signs: real trades are made in the terminal, in one click, with the same exits. If you build your own execution, it is your code with your own key: a Jupiter swap transaction signed with your wallet's keypair and sent through your RPC with a priority fee, in a wallet funded only with what the bot may lose, with per-trade and per-day limits in code, kept in a separate process from the data side.

Mistakes that cost money

  • Buying in the first block: you are the sniper everyone else screens out.
  • Trusting volume: a bot trading with itself makes volume; fees paid and distinct traders do not lie.
  • Skipping the sell quote: a coin you cannot sell is not a position. Quote the sell before the buy.
  • No exit rule: the paper desk's take profit, stop and trailing stop exist because people do not sell.
  • Keys in the data process: one bug and the bot spends everything. Separate them.

More for bot builders

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.

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

Frequently asked questions

Is there an API to build a Solana trading bot on?

BLIX's, with your account: every launch, trade, holder ledger, candle, quote and signal as JSON and a live stream.

Can the bot trade with real money through BLIX?

No. The API quotes and paper-trades; real trades are made in the terminal by you.

How do I build a pump.fun bot specifically?

The same way: pump.fun launches, bonding progress and holders are on the Pulse and holders endpoints from the first trade. The pump.fun API page has the details.

Where do I ask questions?

The BLIX Discord, which comes with your account.

Your next move starts here.

Create your BLIX account to access the trading terminal. Join the Discord community to stay connected.