> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/investor-intel/wallet-watch.md).

# Wallet Watch

Wallet Watch turns any public wallet address into a readable story. Paste an address and get a clear, easy-to-understand AI summary of what that wallet actually does, grounded in its real transaction history.

### What you'll get

* **Clear summary** - what the wallet holds, how it behaves, and what it has been doing lately, written from its transaction history rather than guessed
* **Entity resolution** - known addresses are identified where possible (exchanges, protocols, well-known wallets), so a transfer reads as "moved funds to an exchange" instead of a raw address
* **Activity context** - patterns that matter: accumulation, distribution, rotation between assets, interaction with protocols

### Tracking wallets

Add wallets you want to keep watching: whales, funds, smart-money addresses, project treasuries, or any address whose moves you care about.

* Tracked wallets can feed the **wallet activity** trigger in [Alerts](/thecontentforge-docs/investor-intel/alerts.md), so you hear about significant moves without checking manually
* The number of wallets you can track depends on your plan, from 1 on trial up to 50 on Elite. See [Pricing](/thecontentforge-docs/reference/pricing.md).

### How to use it

1. Paste any address to get an instant AI read on it
2. Track the wallets worth following over time
3. Set a wallet activity alert on the ones where timing matters
4. When a tracked wallet makes a notable move, read the summary before reacting: a transfer to an exchange is a data point, not a verdict

### Things to keep in mind

* Everything here reads **public on-chain data**. Wallet Watch never needs keys and never touches funds, yours or anyone else's.
* Smart money is not always right, and one wallet's exit is not a market call. Treat wallet activity as one signal to weigh, not an instruction to copy.
* Entity labels are best-effort identifications and can be incomplete

### Related

* [Portfolio](/thecontentforge-docs/investor-intel/portfolio.md) - the same read-only approach, for your own wallets
* [Alerts](/thecontentforge-docs/investor-intel/alerts.md) - the wallet activity trigger
* [Explain This](/thecontentforge-docs/investor-intel/explain-this.md) - ask follow-up questions about what a wallet did


---

# 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://thecontentforge.gitbook.io/thecontentforge-docs/investor-intel/wallet-watch.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.
