> For the complete documentation index, see [llms.txt](https://gambleguru.gitbook.io/gambleguru-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gambleguru.gitbook.io/gambleguru-documentation/introduction.md). # Introduction GambleGuru stands as a groundbreaking GambleFi venture aiming to bridge the gap between the worlds of cryptocurrency and traditional fiat betting. After six months of dedicated development work, we are excited to unveil our initial concept. GambleGuru promises a real-time sports betting experience covering a wide array of sports. Users will have the flexibility to make deposits in both fiat and cryptocurrency, thanks to our robust e-money infrastructure and carefully designed backend. GambleGuru will operate through a fee-based growth strategy. GambleGuru plans to have 50% of all fees collected, whether in fiat or cryptocurrency, converted into our native platform token, $GG. This allocation is intended to drive the growth of our project. The remaining 50% will be strategically allocated to a treasury, serving both as a resource for sustained operations and as part of our revenue-sharing plans --- # 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://gambleguru.gitbook.io/gambleguru-documentation/introduction.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.