# Markets to Avoid

There are three main types of markets to avoid proposing.

### Markets you don't understand

Avoid proposing in markets you **don't fully understand**, especially if you're unfamiliar with their **rules or data sources**.

*Example*: In *Nascar: AutoTrader EchoPark Automotive 400 winner*, a casual viewer proposed right after the race. They didn't realize NASCAR performs post-race inspections before finalizing results.

<figure><img src="/files/HI1XWPGQsX5ebbtQ3kwq" alt=""><figcaption></figcaption></figure>

### Markets with ambiguous rules

Stay away from markets with **unclear or undefined rules**. If the criteria can be interpreted multiple ways, **don't risk your bond**.

*Example:* In *Will Zelenskyy wear a suit before July?*, the rules didn't specify what qualified as a "suit," leaving the market open to dispute.

<figure><img src="/files/42i5PagX806inArogJxl" alt=""><figcaption></figcaption></figure>

### Sports, weather, and asset price markets&#x20;

Some markets such as sports, weather, and asset price are **automatically proposed by bots**. Submitting your own proposal is unnecessary and risks your bond.

*Example*: In *XRP UP or Down - November 1, 7PM ET*, a bot submitted a proposal the moment the market was ready to be resolved.

<figure><img src="/files/VQUdZAkg5jXLIV1Kc9Ug" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://polymarketguide.gitbook.io/polymarketguide/resolution/how-to-participate/propose/markets-to-avoid.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.