> For the complete documentation index, see [llms.txt](https://docs.fliq.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fliq.one/trading-concepts/order-books.md).
# Order Books
As we have already seen, placing market orders is the easiest way to enter/exit the desired markets but this convenience comes at a price. You buy/sell at the price offered by the market, which might not be suitable to you. \
If you believe, there is 80% chance of success in an event, you would not want to buy Yes shares at more than 80c per share.\
That's where Limit orders come in, which give you the flexibility to specify the price at which you want to buy/sell.
Order book is aggregation of these limit orders at each price level, which looks like the one shown below.
It shows that the best price someone is willing to pay for buying Yes shares is 49.4c (best bid) and the best price someone is willing to sell at is 50.3c (best ask), which has a gap of 90c. This difference between best bid and best ask is known as spread. As more and more people trade in a market, spread tends to reduce and vice versa.
---
# 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.fliq.one/trading-concepts/order-books.md?ask=&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.
