> 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-providers.md).

# Wallet Providers

Sats Connect lets your app connect with a variety of **Bitcoin, Spark, Starknet & Stacks wallets**:

* The [Xverse](https://www.xverse.app/) browser extension and mobile in-app browser
* The Unisat browser extension
* :soon: Any Bitcoin wallet which follows the [WBIP004](https://wbips.netlify.app/wbips/WBIP004) standard
* :soon: Support for more Bitcoin, Spark, Stacks & Starknet wallets will be announced soon

When installed in your user's browser, the wallets listed above inject a **wallet provider** into the [window](https://developer.mozilla.org/en-US/docs/Web/API/Window) of your application. 

Sats Connect detects the wallet provider, and lets your app interact with it via the `Wallet` component and [`Wallet.request`](/sats-connect/wallet-methods/request-methods.md) methods. \
\
You can use these methods to request your user to share their Bitcoin & Stacks wallet addresses, and sign messages and transactions. All available Bitcoin & Stacks methods are detailed in the present documentation.

## Xverse Wallet Provider

[Xverse](https://www.xverse.app/)'s browser extension and mobile in-app browser will both inject an  `XverseProviders` object into the [window](https://developer.mozilla.org/en-US/docs/Web/API/Window) of your application. 

The `XverseProviders`  interface exposes two sets of methods:

* Standard methods which can be can be invoked with [`wallet.request`](/sats-connect/wallet-methods/request-methods.md)
* [Xverse custom methods](/sats-connect/wallet-methods/xverse-custom-methods.md), which can only be invoked for users using the Xverse wallet.

## Unisat Wallet Provider

The Unisat browser extension injects a `window.unisat` object into the [window](https://developer.mozilla.org/en-US/docs/Web/API/Window) of your application. 

Sats Connect lets you interact with the Unisat wallet provider via the [`wallet.request`](/sats-connect/wallet-methods/request-methods.md) standard methods.

## :soon:  WBIP004 Web Providers

Sats Connect will soon detect the wallet extensions that inject their provider information under `window.btc_providers` , following the [WBIP004](https://wbips.netlify.app/wbips/WBIP004) standard, and let you interact with them via the [`wallet.request`](/sats-connect/wallet-methods/request-methods.md) standard methods.


---

# 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-providers.md?ask=<question>&goal=<user_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.