> For the complete documentation index, see [llms.txt](https://wickdottrade.gitbook.io/wick/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wickdottrade.gitbook.io/wick/prediction/introduction.md). # Introduction Wick Sports is built on Polymarket, giving users access to trending sporting events through a fast, mobile-first interface. The goal is to deliver the speed, clarity, and ease of use people expect from a traditional sportsbook, while keeping everything fully on-chain. While Wick currently focuses on sports predictions, the underlying system is designed to support a broader range of prediction markets over time, all within the same unified app experience. Under the hood, Wick separates systems by purpose to maximize performance. Spot and perpetual trading run on Hyperliquid, while prediction markets settle on Polygon through Polymarket. This architecture allows each market type to operate on the chain best suited for it, while Wick unifies everything into a single, seamless user experience. --- # 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://wickdottrade.gitbook.io/wick/prediction/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.