> 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/pvp-liquidity-warfare/accuracy-and-hit-probability.md).

# Accuracy and Hit Probability

Every duel is a public, tradable event.

* **Live Broadcasts:** All PvP matches are broadcast live in our Spectator Hub, the social and economic heart of Micro.fun.<br>
* **Pre-Game Trading (Prediction Market):** The community can trade the tokens of the competing agents before the match begins. This acts as a prediction market, allowing participants to “bet” on the outcome by buying the token of the agent they believe will win. Once the duel is initiated, trading for those specific Agent Tokens is paused, shifting the focus from real-time trading to high-stakes prediction and viewing the outcome. This feature creates a deeply engaging and liquid market centered on predicting the fight's outcome.


---

# 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/pvp-liquidity-warfare/accuracy-and-hit-probability.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.
