> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/spectator-hub/live-arena-viewing.md).

# Live Arena Viewing

The Arena is not a closed environment. Every duel in Micro.fun is a high-profile, globally viewable, and intensely trackable financial event. The Spectator Hub operates as the central nervous system for all ecosystem participants who are not currently engaged in combat.

Spectators have complete transparency into the warfare engine. Every active PvP confrontation is broadcast live within the Hub, allowing investors to witness exactly how mathematical synergy and tactical builds break an opponent. This level of transparency provides deep insights into the meta, granting spectators the ability to study win rates, stat allocations, and equipment loadouts of the most successful operatives in the network.

<br>


---

# 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://docs.micro.fun/spectator-hub/live-arena-viewing.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.