# Snipe Alert

![](/files/M5Mlvzd2WejPj2wXDttb)\
\
The algorithm mainly focuses on newly formed pairs and fresh wallets.\
\
**Why are fresh wallets important? Fresh wallets are often wallets created specifically for a given token so that others cannot follow the team that implements the token. Often these are Alpha tokens**\
\
In the above visible screenshot, the bot showing information about the token:\
1\. Token name\
2\. Symbol token\
3\. Contract\
4\. Verified contract on Etherscan (very important)\
5\. Market Cap\
6\. Deployer funds\
7\. Taxes (very important)\
8\. Honeypot (very important)\
9\. Amount snipers and fresh wallets (very important)\
10\. Average buy snipers and fresh wallets (very important)\
11\. Information about the large number of fresh wallets (very important)\
12\. Socials (very important)\
\
🚀Example token 1000x called by Snipe Alert: \
\
![](/files/Wz3EeGt3G4nh64jYUvVy)

![](/files/sa7jO62C4c9pFTa0RD0d)\ <br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wallet0x-erc.gitbook.io/0xwallet/snipe-alert.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
