> For the complete documentation index, see [llms.txt](https://betcha.gitbook.io/betcha-markets/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://betcha.gitbook.io/betcha-markets/welcome-to-betcha.md). # 👋 Welcome to Betcha ## Overview Betcha is a decentralized prediction market platform that lets users predict world events. Built on the shoulders of giants, Betcha's unique value comes from it's zero fee nature, competitive yields for users, and strong rewards program - we create an ecosystem where it pays to play! Betcha is built on Edgeless, a novel L2 network that offers users applications with zero application fees. Betcha leverages a Constant Product AMM market design, enabling users to instantly place predictions with a competitive line. Betcha's vision is to be the go-to ecosystem for users to predict on world political and economic events. Whether you are interested in the US election or interest rates, Betcha is the premier market for predicting these events and earning while doing so. ## Navigating Betcha We've put together documents to get you learn more about our product. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://betcha.gitbook.io/betcha-markets/welcome-to-betcha.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.