> 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/getting-started.md). # Getting Started #### What is 0Y Markets? 0Y Markets is a prediction market platform where you trade on real-world outcomes, from crypto and finance to sports, culture, and more. Markets use simple outcomes such as **YES/NO** or **Higher/Lower**, with live odds and potential payouts shown before you confirm your trade. 0Y uses the **Logarithmic Market Scoring Rule (LMSR)**, allowing trades to execute instantly without needing another user to take the opposite side. #### Do I need DeFi knowledge to use 0Y? No. 0Y is designed to be simple and beginner-friendly, with straightforward market choices, a payout preview before you confirm your trade, and automatic settlement when markets resolve. You don't need prior DeFi or prediction market experience to get started. #### Is 0Y focused on Asia / SEA? Yes. 0Y Markets is built for **Southeast Asia and emerging markets**, with a focus on accessible trading and culturally relevant markets across the region. 0Y supports deposits across multiple networks and continues to expand its market coverage and payment options to make prediction markets more accessible to users across SEA and beyond. --- # 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/getting-started.md?ask=&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.