> 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/faq/odds-payouts-and-fees.md).

# Odds, Payouts, and Fees

#### How are odds determined?

Odds are live quotes provided by 0Y, updating based on market movement, time remaining, volatility, and platform risk controls.

#### Do odds represent probability?

Odds generally reflect “how likely the outcome is” and your payout if you win, but 0Y is the platform (not an orderbook), so odds are based on LMSR pricing engine quote rather than a P2P market price.

#### Where can I see my payout before confirming?

Every trade screen shows a payout preview before you confirm.

#### Are there trading fees?

If fees apply, they will be displayed before confirmation. Deposits/withdrawals may include network gas fees. Please check [Pricing & Fees](https://github.com/0ymarkets/0y-docs/tree/main/faq/pricing-and-fees.md)for more infomation.


---

# 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/faq/odds-payouts-and-fees.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.