Tabs Marketplace
Publishing
Workspace owners and admins publish an agent from its page: Settings → Agents → the agent → Marketplace → Publish…. Every version goes to Tabs & Spaces for review before it's listed. Tabby can't be published (every workspace has it already).
Publishing needs the deployment to be registered with Tabs & Spaces (Deployment settings → Support): our cloud is; a self-hosted deployment registers there. Its listings show the workspace's name as their publisher; the person who sent it is kept for our review, never shown.
What a listing carries
You choose what goes in. The page lists what the agent has, ticked to start with (except OpenClaw's starter skills, which every workspace has):
| Part | What's published |
|---|---|
| The agent | Its name, title, description, instructions and face (a drawn one, or its picture: PNG, JPEG or WebP up to 256 kB). |
| About | A longer account of it, in Markdown, and up to three categories. |
| Skills | OpenClaw's built-in skills by name, ClawHub's by reference (@owner/slug). |
| Connectors | Each one's address (without its query, which might hold a key), how it signs in (none, a key in a header, or OAuth), whose account it uses, and the tools the agent may use. |
| Routines | Its workflows, recurring tasks and triggers in one space you choose. A recurring task's or trigger's workflow comes along with it. |
What it never carries
Its model, its memory, its host access, connectors' keys and tokens, and anything else from your workspace: your spaces, tabs, people and other agents are replaced by placeholders (below), and the workspace that adds it fills them in.
Placeholders
| In your workspace | In the listing | When it's added |
|---|---|---|
| The agent itself | @self | The new agent |
| Tabby | @tabby | That workspace's Tabby |
| A person (an assignee, a step's person) | @adder | Whoever adds it |
| A conversation, Docs or Tasks tab | @conversations, @docs, @tasks | The chosen space's first tab of that type, made if missing |
What can't be listed yet is shown greyed out, with why: a routine that uses another agent, an app's tab, action or event (apps come to the marketplace later), or a tab that's gone.
Review and versions
- Waiting for review: we're looking at it; the agent's page says so. We email the person who sent it when we decide.
- Listed: every deployment can find and add it. Its page on the website is
tabsandspaces.dev/marketplace/<slug>. - Not listed: we say why; change the agent and send it again.
- A new version (Send a new version…, with what changed) waits for review while the listed one stays listed. Workspaces that added an earlier version keep their copy.
- Taking it out: Take it out on the agent's page removes it from the marketplace; publishing again sends a new version for review. We can also take a listing down, and say why.
The catalogue's API
The catalogue is public and read-only, for any site or tool. It answers any origin.
curl "https://control.tabsandspaces.app/api/v1/marketplace/listings?q=notes&category=productivity"| Request | Answer |
|---|---|
GET /api/v1/marketplace/listings?q=&kind=&category=&limit=&offset= | { listings, total }: live listings, most added first (limit up to 60). |
GET /api/v1/marketplace/listings/:slug | { listing }: one, with about, changes and content (what it sets up). 404 if it isn't listed. |
GET /api/v1/marketplace/listings/:id/picture?v= | Its picture, if it has one. |
A listing in the list has id, slug, kind (agent), name, title, description, categories, avatar, pictureUrl, publisher.name, version, installs, needs (how many skills, connectors, workflows, recurring tasks and triggers it sets up), publishedAt and updatedAt.