Skip to main content

Marketplace

The Marketplace moves resources between companies, intact. Package a working setup — agents, tools, tables, and everything they depend on — into a bundle, then hand it to another company as a file or publish it as a template in the public catalog.

What it's for​

Once you've built a workflow that works, the Marketplace is how you distribute it. It solves the hard part for you: resolving every dependency a resource has, stripping secrets so nothing sensitive leaves your company, and recreating the whole graph on the other side in the right order — with a clean rollback if anything fails mid-install.

There are two distribution mechanisms, both built on the same bundle pipeline:

  • Private bundles — export a selection of resources to a downloadable JSON file and share it directly. Anyone in another company uploads the file and installs it. No review, no listing. See Bundles.
  • Public catalog templates — publish a bundle as a versioned, reviewed listing with a name, screenshots, and release notes. Other companies discover and install it from the catalog. See Catalog for installing and Publishing for listing your own.
The Marketplace is managed entirely in the app — exporting, publishing, and installing all happen in the builder. There is no public Marketplace API.

Click Marketplace in the builder sidebar. The landing page offers three actions — Browse catalog, Export bundle, and Import bundle — plus a Recent installs feed showing your company's latest installations with their status. Click any install to open its detail page.

Key concepts​

What can be packaged​

A bundle can contain nine resource types: tools, agents, managers (multi-agents), AutessaDB tables (including their triggers), scheduled jobs, webhooks, custom apps, MCP servers, and connector requirements. Custom apps are pinned to their latest published version at export; the other types embed their full configuration inline so an install never depends on the source company's live state.

Dependencies resolve automatically​

Select a manager and its agents come along; select an agent and its tools and MCP server come along. The export wizard walks the dependency graph transitively and shows you exactly what was auto-included before anything leaves your company. Bundles are capped at 200 resources with a dependency depth of 8.

Secrets are stripped, then re-supplied​

Credentials never travel in a bundle. MCP server auth configuration and connector credentials are removed at export and recorded in the manifest, and the installer asks the receiving company to supply its own: secret fields are re-entered during import, and connectors must be linked to an already-authenticated connector in the target company.

Installs are a resumable saga​

Installation creates resources one at a time, dependencies first, recording each step as it commits — so the status page updates live. If any step fails, every resource created so far is rolled back automatically and the company is left exactly as it was. Completed installs can be revisited any time from Recent installs or the installations list, where you can also share the installed resources with your team or uninstall the whole set.

Versions​

Catalog templates are versioned with dotted version numbers (semver-style, starting at 1.0.0). Each new version is a fresh bundle with its own changelog and goes through review before it is publicly visible.

Installing a template never reads the publisher's live resources — everything comes from the manifest that was captured at export time, so a listing can't change under you.