> For the complete documentation index, see [llms.txt](https://hello-fun-1.gitbook.io/hello.fun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hello-fun-1.gitbook.io/hello.fun-docs/hello-intelligence/hello-lens.md). # HELLO Lens ### Read Tokens, Data and Market Signals HELLO Lens is the AI token intelligence and scoring system of Hello.Fun. Markets generate information constantly. Price moves. Volume changes. Liquidity shifts. Holders enter and leave. Transactions build a history around the token. At the same time, every project has its own identity, positioning and activity. HELLO Lens is designed to bring available information together and turn it into easier to understand intelligence. ### From Data to Intelligence Raw data tells users what is happening. Lens is designed to help users interpret that information. ```mermaid flowchart LR A["Project Information"] --> C["HELLO Lens"] B["Market Information"] --> C C --> D["Analysis"] D --> E["Scores"] D --> F["Insights"] D --> G["Risk Signals"] ``` Instead of requiring users to interpret every available data point independently, Lens provides another layer through which a token can be evaluated. ### Token Analysis HELLO Lens is designed to analyze available information surrounding a token and its project. This can include information from areas such as: * Project information * Market activity * Price * Volume * Liquidity * Holders * Transactions * Market history * Other available project and market signals Lens can process these inputs together rather than treating each figure in isolation. ### Lens Scores HELLO Lens can turn its analysis into scores that make different aspects of a token easier to assess. A score is an AI generated interpretation based on the information available to Lens. It is not an onchain fact. It is not a guarantee of project quality. It is not a prediction of future price or performance. The purpose of scoring is to make complex information easier to navigate and compare. ### Insights Numbers alone do not always explain what is happening. Lens is designed to generate insights that provide additional context around the information it analyzes. ```mermaid flowchart TD A["Available Information"] --> B["HELLO Lens"] B --> C["Identify Signals"] C --> D["Generate Insights"] D --> E["Present Context"] ``` These insights can help users notice patterns or information that may otherwise require reviewing multiple data points separately. ### Risk Signals HELLO Lens is also designed to surface risk signals. A risk signal highlights something that may deserve closer attention. It should not automatically be interpreted as proof that a project is unsafe. Likewise, the absence of a particular risk signal does not mean a token is risk free. Lens provides another layer of information for users to consider when doing their own evaluation. ### Market Data and Lens Intelligence Hello.Fun keeps the distinction between underlying market data and AI generated intelligence clear. **Market data** is derived from indexed market activity. **Lens intelligence** is generated by analyzing available information. ```mermaid flowchart TD A["Indexed Market Data"] --> B["Displayed Market Information"] A --> C["HELLO Lens"] D["Project Information"] --> C C --> E["AI Generated Intelligence"] ``` Users can therefore review the underlying information separately from the interpretation provided by Lens. ### A Different Way to Explore HELLO Lens is designed to become part of the wider discovery experience across Hello.Fun. Instead of discovering a token and seeing only its ticker, chart and market figures, users can also gain an intelligence layer around what they are looking at. **See the data. Read the signals. Understand more.** ### Lens and Say Hello HELLO Lens provides the analysis. Say Hello is designed to bring the wider world around a token together. Lens intelligence can become one part of that larger experience alongside market data, project information, social context, wallet activity and other available signals. ```mermaid flowchart LR A["Token"] --> B["HELLO Lens"] B --> C["Scores"] B --> D["Insights"] B --> E["Risk Signals"] C --> F["Say Hello"] D --> F E --> F ``` Lens helps analyze the token. Say Hello helps users see its wider world. ### Part of HELLO Intelligence HELLO Lens is the **ANALYZE** layer of HELLO Intelligence. **ANALYZE → HELLO Lens → Read tokens, data and market signals.** It sits between raw information and deeper understanding. ### Availability HELLO Lens is coming soon and will be introduced as HELLO Intelligence expands. **Look closer. See more.** --- # 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://hello-fun-1.gitbook.io/hello.fun-docs/hello-intelligence/hello-lens.md?ask=&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.