> 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/developer-docs/marketplace.md).

# Marketplace Plugins (paused)

{% hint style="warning" %}
**Paused.** The plugin marketplace is not in production. These pages describe the planned product and stay for reference.
{% endhint %}

These pages describe the planned plugin product. Plugins would run on Vultisig infrastructure and sign through the vault. Users do not hand over keys.

## Getting Started

1. **Understand the architecture**: Learn [what a plugin is](/developer-docs/marketplace/plugins.md) and how the [services](/developer-docs/marketplace/services.md) work together
2. **Build your plugin**: Follow the [quick start guide](/developer-docs/marketplace/basics-quick-start.md) and reference the [App Recurring](https://github.com/vultisig/app-recurring) plugin
3. **Submit for review**: Complete the [submission process](/developer-docs/marketplace/submission-process.md) to list on the Marketplace

## Documentation

### Architecture

* [What is a Plugin](/developer-docs/marketplace/plugins.md) - Core concepts and security model
* [Services Architecture](/developer-docs/marketplace/services.md) - HTTP Server, Worker, Scheduler, TX Indexer
* [Policy Rules](/developer-docs/marketplace/metarules.md) - MetaRules and Direct Rules for transaction validation
* [Infrastructure Overview](/developer-docs/marketplace/infrastructure.md) - System components and interactions

### Building

* [Quick Start](/developer-docs/marketplace/basics-quick-start.md) - Step-by-step guide to your first plugin
* [Build Your Plugin](/developer-docs/marketplace/build-your-plugin.md) - Detailed developer guide
* [Adding a New Chain](/developer-docs/marketplace/build-your-plugin/adding-a-new-chain.md) - Extend chain support

### Publishing

* [Submission Process](/developer-docs/marketplace/submission-process.md) - Review and approval workflow
* [Revenue](https://github.com/vultisig/docs/tree/main/developer-docs/marketplace/infrastructure-overview/revenue.md) - Fee structures and 70/30 revenue split

## Reference Implementation

The [App Recurring](https://github.com/vultisig/app-recurring) plugin is the official reference implementation. Clone it as a starting point for your own development.

Each plugin is an independent service — you define your own recipe (transaction rules), authentication flow, and business logic. The reference plugin shows integration patterns, but your plugin can be structured however you need.

## Support

* **Discord**: [discord.gg/Cugw9T2NrP](https://discord.gg/Cugw9T2NrP) - Join the third-party developer section
* **GitHub**: [github.com/vultisig](https://github.com/vultisig) - Source code and issues


---

# 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/developer-docs/marketplace.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.