> For the complete documentation index, see [llms.txt](https://lens-project.gitbook.io/lens-project-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lens-project.gitbook.io/lens-project-docs/documentation/introduction/quickstart.md).
# Core Features
### Smart Wallet Alerts
Track selected wallets and receive alerts when they buy into tokens.
Lens is focused on helping users detect potentially meaningful entries early, with enough context to decide what matters and what doesn’t.
***
### Wallet Tracking
Users can add and manage wallets they want to follow.
This creates a personalised tracking experience instead of forcing everyone into the same feed.
You track what matters to you.
***
### Enriched Alert Data
Every alert is built to carry more than just a wallet buy.
Depending on the alert, Lens can include:
* token name and ticker
* contract address
* buy size
* market cap
* liquidity
* wallet behaviour profile
* wallet performance context
* signal strength / score
* reasoning behind the score
The aim is simple: give context fast.
***
### Wallet Behaviour Analysis
Lens doesn’t just show wallet activity.
It also helps classify behaviour.
Examples include wallets that rotate quickly, scale positions, or behave in ways that can help users better understand the kind of signal they’re seeing.
This adds another layer of meaning beyond just “wallet bought token.”
***
### Performance Milestone Tracking
Lens can track how alerted tokens perform after detection and surface milestone hits such as:
* 2x
* 3x
* 5x
* 10x
This helps users measure outcomes, review alert quality, and see real examples of performance over time.
Not every alert is a buy.\
But every alert can become data.
***
### Telegram Native Experience
Lens is built directly around Telegram usage.
That means:
* fast access
* clean menus
* easy tracking flows
* private interaction where needed
* no need to leave your normal workflow
The product is designed to feel lightweight, fast, and practical.
{% hint style="info" %}
Want to learn about writing content from scratch? Head to the [Basics](/lens-project-docs/documentation/get-started/editor.md) section to learn more.
{% endhint %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://lens-project.gitbook.io/lens-project-docs/documentation/introduction/quickstart.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.