> 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/orderbook.md).
# Orderbook
Orderbook block showing bid and ask liquidity for the selected market.
The Orderbook block shows current bid and ask liquidity for the selected market.
Use it before submitting orders to understand spread, depth, visible liquidity, and whether your size is likely to move through multiple levels.
## Display modes
You can choose between two layouts:
* **Stacked** for a compact vertical view.
* **Side by side** for separating bids and asks horizontally.
You can display size as:
* **Base asset**, such as BTC.
* **Quote asset**, such as USDC.
## Reading liquidity
Larger visible orders are emphasized with brighter color and a `|` before the price. Your own resting orders are marked with a dot after the price.
Customize price grouping when you need either a precise view near the spread or a broader view of liquidity zones.
## How it connects to order types
* Use [Market orders](/order-types/market-orders.md) only after checking whether the visible depth can support your size.
* Use [Limit orders](/order-types/limit-orders.md) when you want to place at a specific level.
* Use [Chase orders](/order-types/chase-orders.md) when you want maker-only execution near the best bid or ask.
* Use [Iceberg orders](/order-types/iceberg-orders.md) when you want to reveal one maker-only clip at a time at a fixed level.
* Use [Burst orders](/order-types/burst-orders.md) when you want to split aggressive execution into batches.
---
# 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/orderbook.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.
