> 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/markdown.md).

# Token Utility

<figure><img src="/files/6nx65r48tsY8pfC3KpO4" alt=""><figcaption></figcaption></figure>

### Token-Gated Features

Access to Lens is structured around token-based utility.

Holding the token unlocks features within the product, including:

* access to advanced alert systems
* enhanced wallet tracking capabilities
* deeper data and signal context
* priority access to new features and updates
* expanded limits and functionality

As the product evolves, additional features will be introduced and gated in a way that directly benefits holders.

***

### What Holding Unlocks

Holding Lens is designed to give users more than just access — it improves how effectively they can use the product.

This can include:

* stronger filtering and signal control
* access to higher-quality or more refined alerts
* deeper insight into wallet behaviour and performance
* early access to new tools and improvements
* a more complete version of the LENS system

The aim is to create a clear difference between basic usage and full access.

***

### Why It Matters

Most tokens promise utility without delivering anything meaningful.

Lens is built differently.

The token is tied directly to a working product, where access and capability scale with ownership.

This creates alignment between:

* users who actively use the product
* holders who support its growth
* and the long-term development of the system

If the product improves, the value of holding becomes clearer.\
If the signals are useful, the demand becomes natural.

No forced mechanics.\
No artificial hype.

Just a product where **utility and ownership are connected.**

{% hint style="info" %}
If you have multiple files, GitBook makes it easy to import full repositories too — allowing you to keep your GitBook content in sync.
{% 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/get-started/markdown.md?ask=<question>&goal=<endgoal>
```

`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.
