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

# Say Hello

### See the Whole Token in One Place

A token is more than a ticker.

More than a chart.

More than a market cap.

Around every token is a wider world of market activity, holders, transactions, liquidity, project information, social activity, wallets, conversations and signals.

**Say Hello** is designed to bring that world together.

It is the token, project and market intelligence experience of Hello.Fun.

**KNOW IT.**

### Not Just a Token Page

Traditional token pages often focus on a familiar set of market figures.

Price.

Market cap.

Volume.

Liquidity.

Charts.

Those numbers matter, but they do not tell the entire story.

Say Hello is designed to connect market information with the wider project and intelligence layer surrounding the token.

```mermaid
flowchart TD
    A["Token"] --> B["Market"]
    A --> C["Project"]
    A --> D["Community"]
    A --> E["Activity"]
    A --> F["Wallets"]
    A --> G["HELLO Intelligence"]

    B --> H["Say Hello"]
    C --> H
    D --> H
    E --> H
    F --> H
    G --> H
```

Instead of moving between different places to understand a token, Say Hello is designed to bring more of that picture into one experience.

### The Market

Say Hello can bring together core market information around the token.

This can include:

* Price
* Market capitalization
* Trading volume
* Liquidity
* Holders
* Transactions
* Charts
* Pair information
* Market stage

The underlying market information remains connected to the available market and blockchain data.

### The Project

Numbers explain the market.

They do not necessarily explain the project.

Say Hello is designed to place project context alongside market information.

This can include:

* Project name
* Token symbol
* Description
* Token image
* Website
* X profile
* Telegram
* Available project information

Users can move from seeing how a token is trading to understanding what the project represents.

### The Activity

Tokens continue changing after they launch.

Trading happens.

Communities react.

Projects develop.

New signals appear.

Say Hello is designed to bring relevant activity into the wider token experience rather than presenting the token as a static profile.

This creates a living view of what is happening around the project.

### The Social Layer

Market activity is only one part of a token's world.

Social activity can provide additional context around how a project is being discussed and followed.

Say Hello is designed to bring available social context closer to the market and project information surrounding the token.

```mermaid
flowchart LR
    A["Market"] --> D["Say Hello"]
    B["Project"] --> D
    C["Social Context"] --> D
    D --> E["Wider Token View"]
```

This helps connect what is happening onchain with the wider conversation around the project.

### Wallet Activity

Wallet activity can provide another perspective on what is happening around a token.

Say Hello is designed to surface relevant wallet information and signals alongside the wider project experience.

This can include notable wallet activity and **FOMO wallets** where supported by the experience.

Wallet signals provide additional context.

They should not by themselves be treated as a reason to buy or sell a token.

### HELLO Lens Inside the Experience

HELLO Lens brings token analysis into Say Hello.

Lens is designed to analyze available project and market information and generate:

* Scores
* Insights
* Risk signals

```mermaid
flowchart LR
    A["Token Information"] --> B["HELLO Lens"]
    B --> C["Scores"]
    B --> D["Insights"]
    B --> E["Risk Signals"]
    C --> F["Say Hello"]
    D --> F
    E --> F
```

This gives users an intelligence layer alongside the underlying information.

### Ask HELLO Mate

Say Hello is also designed to become conversational through HELLO Mate.

Instead of only navigating the information presented around the token, users can ask questions about the project and the information available to Mate.

```mermaid
flowchart LR
    A["Say Hello"] --> B["HELLO Mate"]
    C["User Question"] --> B
    B --> D["AI Generated Answer"]
```

The token becomes something users can explore through both information and conversation.

### See What The Scout Found

The Scout adds the activity radar.

While users are away, Scout is designed to follow meaningful activity around the project.

When users return, Scout can help surface developments, milestones, engagement and unusual movement that may deserve attention.

```mermaid
flowchart LR
    A["Project Activity"] --> B["The Scout"]
    B --> C["Meaningful Signals"]
    C --> D["Say Hello"]
```

Say Hello can therefore show not only what the token looks like now, but also what has been happening around it.

### One Token. Multiple Layers.

Say Hello is designed to connect information that would otherwise be viewed separately.

```mermaid
flowchart TD
    A["SAY HELLO"] --> B["Market Data"]
    A --> C["Project Information"]
    A --> D["Social Context"]
    A --> E["Wallet Activity"]
    A --> F["HELLO Lens"]
    A --> G["HELLO Mate"]
    A --> H["The Scout"]

    B --> I["The Token's Wider World"]
    C --> I
    D --> I
    E --> I
    F --> I
    G --> I
    H --> I
```

Each layer adds another piece of context.

Together, they create a more complete way to discover and understand a token.

### From Discovery to Understanding

Say Hello is designed to change what happens after someone discovers a token.

Instead of:

**Find → Check Price → Check Chart**

The experience becomes:

**Find → Explore → Analyze → Ask → Watch → Understand**

Discovery becomes deeper than finding what is moving.

It becomes understanding what you found.

### Intelligence Without Hiding the Data

HELLO Intelligence adds interpretation, summaries and signals around available information.

It does not make AI generated outputs equivalent to underlying market data.

Market figures, project information and available source data can be viewed alongside the intelligence generated from them.

Users can see the information and decide how they want to interpret it.

### Part of HELLO Intelligence

Say Hello is the **KNOW** layer of HELLO Intelligence.

**KNOW → Say Hello → See the whole token in one place.**

HELLO Lens analyzes.

HELLO Mate answers.

The Scout watches.

Say Hello brings the wider picture together.

### Availability

Say Hello is coming soon and will be introduced as HELLO Intelligence expands.

### KNOW IT.

**See the whole token in one place.**

**Not just a token page.**

**The token's entire world.**


---

# 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/say-hello.md?ask=<question>&goal=<user_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.
