> 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/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/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.