> 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/rewards/points.md). # Points TurboFlow’s platform points system. TurboFlow Points is the platform’s points system, designed to reflect eligible activity across TurboFlow. ### How It Works Points may include activity related to: * trading participation * referrals * campaigns The exact allocation logic is determined by platform rules and may vary over time. ### Where to Check Users can view their total points directly through the Points interface on TurboFlow. Displayed balances may also include point categories such as airdrop points or other eligible distributions when applicable. ### Update Cycle Points are updated on a scheduled basis rather than in real time. Users should always refer to the live product interface for the latest displayed balance, update timing, and applicable notices. ### Important Notice Points are part of TurboFlow’s platform points system. They do not by themselves represent cash, tokens, or guaranteed future benefits. Point allocation, update timing, and any related utility remain subject to platform rules and may change over time. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://turboflow.gitbook.io/whitepaper/turboflow/rewards/points.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.