> For the complete documentation index, see [llms.txt](https://polysports.gitbook.io/polysports-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polysports.gitbook.io/polysports-whitepaper/about-us.md). # About Us Polysports is a play to earn gaming platform where users use their skills to create, compete and earn cryptocurrencies and are rewarded for contributing to the success of Polysports ecosystem. Our vision is to have one of the largest communities of passionate sports lovers, crypto enthusiasts & traders who can benefit from our value-added services and have a great gaming experience. With the use of blockchain technology and inbuilt wallet, Polysports is bridging the gap between Web2 and Web3 users. Our users not only get to play virtual games by creating competitive teams using their skills but also socialize, create, trade and collect rare NFTs and play games in the metaverse. #### **THE GLOBAL FANTASY SPORTS MARKET SIZE TO CROSS USD 49 BILLION IN 2026, GROWING AT A CAGR OF 14% DURING 2020-2026** --- # 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://polysports.gitbook.io/polysports-whitepaper/about-us.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.