> For the complete documentation index, see [llms.txt](https://docs.swoop.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.swoop.fun/swoop-pro/about-swoop-pro.md).

# About Swoop Pro

<figure><img src="https://1965679461-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6ChFFAAPr98iDFraSOTh%2Fuploads%2Fm3bPrMaQsaNFOKM6jpCX%2Fimage.png?alt=media&amp;token=4ef216d9-2d1e-48d6-b067-c2c7e8e9fbe3" alt=""><figcaption></figcaption></figure>

**Swoop Pro is a DEX-trading tool that transforms raw on-chain chaos into clear, actionable trading opportunities.**

The system analyzes tens of thousands of new tokens every day using both blockchain data and signals from X (Twitter), identifying promising tokens and opening them for trading **before the wider market becomes aware of them**.

Swoop Pro also evaluates each token’s **developer**, compiling data on all tokens they’ve launched — including fees, ATH market caps, and other key metrics. This information is presented in a clean, easy-to-read format, allowing you to quickly assess a developer’s track record and reliability before entering a trade.

In addition, you can build **developer white-lists and ban-lists**, attach personal notes, and use this data to make more informed and consistent trading decisions over time.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.swoop.fun/swoop-pro/about-swoop-pro.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.