> 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/get-started/integrations.md).
# FAQ
### Is Lens token-gated?
Yes - Lens is designed with token-gated utility.
Holding the token unlocks access to features within the product, with additional functionality being introduced over time for holders.
The goal is to make holding directly connected to real usage.
***
### Is it beginner friendly?
Yes.
Lens is built to be simple to use, even for users with limited on-chain experience.
Alerts are structured clearly, with context included so users can understand what they’re seeing without needing complex tools or dashboards.
***
### What chains does Lens support?
Lens is currently focused on Solana.
This allows for faster detection, lower latency, and a more efficient tracking system.
Additional support may be explored over time, but the focus is on doing one chain properly first.
***
### How fast is detection?
Detection speed is a core focus of Lens.
Alerts are designed to be delivered as quickly as possible after a tracked wallet enters a position, often within seconds.
Speed will continue improving as infrastructure is refined.
***
### Do I need to track my own wallets?
No - Lens is built around personalised tracking, but it also provides a curated wallet list.
Users can choose to:
* track their own selected wallets
* or use a curated list of wallets sourced from top-performing on-chain data
This allows both flexibility and accessibility:
* advanced users can build their own tracking setup
* newer users can rely on proven wallets without needing to research
The goal is simple:\
**give users access to high-quality signals, without unnecessary friction.**
***
### Are all alerts buys?
No.
Not every alert is a guaranteed opportunity.
Lens is designed to surface activity and provide context - allowing users to make their own decisions based on the information provided.
***
### How is this different from other tools?
Lens focuses on:
* speed
* clarity
* simplicity
* real utility
It is built to deliver useful signals quickly inside Telegram, without unnecessary complexity.
---
# 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/get-started/integrations.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.