> For the complete documentation index, see [llms.txt](https://docs.vultisig.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vultisig.com/ecosystem.md).

# Ecosystem

- [Vultisig Extension](https://docs.vultisig.com/ecosystem/vultisig-extension.md): Vultisig browser extension for Chrome and Firefox. Full vault in the browser: create, send, swap, DeFi, and dApp connect. No seed phrase.
- [How to use Vultisig Extension](https://docs.vultisig.com/ecosystem/vultisig-extension/how-to-use-vultisig-connect.md): Install and use the Vultisig extension on Chrome or Firefox. Full vault in the browser: create, send, swap, DeFi, and dApp connect.
- [Web3 dApps with Vultisig Extension](https://docs.vultisig.com/ecosystem/vultisig-extension/web3-support.md): Supported dApps and Web3 sites for Vultisig Extension. DeFi, NFT marketplaces, and utilities. Native integration or wallet injection fallback.
- [Vultisig plugin marketplace (paused)](https://docs.vultisig.com/ecosystem/marketplace.md): Plugin marketplace (paused, not in production). Planned self-custodial automation for scheduled workflows and AI agents.
- [Vultisig SDK](https://docs.vultisig.com/ecosystem/vultisig-sdk.md): Vultisig TypeScript SDK and CLI. Create vaults, check balances, send, swap, and sign across 36+ chains. No seed phrase.
- [Vultisig community tools](https://docs.vultisig.com/ecosystem/community-tools.md): Community-built Vultisig tools. Vault Share Decoder for last-resort recovery.


---

# 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.vultisig.com/ecosystem.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.