> 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/markets/how-are-markets-created.md).

# How Are Markets Created

0Y markets are created by the 0Y Markets team, with input from the community. We will introduce a market place for a permissionless market creation in the near future.

We focus on:

* markets that are easy to understand (YES/NO or Higher/Lower)
* markets that are easy to verify (strong resolution sources)
* markets that avoid ambiguity (clear edge-case handling)

***

#### Can I create my own market?

You can’t publish markets directly (to protect quality and reduce disputes), but you can suggest markets.

To help your suggestion get listed, include:

* a clear title
* the exact question (YES/NO)
* your preferred resolution source
* the expiry date/time + timezone
* why people would trade it (demand)

Please feel free to join us at 0Y community for more discussions: <https://t.me/0ymarketsofficial>

***

#### Charlie’s good vs bad suggestion

Bad: “Will BTC go up soon?” (too vague)

Good: “Will BTC close higher in the next 15 minutes? Resolve using Binance BTC/USDT price at timestamp.”


---

# 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/markets/how-are-markets-created.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.