Automation
Auto Sniper — Buys Before You Could Tap
New tokens launch on pump.fun every few seconds. The sniper watches them all, applies your filters, and buys the ones that pass — in the same block the token was created. It runs with Telegram closed.
Last updated: August 2026
Setting It Up
Six settings, each on its own screen with presets. Configure first, enable second — the bot shows you a summary and asks for confirmation before it starts buying on its own.
| Setting | Presets | Default |
|---|---|---|
| ◎ Buy amount | 0.05 · 0.1 · 0.25 · 0.5 · 1 · 2 · 5 · 10 SOL + custom | 0.1 SOL |
| 🎯 Dev buy | a floor, a ceiling, or both | from 3 SOL |
| 🛑 Snipe limit | 1 · 2 · 3 · 5 · 7 · 10 + custom, or no limit | 3 |
| ⚡ Bid mode | x1 · x2 · x3 | x1 |
| 🧩 Buy mode | fixed SOL or fixed tokens | fixed SOL |
| 🧠 AI Score exit | 20 · 30 · 40 · 50 + custom | off |
Dev Buy — the Filter That Matters
At the moment a token is created there is no liquidity history, no holder count, no chart. One number exists: how much SOL the creator put into their own token. It is their money on the line, and it is the only real signal available in the first seconds.
Set a floor, a ceiling, or both:
Too little
The creator has nothing at stake. A launch they can walk away from costs them nothing.
Too much
They hold enough of the supply to dump on you. A ceiling keeps those out.
The screen shows each bound in SOL and as a percentage of supply — and the number that actually helps you choose:
That estimate updates as you move the bounds, so you can see the effect of a filter before turning the sniper on. A narrow band means long quiet stretches; a wide one means more noise. Both are valid — you just get to see which you picked.
Presets run 0.1 to 5 SOL for the floor and 1 to 20 for the ceiling, with custom up to 1000 on either side. A minimum above the maximum is refused rather than saved, because an impossible band would make the sniper go silent with no error anywhere.
Bid Mode — Priced Against the Live Market
Landing in the first block costs money — a priority fee and a tip. Pay too little and you lose the race; pay a flat high number and you overpay on every quiet launch, which is most of them.
Reaper reads what other buyers are actually paying in that block, right now, and prices your snipe against it. The modes are ceilings, not prices:
| Mode | Maximum per attempt | Use when |
|---|---|---|
| x1 | up to 0.00115 SOL | The default. Quiet launches cost quiet money. |
| x2 | up to 0.0018 SOL | You are competing for launches that draw a crowd. |
| x3 | up to 0.0028 SOL | Headroom for the most contested launches. |
A higher mode only changes anything when a launch is genuinely contested. On an empty one you pay the same either way.
Nothing to Type In
A priority fee you set by hand is a guess that never updates. Pick a number once and it charges the same on a launch nobody is bidding on as on one where twenty bots are fighting — and nothing tells you which of the two you just paid for.
Reaper reads what the block actually costs and prices each attempt against it. The mode you pick is a ceiling; on a quiet launch you pay quiet-launch money without touching a setting.
The same principle runs through the rest of the bot — slippage, priority fee and transaction landing are all sized per trade rather than typed in once and forgotten. Fewer numbers to get wrong, and less spent getting them right.
Buy Mode — Why Fixed SOL Wins
This is the setting most people never need to touch, and the reason it exists is worth one paragraph.
Fixed tokens asks the curve for an exact number of tokens. The problem: between the moment the price is read and the moment the transaction lands, other buyers push into the same block. The cost of your exact amount rises, your limit no longer covers it, and the whole trade reverts. Measured across hundreds of buys, the shortfall ran to a median of 18% and as high as 47% — beyond what any slippage setting can absorb.
Fixed SOL flips it: you commit an amount of SOL and take whatever tokens that buys. Nothing to overshoot, nothing to revert. On the same failed attempts, fixed SOL would have landed every one of them.
Snipe Limit — Your Circuit Breaker
The sniper switches itself off after a set number of buys and tells you. A bad session stays bounded whether you are watching or asleep.
Only confirmed buys count — failed attempts do not consume the limit. The counter resets every time you turn the sniper back on.
Set it to no limit if you want it running indefinitely, but understand what that means with a 0.1 SOL buy amount and a wide dev-buy band.
AI Score After the Buy
The full 14-factor score needs on-chain data that does not exist at second zero, so it arrives about two seconds after the purchase. Hard safety gates — mint authority, freeze authority, Token-2022 traps — run before the buy.
Set a threshold and the bot exits on its own if the score lands below it. This is off by default, deliberately: we would rather you switch it on knowingly than believe you are covered when you are not.
You also get an alert if the score of a token you hold drops later, with a one-tap sell.
What Happens on a Snipe
A message arrives the moment the buy lands, with everything you need to decide what to do next:
The AI Score fills in a couple of seconds later. Four buttons sit under it: Hold, Sell 100%, and two one-tap take-profits at +50% and +100%.
The Entry Price Correction
Because fixed SOL takes whatever tokens the curve gives, the quote at submission is an estimate — the real fill can differ by a fifth or more. If the bot recorded the estimate as your entry price, every PnL number and every take-profit would be measured from the wrong figure.
So it does not. Reaper reads the actual fill from the chain and corrects the position. Around a third of snipes need it.
While that correction is in flight, take-profits on that position are held back — selling on a wrong number would be worse than selling a second late. Stop losses are never held back: a late stop beats no stop.
