Choose the tool around the pool you need

Safeguard public setup docs describe a guided setup where admins use /add, choose a chain, send the contract, and select a pair.

That setup style is familiar and can be enough for many communities. If your team is looking for a Safeguard buybot alternative, the practical question is more specific: do you need a normal pair feed, or do you need route-aware setup for Base Uniswap v4, Aerodrome, Hydrex, Curve, Balancer, or another exact pool?

Try baes scan for the exact market

Invite @BAESBuyBot, give it permission to post, and run:

/watch

The guided flow asks for chain, token contract, and first-mint block. For direct setup:

/watch base 0xToken any <firstMintBlock> all
/watch base 0xToken any <firstMintBlock> uniswap v4 all

If the pool is already known:

/pool
/pool base 0xPoolAddress 0xTargetToken

For Uniswap v4 pool IDs:

/pool base 0xV4PoolId 0xTargetToken <firstMintBlock>

What to compare

Do not compare only the first alert. Compare the saved market:

/pools
/settings
/topic here

If /pools shows the route buyers actually use, then tune minimum buy size, media, and topic routing. If the saved market is wrong, fix that before judging the feed.

When this works best

Use this path when the group has a concrete market to verify. The strongest Safeguard replacement testing starts from public details the moderator can paste into Telegram: chain, token contract, first-mint block, DEX route, pool address when known, and the topic where alerts should land. That keeps the setup grounded in the market buyers actually use instead of a ticker, screenshot, or vague chart title.

It also helps when a token has more than one pool. A community might talk about the token as if there is only one market, while the chain has an old pair, a newer concentrated-liquidity pool, and a separate route the launch team actually wants to promote. In that situation, the clean setup is not the broadest setup. It is the setup that matches the pinned chart and the route admins expect to see in every alert.

What can still block alerts

The common trap is switching tools before proving the exact pool and topic are correct. Check that before declaring the bot broken. A Telegram group can also block posts through topic permissions, missing admin rights, or a media setting that Telegram refuses to send. Those issues are easier to solve after the saved market is correct.

If your chain or DEX is not listed, message @mrtdlgc on Twitter/X or Telegram with the chain, DEX, token address, first-mint block, pool address if available, and the Telegram group where alerts should post. Specific market details make setup help much faster than a broad request for a buybot.

Summary

baes scan is a Safeguard buybot alternative for teams that want exact chain, route, and pool control. Add @BAESBuyBot, test /watch, use /pool when the market is known, and confirm with /pools.