> For the complete documentation index, see [llms.txt](https://robindog.gitbook.io/robindog-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://robindog.gitbook.io/robindog-docs/11-trading-and-liquidity.md).

# 11 Trading and liquidity

RobinDog prediction markets are intended to use fully collateralized outcome shares. Before opening a position, users can review the current market price, implied probability, outcome shares received, estimated slippage, market depth, and resolution rules.

During the protocol's early stages, different markets may use different mechanisms based on liquidity conditions:

* AMMs for continuous baseline quotes.
* Prize pools for short-duration Battlegrounds.
* Order books for deeper professional markets.
* Requests for quote for larger or specialized combo positions.

RobinDog will not open an excessive number of low-quality branches at once. Not every Story Tree node needs to become a tradable market immediately.

Priority nodes should have a clear resolution source, sufficient user interest, a reasonable settlement period, available initial liquidity, and an explicit connection to the active story.


---

# 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://robindog.gitbook.io/robindog-docs/11-trading-and-liquidity.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.