> For the complete documentation index, see [llms.txt](https://docs.premia.blue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premia.blue/the-premia-protocol/options-on-premia/order-book-vs.-amm.md).

# Order-book vs. AMM

Most traditional markets and centralized exchanges utilize central-limit order books (CLOBs) to track user orders and match overlapping trades. Traders familiar with traditional option brokers and crypto option exchanges will be familiar with order books, in which a depth of liquidity is maintained for each price level on the bid (buy-side) and ask (sell-side) of the market price by market **makers**, while **takers** can fill trades by accepting existing orders on the book.

In the Premia v3, market makers can deposit liquidity into [**range orders**](/the-premia-protocol/concepts/lp-range-orders.md) in an on-chain pool within the user’s defined price range (AKA concentrated liquidity). Makers can place range orders on the **buy-side,** **sell-side,** or **both**, to determine how their liquidity can be used within the specified price range. Each market’s automated price is directly determined by the distribution of liquidity on the exchange, and the past trades in the market. As traders (takers) buy options from sell-side orders, the market price will be adjusted upwards, and as traders sell options to buy-side orders, the market price will be adjusted downwards. This enables both traders and market makers to maintain short and / or long positions on the exchange as either makers or takers.

Each time a trade occurs, every overlapping range order will split fees and exposure for the trade pro-rata, determined by the amount of liquidity in each range order vs. the total amount of overlapping liquidity. The price each user pays or receives for an option is the quote price, determined by the AMM, plus a [**taker fee**](/the-premia-protocol/concepts/fees.md)**.** The taker fee is split between makers and the protocol **stakeholders** ([vePREMIA](broken://pages/uTRjNgDDxzIhDimjgDs2) holders and protocol treasury).

Additionally, market makers can place limit orders on the [v3 order book](/the-premia-protocol/concepts/orderbook-and-request-for-quote-rfq.md) (which lives on Arbitrum Nova). Users do not need to interact with Arbitrum Nova directly; the Premia Blue UI will relay these orders and cover gas for your convenience. These orders do not earn maker fees; however, they will still be quoted to users on the Premia Interface via resting Limit Order.

This duality enables Premia v3 users to benefit from both earning fees in automated range orders and trade or market-make in traditional order book fashion. Exchange traders will also benefit from increased liquidity and better option pricing.


---

# 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.premia.blue/the-premia-protocol/options-on-premia/order-book-vs.-amm.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.
