> 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/squadsx-beta-development/what-is-squadsx.md). # What is SquadsX SquadsX is a web-extension wallet powered by Squads Protocol and its v4 program. It enables users to safely engage with Solana applications through their Squad. This simplifies the creation of multisig transactions, allowing users to interact with applications as they would with conventional wallets. This documentation provides a developer reference for using and integrating with SquadsX. ### Why SquadsX Matters Think of SquadsX as the next big step in the evolution of self-custody - it's convenient, secure, and forgiving. It's a significant addition to the primary Squads product. This web-extension wallet can potentially unlock access to the value managed by numerous active Squads for many existing Solana products. We believe that improvements in the wallet-app compatibility could scale up opportunities for the entire ecosystem. --- # 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/squadsx-beta-development/what-is-squadsx.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.