> 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/images-and-media.md).

# Product Vision

<figure><img src="/files/6nx65r48tsY8pfC3KpO4" alt=""><figcaption><p>Add alt text and captions to your images</p></figcaption></figure>

### Where Lens Is Going

The direction is simple:

More signal.\
Less noise.\
Better decisions.

Lens will continue improving across three core areas:

* **Speed** - faster detection, faster delivery, lower latency
* **Clarity** - cleaner alerts, better formatting, easier interpretation
* **Quality** - stronger filtering, better scoring, more reliable signals

The goal is not to push more alerts - it’s to make each alert more valuable.

***

### Expansion

As the product matures, Lens will expand beyond basic tracking into a more complete on-chain toolkit.

This includes:

* more advanced wallet behaviour analysis
* smarter signal filtering and customisation
* deeper performance tracking and analytics
* improved scoring systems based on real outcomes
* additional tools that help users act, not just observe

All expansions are built around the same principle:

**keep it simple, keep it fast, keep it useful.**

***

### Long-Term Mindset

Lens is not being built for a single cycle or short-term attention.

The focus is on:

* consistent product improvements
* reliable performance
* long-term user trust
* meaningful utility tied to the product

Markets change, narratives shift - but tools that provide real value continue to be used.

That is the standard Lens is being built towards.


---

# 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/images-and-media.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.