> For the complete documentation index, see [llms.txt](https://docs.probly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.probly.com/resources/refund-policy.md).

# Refund Policy

Probly may refund users at its discretion. Refunds are typically issued when a market cannot resolve as intended or is affected by a technical error.

## Refund types

Probly only refunds your initial costs.

### Initial cost

This refund applies when a market is voided. A market may be voided when:

1. The rules are faulty, the market is posted too late, it is removed before resolution, or its rules change after launch.
2. The resolution source becomes unavailable and no acceptable alternative exists.
3. The event is cancelled or indefinitely postponed with no clear path to resolution.
4. The outcome is genuinely ambiguous and cannot be determined fairly under the published rules.
5. A critical setup error is discovered that materially affects fairness.

If a void is declared, Probly may announce it on the affected market page or notify users separately, at Probly’s sole discretion.

## Refund issuance

Refunds typically apply to trades made before Probly makes an announcement. If Probly pre-announces a clarification, refunds may apply to trades made before that pre-announcement. Trades made afterward are generally not eligible.

## When refunds are not issued

Refunds are not typically issued simply because a market is controversial or disputed. Non-refundable circumstances include:

1. Disagreements over interpretation, qualification, or unclear wording.
2. Slippage on market orders.
3. Orders placed by mistake.
4. Price movements while an order is open.
5. Network gas fees paid to the blockchain.
6. Normal trading losses.


---

# 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.probly.com/resources/refund-policy.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.