> For the complete documentation index, see [llms.txt](https://turboflow.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://turboflow.gitbook.io/whitepaper/turboflow/getting-started/why-were-building-turboflow.md). # Why We’re Building TurboFlow Today, too many trading platforms still feel difficult to enter, expensive to use, or built around the needs of professionals rather than everyday participants. TurboFlow is designed from the other direction: **starting with the retail user**. We are building TurbFlow around four core principles: 1. **Amplified Opportunity** Event Contracts start from just **30 seconds**, while perpetuals offer **up to 1000x leverage**. TurboFlow is designed to help users do more with less capital. 2. **Accessible by Design** Users can start trading from as little as **$2**. Lower barriers create broader access and allow more people to participate. 3. **Institutional-Grade Liquidity** TurbFlow is powered by **professional market makers and robust trading mechanisms**, bringing stronger market quality to everyday users. 4. **Transparent by Design** With on-chain data, published rules, and verifiable market logic, TurboFlow is built to make trading more open, more understandable, and more trustworthy. **TurboFlow is not just about adding more products. It is about rebuilding market access for everyone.** --- # 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://turboflow.gitbook.io/whitepaper/turboflow/getting-started/why-were-building-turboflow.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.