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

# The Scout

### Follow Activity While You Are Away

The Scout is the AI Activity Radar of Hello.Fun.

Tokens and projects can move quickly.

Market activity changes, communities react, milestones happen and new signals can appear while users are away.

The Scout is designed to keep watch.

It follows activity around a project and helps surface what may be worth knowing when a user returns.

### Always Watching the Project

The Scout is designed to monitor activity surrounding a project over time.

Instead of requiring users to continuously follow every available signal themselves, Scout can help identify meaningful developments across the information available to it.

```mermaid
flowchart LR
    A["Project Activity"] --> E["The Scout"]
    B["Market Activity"] --> E
    C["Engagement"] --> E
    D["Milestones"] --> E
    E --> F["Activity Radar"]
```

The goal is not to show more noise.

It is to help surface activity that deserves attention.

### What Scout Looks For

The Scout is designed to follow signals across areas such as:

* Project activity
* Market activity
* Engagement
* Milestones
* Unusual movement
* Other meaningful changes around the project

Different signals can matter for different reasons.

Scout brings them into an activity monitoring layer around the token.

### See What Happened While You Were Away

A user should not need to watch a token every minute to understand what changed.

The Scout is designed to make returning to a project easier.

```mermaid
flowchart LR
    A["User Leaves"] --> B["The Scout Watches"]
    B --> C["Activity Happens"]
    C --> D["Scout Identifies Signals"]
    D --> E["User Returns"]
    E --> F["Review What Happened"]
```

Instead of starting from the beginning, users can get a clearer view of meaningful activity that occurred while they were away.

### Detecting Unusual Activity

Some changes deserve more attention than normal day to day movement.

The Scout is designed to identify unusual activity within the information it monitors and surface it for closer review.

An unusual signal does not automatically mean something positive or negative has happened.

It means the activity may be worth looking at.

### Milestones and Project Activity

Not everything important happens on a chart.

Projects can reach milestones, increase engagement or generate activity outside a simple price movement.

The Scout is designed to help bring these developments into the wider intelligence picture around a token.

This gives users another way to follow the project beyond watching market figures alone.

### Scout and HELLO Lens

The Scout and HELLO Lens look at tokens from different angles.

**HELLO Lens** analyzes available information and generates scores, insights and risk signals.

**The Scout** watches activity over time and helps surface meaningful changes.

```mermaid
flowchart LR
    A["Token and Project"] --> B["HELLO Lens"]
    A --> C["The Scout"]
    B --> D["Analyze"]
    C --> E["Watch"]
```

Lens asks what the available information may tell you.

Scout asks what has changed.

### Scout and HELLO Mate

The Scout can identify activity worth noticing.

HELLO Mate provides a conversational way to understand information around the project.

Together, these products are designed to make it easier to return to a token, see what happened and explore the information further.

```mermaid
flowchart LR
    A["The Scout"] --> B["Activity and Signals"]
    B --> C["HELLO Mate"]
    C --> D["Ask and Understand"]
```

### Scout and Say Hello

Say Hello is designed to bring the wider world around a token together.

The Scout can provide the activity layer within that experience, helping users see important developments alongside market information, project information and other HELLO Intelligence products.

This means a token can be understood not only by what it is now, but also by what has been happening around it.

### Intelligence, Not a Guarantee

The Scout surfaces activity and signals based on the information available to it.

A surfaced signal should not automatically be interpreted as proof of project quality, risk or future market direction.

It is designed to help users know what may deserve their attention.

The final interpretation remains with the user.

### Part of HELLO Intelligence

The Scout is the **WATCH** layer of HELLO Intelligence.

**WATCH → The Scout → Follow activity while you are away.**

While the market keeps moving, Scout keeps watching.

### Availability

The Scout is coming soon and will be introduced as HELLO Intelligence expands.

**Step away. Scout stays on watch.**


---

# 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/the-scout.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.
