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

# AI Wallet Tags

AI-inferred trader profiles for wallets without a manual label, surfaced inline across every supported platform.

For wallets that don't have a manual label, Frontrun generates a short trader profile from on-chain behavior. AI tags appear inline alongside manual labels across every supported platform.

### What's tagged

* Trading style (sniper, swing, scalper, holder)
* Notable positions and historical winners
* KOL identity when a wallet is publicly linked to an X handle
* Risk patterns (rugs, bundles, suspicious flow)

### Reporting and moderation

Every AI tag in the sidepanel includes a Report button. Reports are reviewed by Frontrun moderators.

### Availability

AI Wallet Tags are available on Silver and Gold. Free users see a paywalled preview.


---

# 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.frontrun.pro/features/ai-wallet-tags.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.