> For the complete documentation index, see [llms.txt](https://support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.backpack.exchange/support-docs/vn/legal/backpack-exchange-disclaimer-re-ftx-creditor.md). # Backpack Exchange Disclaimer re: FTX Creditor **Disclaimer** Backpack Exchange is providing access to FTX Creditor solely as a convenience to our users. Backpack Exchange does **not** endorse, support, or recommend the sale or transfer of any FTX claims. We are not affiliated with FTX Creditor and have not independently verified the accuracy, legitimacy, or reliability of its services. Users interact with FTX Creditor entirely at their own risk. Backpack Exchange expressly disclaims any and all responsibility or liability arising from or related to your use of the FTX Creditor services. This includes, but is not limited to, any loss, error, delay, dispute, or claim arising out of or in connection with the FTX Creditor platform or your transactions with it. Please conduct your own due diligence and consult with your legal or financial advisors before proceeding. --- # 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://support.backpack.exchange/support-docs/vn/legal/backpack-exchange-disclaimer-re-ftx-creditor.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.