> 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/tracking-your-positions.md).

# 追蹤你的持倉

#### 在哪裡查看持倉

前往：

* “我的持倉”（或儀表盤），查看所有未結算和已結算的交易。

你通常會看到：

* 市場名稱
* 選擇的方向
* 投注金額
* 到期時間
* 狀態（進行中 / 已結算 / 已退款）
* 結算後的賠付結果

{% hint style="info" %}
如果你的持倉很多，可以先篩選“進行中”，以免錯過即將到期的市場。
{% endhint %}

***

#### Alice 的習慣

Alice 每天查看一次“我的持倉”：

* 進行中 → 看看哪些倉位仍然有效
* 已結算 → 回顧哪些判斷是對的
* 已退款 → 瞭解少見的數據質量問題


---

# 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/tracking-your-positions.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.