> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/terminal-sections/spectate-mode.md).

# Spectate mode

<div align="left"><figure><img src="https://1571380119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwUo1o7rINODRyyILQE1%2Fuploads%2F5RmIe0RFbAS2kCfOBdOg%2Fimage.png?alt=media&amp;token=a3f30425-df8e-4e76-ae0b-60ef359755df" alt="Spectate mode view for inspecting a public Hyperliquid address read-only."><figcaption><p>Spectate mode view for inspecting a public Hyperliquid address read-only.</p></figcaption></figure></div>

Spectate mode lets you view Terminal context for any public Hyperliquid address.

Use it to inspect another address, follow a public trader, or review account activity without connecting as that wallet.

Spectate mode is read-only. You can view public account context, but you cannot submit orders, manage positions, or change wallet-specific settings for the address.

For details on how read-only viewing differs from a connected trading wallet, read [Security and wallet safety](/getting-started/security-and-wallet-safety.md).

Related pages: [Whales](/features/whale-alerts-and-large-trades.md), [Private mode](/terminal-sections/private-mode.md), [Positions](/terminal-sections/positions.md).


---

# 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.proliquid.xyz/terminal-sections/spectate-mode.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.