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