> For the complete documentation index, see [llms.txt](https://docs.0y.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.0y.world/zh-tw/jiao-yi/understanding-your-trade.md).

# 讀懂你的交易

每個交易頁面都應該一目瞭然。以下是各個字段的含義：

* 市場問題：這個市場衡量的是什麼
* 到期時間：什麼時候結算
* 規則：什麼算 YES/NO，以及數據來源
* 你的方向：YES/NO 或看漲/看跌
* 投注金額：你承擔風險的金額
* 賠付預覽：獲勝時你將獲得的金額

{% hint style="info" %}
“規則”部分是最終依據。
{% endhint %}

***

#### Ben 的例子

Ben 閱讀規則時注意到：“持平算作看跌。”

現在他清楚地知道，如果 BTC 收盤價與參考價相同會發生什麼。


---

# 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.0y.world/zh-tw/jiao-yi/understanding-your-trade.md?ask=<question>&goal=<user_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.