> For the complete documentation index, see [llms.txt](https://docs.xverse.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xverse.app/sats-connect/wallet-methods/wallet_open.md). # wallet\_open ## wallet\_open methods The `wallet_open*` methods let your app open **specific screens and flows** in the Xverse wallet (e.g. Receive, Send, Swap, Bridge, Earn) via a single Sats Connect request. They are designed to create a smoother, more seamless **dapp ↔ wallet** experience by allowing your app to deep-link users directly into the right place in the wallet — without requiring manual navigation or multiple steps. Common use cases include: * guiding users to the correct **Receive** address for a given asset or network * directing users into **Swap / Bridge / Earn** flows to complete an in-app intent * reducing friction when an action requires switching from your app to the wallet {% hint style="info" %} `wallet_open*` methods require the user to have already connected their Xverse account to your app and granted the necessary [permissions](/sats-connect/xverse-wallet-permissions.md). {% endhint %} --- # 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.xverse.app/sats-connect/wallet-methods/wallet_open.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.