> 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/getting-started/how-you-can-profit.md).

# How you can profit?

You profit when your chosen outcome is correct at settlement at resolution.

#### Alice’s example

Alice thinks BTC will move up short-term.

* Market: “BTC 15-min close: Higher or Lower?”
* Alice chooses: Higher
* Stake: 20 USDT
* If BTC closes higher at expiry → Alice wins and is paid automatically.

#### Ben’s example

Ben thinks BTC will cool down and retrace.

* Ben chooses: Lower
* Stake: 20 USDT
* If BTC closes lower (or matches the market’s exact tie rule) → Ben wins.

{% hint style="info" %}
Some markets define “equal” as Lower, some treat it as a refund. The market’s **Rules section** is the final resolution.
{% endhint %}

***

### How 0Y Resolves Markets

0Y resolves outcomes using the market’s listed resolution method, typically including:

* Binance live feed API
* Chainlink Data Streams
* other third-party sources when needed

Resolution is based on:

* the exact timestamp / time window defined in the market rules
* the market’s defined instrument (e.g., BTC/USDT spot vs perpetual — must be specified)

#### If data is unclear: Refund policy

If there is a dispute due to data quality issues (missing, inconsistent, or unreliable resolution data), 0Y will:

> ✅ Refund all traders for that specific market.

This is designed to protect users and maintain trust when external data fails.


---

# 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/getting-started/how-you-can-profit.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.