# New-Token Sniper — AI Pattern Recognition

The **New-Token Sniper** leverages deep historical insights and machine learning to identify early-stage tokens that exhibit the same statistical and behavioral signals as past high-performers. Designed to spot breakout opportunities early, it automates evaluation and decision-making at machine speed.

![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXfV4jy7kKUhlYMez5EM2nEWvOwCoH_TZLkS0bAJbeW5KG-lhxX5ubv1CBe8qo0DbGEezgei6zVMk6AVgk8HwZE8PuugqNfnEeW1fWb3Vm3v1iBF8iOa06RAIX5FliYoIi0MqmEieQ?key=pLJLFHzbL-FOIiOqLBYN8lsL)

A classifier trained on 10 000 00+ historical launches flags tokens whose early-stage metrics mirror past multi-baggers.

| Pipeline Stage        | Detail                                                               |
| --------------------- | -------------------------------------------------------------------- |
| Historical Token Data | Price curves, liquidity curves, holder dispersion, GitHub cadence    |
| Feature Engineering   | Log returns, TVL velocity, whale-wallet overlap, social buzz vectors |
| Pattern Classifier    | Ensemble of GBDT + graph nets produces a moon-score (0–1)            |
| Live Feed             | Brand-new pools scored within seconds of creation                    |
| Trade Decision        | Auto-buy above user-set threshold; auto-skip probable rugs           |

With the New-Token Sniper, users can move early on high-potential tokens—without relying on guesswork or manual analysis.


---

# 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://selen-ai.gitbook.io/selen-ai/new-token-sniper-ai-pattern-recognition.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.