ShrineAPI

Ultra Fast Shred Stream

Read from the shreds.
Before the block runs.

Every other feed waits for a block to execute. Ultra Fast Shred Stream reads the transactions straight from the shreds, the moment they arrive, and sends you each pump.fun and PumpSwap transaction before the block has run. Other launchpads and pools come when you ask for them.

On Developer, 2 sockets per key, and Professional, 5.

01Before execution

The earliest look at a trade.

The leader sends its block out in shreds while it builds it. We read the transactions from those shreds, in the leader's order, before any node has run them.

earlierlater
Shreds reach usThe leader sends its block out in shreds while it is still building it.
Ultra Fast Shred StreamEach pump.fun and PumpSwap transaction, read from the shreds and sent to you.
The block executesA node runs the transactions and writes the result.
Feeds that wait for itEvery other feed, ours included, hands that result on.

02How far ahead

First on 98% of pump.fun transactions.

Measured on one machine in the US against the same transactions on 8 October 2026, over the public sockets. The gain is small against the best executed feed; what it buys is the whole order of events, not a fixed head start. The test is in the docs.

98%of pump.fun transactions seen first, in a test from the US on 2026-10-08
6msahead of our own Advanced Data Stream, both on New York
500mints and 500 wallets per connection, or every launch, or the whole tape
60+routers, aggregators and bots whose trades come with their side

03The event

Everything a bot acts on.

The intent, not the result: who sends it, which coin, buy or sell, the amount it puts in and the limit it sets on what comes out. The price it got and the tokens it received do not exist yet; the Advanced Data Stream has them a few milliseconds later.

Every launch, and its tradesJavaScriptexample
const ws = new WebSocket(
  "wss://sol.shrine.trade/api/ultrafast/stream?key=…&creates=1"
);
ws.onmessage = (m) => {
  const e = JSON.parse(m.data);
  if (e.type === "create") {
    // the mint, before the block exists
    console.log("launch", e.symbol, e.mint);
    // and follow its trades
    ws.send(JSON.stringify({ subscribe: [e.mint] }));
  }
  if (e.type === "trade")
    console.log(e.side, e.mint, e.solAmount, "SOL", e.trader);
};
{
  "type": "trade", "protocol": "PUMPFUN", "preExecution": true,
  "signature": "5aP…", "slot": 447483509, "recv": 1791325200231,
  "mint": "…pump", "trader": "…",
  "side": "buy", "tokenAmount": 1250000000000,
  "solAmount": 0.5, "solLamports": 500000000,
  "createBuy": false, "leg": 0,
  "computeUnitPrice": 1000000, "computeUnitLimit": 150000,
  "priorityFeeLamports": 150000, "tipLamports": 1000000,
  "expected": { "tokenAmount": …, "quoteAmount": …,
    "priceImpactBps": 102, "feeBps": 125, "withinLimit": true }
}
  1. Before the block runs.preExecution is always true. slot is the slot whose shreds carried it: the block it lands in, if it lands.
  2. The intent, not the fill.The side, the amount going in and the limit on what comes out. On any buy, the SOL amount is the most the trader pays and tokenAmount is a bound.
  3. The dev buy.createBuy is true when the same transaction creates the coin. It arrives right behind its create.
  4. The fee and the tip.The compute-unit price and limit the transaction sets, the priority fee they come to and the SOL it tips.
  5. The expected fill.On a pump.fun curve, a PumpSwap pool or a Raydium AMM v4 pool: what the trade would get at the pool's last executed state, and whether that meets its own limit.

04Your filter

One WebSocket. Your filter.

A plain WebSocket with JSON text frames. Say what you want in the query string, or change it with messages afterwards; subscribed confirms each change.

  • Connect with your plan's key.As ?key= on the URL, or in the x-api-key header.
  • Pick what to follow.Up to 500 mints and 500 wallets, every launch with creates=1, or the whole tape with all=1.
  • Add other venues.pump.fun and PumpSwap by default. Raydium LaunchLab, Meteora, Raydium and Orca when you name them in protocols.
  • Know if it went through.With status=1, each transaction you were sent is followed by its status, a few milliseconds after it executes.
  • Act in the same region.Frankfurt, Amsterdam and New York, each on its own chain feed. A create names the mint before the block exists, so a Lightspeed buy can leave the same instant.
Subscriptions
Ultra Fast Shred Streambefore executionexample

    05Plans

    Open it with your plan's key.

    Pass your plan's key as ?key= or in the x-api-key header. A key on another plan is refused with 403 plan_required.

    Included in

    Developer and Professional

    Both come with the Advanced Data Stream too, the executed side to account with. A new account can try Developer free for 5 hours, from the dashboard.

    • 2 sockets per key on Developer, 5 on Professional
    • 500 mints and 500 wallets per connection
    • Every region: Frankfurt, Amsterdam and New York
    • A private link: your server in our datacenter, wired straight to the API
    • The Advanced Data Stream: 5 sockets on Developer, 10 on Professional

    Every limit, endpoint by endpoint, is in Plans and limits. Prices are on the pricing page. The trial starts from the dashboard.

    06FAQ

    Questions, answered.

    Anything else is in the Ultra Fast Shred Stream docs.

    What is a shred?

    A Solana block is not sent around as one piece. The leader cuts it into small packets called shreds and sends them out as it builds the block. Put enough shreds together and you have the transactions in the block, as the leader ordered them, before any node has executed them.

    How is it different from the Advanced Data Stream?

    The Advanced Data Stream describes what a transaction did: the price it got, the tokens it received, the fees it paid, the reserves it left behind. Ultra Fast Shred Stream tells you what a transaction asks for: who sends it, which coin, buy or sell, the amount it puts in and the limit on what comes out. Run both: this one to act, the executed stream to account.

    Which launchpads and pools does it cover?

    pump.fun and PumpSwap by default. Name others in protocols to add them: Raydium LaunchLab (BONK and STONKFUN), Meteora DBC, DAMM v2, DAMM v1 and DLMM, Raydium CPMM, AMM v4 and CLMM, and Orca Whirlpool. protocols=all takes every one.

    Does it include transactions that fail?

    Yes. A transaction that will fail is still one the leader is about to run, so it is on this feed, and about half of the transactions on it fail. Turn on statuses with status=1 and each transaction you were sent is followed by whether it went through, a few milliseconds after it executes.

    How do I catch a pump.fun dev buy?

    The dev buy arrives as a trade with createBuy: true, right behind its create. It goes out before a subscribe you send in reply to the create can take effect, so take the whole tape (all=1) and pick the createBuy trades.

    Ultra Fast Shred Stream comes with Developer and Professional.