> 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/ru-men-zhi-nan/what-is-odds-and-payout.md).
# 什麼是賠率與賠付？
{% hint style="success" %}
賠率 = 市場當前對概率的判斷 + 賠付。
{% endhint %}
在 0Y 上，賠率會根據以下因素變化：
* 實時市場狀況（價格走勢、波動率、流動性、新聞）
* 為保持市場公平和可持續而設的風險控制
可以簡單這樣理解：
* 如果某一邊看起來*更可能*發生，它通常賠付*更少*。
* 如果某一邊看起來*更不可能*發生，它通常賠付*更多*。
#### 示例：BTC 15 分鐘收盤（看漲/看跌）
市場：“15 分鐘後 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/ru-men-zhi-nan/what-is-odds-and-payout.md?ask=&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.