> For the complete documentation index, see [llms.txt](https://docs.deep3.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deep3.ai/the-business/our-dapps/hedera-signals.md).
# Hedera Signals
Hedera Signals watches trading on the Hedera network and shows you which tokens are under the most buying or selling pressure, what eight price-movement models think will happen to them next, and whether those calls came true.
It also includes the **Wallet Cloud**, an interactive 3D map of 65,162 Hedera accounts grouped by how they behave.
### What you can do
* **See where the money is moving.** The Flow Leaderboard ranks tokens by net buying or selling pressure.
* **Read the models' calls.** Trade Signals lists every open prediction, such as "Up 20% within 4h" on a given token.
* **Check the track record.** Signal History and each token's Backtest panel check past calls against real minute-by-minute prices.
* **Explore the network.** The Wallet Cloud lets you fly through clusters of accounts and look any account up by its id.
### Before you start
Hedera Signals is a **prototype**. It is read-only: there is no wallet to connect, nothing to sign, and no way to place a trade from the app.
The app can run in several **data modes**, and some of them show predictions that no model fired at its normal cutoff. A coloured badge in the top right of every page tells you which mode you are in.
{% hint style="info" %}
Nothing in Hedera Signals is investment advice. See our Terms and Privacy.
{% endhint %}
---
# 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://docs.deep3.ai/the-business/our-dapps/hedera-signals.md?ask=&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.
