> For the complete documentation index, see [llms.txt](https://bread-5.gitbook.io/bread/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bread-5.gitbook.io/bread/predict-terminal/how-to-read-market-page.md).

# How to read a market page

### Page structure

A market page consists of these key blocks:

* **Headline** — the question (English original)
* **YES / NO price** — current probability (cents per share)
* **Price chart** — historical probability movement with adjustable timeframes
* **Order book** — liquidity on both sides
* **Trade panel** — Buy YES / Buy NO buttons + order parameters
* **Metadata** — resolution date, source of truth, volume, liquidity
* **Recent trades** — real-time execution stream

<figure><img src="/files/tUrjLb8QzDp8fo3sX1o2" alt=""><figcaption></figcaption></figure>

### YES / NO price

Share price = probability of the outcome. YES + NO always equals 1 dollar.

* **YES 30¢** — the market values the event at 30%
* **NO 70¢** — the opposite side of the same event
* Prices move inversely — YES up = NO down

### Order book

The order book shows current liquidity depth:

* **Bids** — buy orders for YES / NO at different price levels
* **Asks** — sell orders for YES / NO at different price levels
* **Spread** — difference between the best bid and the best ask

**A thin order book** = slippage risk. If you place a market order for 1000 dollars but only 200 sits at the nearest levels — the remaining 800 will execute deeper and the average price will be worse.

### Chart

* **Line** — historical YES price (or NO — toggleable)
* **Volume under the chart** — trading volume per period

### Resolution metadata

The section on market closing conditions — read carefully **before** opening a position:

* **Resolution date** — when the event closes
* **Resolution source** — source of truth
* **Resolution criteria** — exact conditions for what counts as YES vs NO

**An important nuance:** "Will BTC close above 100K on July 31?" — resolution depends on:

* The specific price source (Binance, CoinGecko, Coinbase)
* The specific time (UTC midnight or local close)
* What counts as "close" (last trade, weighted average, settlement)

These details are spelled out explicitly in Resolution criteria. Don't open a position before reading them.

### Recent trades

The execution stream shows:

* Trade time
* Size
* Side (YES / NO)
* Execution price
* Wallet address (if public)

Useful for assessing activity — a market with thin, rare trades is riskier than one with constant flow.

### How to use the page to make a decision

**Before opening a position:**

1. Read Resolution criteria — the exact definition of the outcome
2. Look at the chart — what happened to the price before you walked in
3. Check the order book — is there enough liquidity for your size
4. Check the resolution date — how long to wait for payout
5. Watch recent trades — is the market live or almost dead

***


---

# 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://bread-5.gitbook.io/bread/predict-terminal/how-to-read-market-page.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.