> For the complete documentation index, see [llms.txt](https://docs.squads.so/main/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squads.so/main/navigating-your-squad/integrated-apps/range.md). # Range Greater transparency for your Squads transactions ## What is Range? Range is a security platform designed to protect you from scams, hacks, and unintended mistakes that could compromise the integrity of your Squads account. We chose Range for its accuracy, speed, and proven track record with leading organizations such as the Solana Foundation, Etherfuse, Agant, and Perena. ## How do Squads users benefit from this integration? By integrating Range's simulation API, we can provide clearer explanations of how transactions will impact your Squad and flag potentially risky or malicious transactions in real-time—before they are signed. In this context, Range is particularly helpful for non-technical users who e.g. might be tricked by a custom instruction granting access to funds or changing the authority of a program. --- # 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://docs.squads.so/main/navigating-your-squad/integrated-apps/range.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.