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

# HELLO Paws

### Catch Token Worthy Moments

HELLO Paws is the autonomous meme opportunity agent of HELLO Intelligence.

Internet culture moves fast.

A post, reply, phrase, image or unexpected moment can suddenly capture attention and create an opportunity for a meme token.

Paws is designed to watch for those moments.

Instead of requiring someone to constantly monitor X and manually react to every opportunity, Paws can follow selected accounts, identify potentially token worthy moments and act according to rules defined by the user.

### Follow the Accounts That Matter

Users can select the X accounts they want Paws to watch.

These could include accounts connected to communities, creators, personalities or other sources where relevant moments may emerge.

Paws continuously looks at activity from the selected sources for potential meme opportunities.

```mermaid
flowchart LR
    A["Selected X Accounts"] --> B["HELLO Paws"]
    B --> C["Watch Activity"]
    C --> D["Detect Potential Moment"]
```

The user decides where Paws should look.

Paws handles the watching.

### Spot the Moment

Not every post needs a token.

Paws is designed to analyze activity and identify moments that may have the characteristics of a meme or token opportunity.

The goal is to shorten the time between a moment appearing and a potential token entering the market.

```mermaid
flowchart LR
    A["New Activity"] --> B["Paws Analyzes"]
    B --> C{"Token Worthy?"}
    C -->|"No"| D["Keep Watching"]
    C -->|"Yes"| E["Apply User Rules"]
```

Paws keeps looking while the internet keeps moving.

### Set Your Rules

Autonomy does not mean acting without boundaries.

Users define the rules that determine how Paws should operate.

Those rules establish the conditions under which the agent is allowed to move from detecting an opportunity toward creating a launch.

This gives the user control over the framework while allowing Paws to operate within it.

### Fund the Wallet

Automated launching requires a wallet with the funds needed to execute permitted actions.

The user can prepare a funded wallet for Paws to operate with according to the configured rules.

This gives the agent the resources required to act when a qualifying opportunity is identified.

Users remain responsible for deciding how the wallet is funded and what operating rules are given to Paws.

### From Moment to Market

When Paws identifies an opportunity that satisfies the user's configured rules, it is designed to move beyond simply sending an alert.

It can prepare and execute a matching token launch through Hello.Fun using the configured wallet and rules.

```mermaid
flowchart TD
    A["Watch Selected Accounts"] --> B["Detect Opportunity"]
    B --> C["Analyze Moment"]
    C --> D{"Matches User Rules?"}
    D -->|"No"| E["Continue Watching"]
    D -->|"Yes"| F["Prepare Token"]
    F --> G["Execute Launch"]
    G --> H["Hello.Fun Market"]
```

This is what makes Paws different from a standard monitoring tool.

It is designed not only to spot opportunities, but to act on qualifying ones.

### Paws and HELLO Pilot

HELLO Pilot and HELLO Paws solve different problems.

**HELLO Pilot** helps a creator intentionally prepare a token launch with AI assistance.

**HELLO Paws** watches for emerging opportunities and can act autonomously when a moment satisfies the user's rules.

```mermaid
flowchart LR
    A["Creator Has an Idea"] --> B["HELLO Pilot"]
    B --> C["Assisted Launch"]

    D["A Moment Happens"] --> E["HELLO Paws"]
    E --> F["Autonomous Opportunity Launch"]
```

Pilot starts with the creator's idea.

Paws starts with the opportunity.

Both can ultimately lead into the Hello.Fun market.

### Built for Speed

Meme opportunities can be highly time sensitive.

By the time a moment is noticed, discussed, prepared and manually launched, the conversation around it may already have moved on.

Paws is designed to reduce that delay.

**Watch → Spot → Match → Launch**

The objective is not simply automation.

It is being ready when the moment happens.

### Part of HELLO Intelligence

HELLO Paws is the **SPOT** layer of HELLO Intelligence.

**SPOT → HELLO Paws → Catch token worthy moments.**

It connects real time cultural discovery with the Hello.Fun launch ecosystem.

### Availability

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

**The internet moves fast. Paws moves with it.**&#x20;


---

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