> For the complete documentation index, see [llms.txt](https://hypes-organization.gitbook.io/hypesphere-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hypes-organization.gitbook.io/hypesphere-whitepaper/hypesphere.md).

# HypeSphere

**Visualize the Hype. Decode the Memes.**

**HypeSphere** is the first meme token analytics and discovery suite on **HyperEVM**, combining real-time **sphere map visualizations**, automated Telegram bots, and alpha-focused tools—powered by the $SPHERE token.

> "In a world full of noise, we map the signal."

***

### 🔥 TL;DR

* 🗺️ **Sphere Maps**: Live visual mapping of meme token launches.
* 🤖 **Telegram Bots**: Buy alerts, token detectors, sniper (soon).
* 🚀 **Built for HyperEVM**: Fast, cheap, and community-led.
* 🧠 **Powered by $SPHERE**: The native token of hype tracking.
* 🔧 **Indie-built** by [@ZenzoDegen](https://x.com/ZenzoDegen)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hypes-organization.gitbook.io/hypesphere-whitepaper/hypesphere.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.