> 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-match.md).

# HELLO Match

### Find the Voices That Fit

HELLO Match is the AI KOL matching product of Hello.Fun.

Finding attention is one thing.

Finding the right people to talk about a project is another.

HELLO Match is designed to analyze what a project is about and help identify KOLs whose audience, content and positioning may be a better fit for that project.

The goal is not simply reach.

It is compatibility.

### Understand the Project First

Before finding a match, HELLO Match needs to understand what it is matching.

The system is designed to analyze information around the project, including areas such as:

* Project narrative
* Category
* Positioning
* Target audience
* Available project information

This creates a project profile that can be used when searching for relevant KOLs.

```mermaid
flowchart LR
    A["Project"] --> B["Narrative"]
    A --> C["Category"]
    A --> D["Positioning"]
    A --> E["Audience"]
    B --> F["HELLO Match"]
    C --> F
    D --> F
    E --> F
```

### Find Relevant KOLs

HELLO Match is designed to compare the project with available information around KOLs.

Rather than treating every KOL as equally relevant, Match looks for alignment between the project and the voices that may suit it.

```mermaid
flowchart LR
    A["Project Profile"] --> C["HELLO Match"]
    B["KOL Profiles"] --> C
    C --> D["Relevant Matches"]
```

This helps narrow a much larger KOL landscape into more relevant possibilities.

### Compatibility Scoring

HELLO Match is designed to provide compatibility scoring around potential matches.

A higher compatibility score represents stronger identified alignment between the project and the KOL based on the information available to Match.

The score is designed to help projects compare potential matches more easily.

It does not guarantee that a KOL will work with a project or that a collaboration will produce a particular result.

### More Than Follower Count

A large audience does not automatically make someone the right voice for every project.

A smaller KOL whose audience and content strongly align with a project may sometimes be more relevant than a much larger account with little connection to its narrative.

HELLO Match is designed around that idea.

```mermaid
flowchart TD
    A["Potential KOL"] --> B["Audience Fit"]
    A --> C["Content Fit"]
    A --> D["Project Relevance"]
    B --> E["Compatibility"]
    C --> E
    D --> E
```

**Reach matters. Relevance matters too.**

### From Project to Match

The HELLO Match journey is designed to make KOL discovery more focused.

```mermaid
flowchart LR
    A["Understand Project"] --> B["Analyze KOLs"]
    B --> C["Measure Compatibility"]
    C --> D["Recommend Matches"]
    D --> E["Creator Reviews"]
```

AI helps narrow the search.

The creator decides what to do with the result.

### Match and Project Growth

Launching a token creates a market.

Growing awareness around that market is a different challenge.

HELLO Match extends HELLO Intelligence into project growth by helping creators identify voices that may fit what they are building.

This connects the intelligence around the token with the people who may help bring it to the right audience.

### Match and Say Hello

Say Hello is designed to build a wider intelligence picture around a token.

That broader project context can help make matching more meaningful by giving HELLO Match more information about what the project represents.

```mermaid
flowchart LR
    A["Project World"] --> B["HELLO Match"]
    B --> C["KOL Compatibility"]
    C --> D["Potential Matches"]
```

As the intelligence ecosystem expands, project understanding and project discovery can work together.

### AI Generated Recommendations

HELLO Match recommendations and compatibility scores are AI generated outputs based on the information available to the system.

They should not be interpreted as guarantees of endorsement, availability, campaign performance or project success.

Creators remain responsible for reviewing potential matches and deciding who they want to approach or work with.

### Part of HELLO Intelligence

HELLO Match is the **CONNECT** layer of HELLO Intelligence.

**CONNECT → HELLO Match → Find the voices that fit.**

It brings AI powered matching into the growth side of the Hello.Fun ecosystem.

### Availability

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

**Do not just find reach. Find the match.**


---

# 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-match.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.
