Skip to content

Marketplace

Sell your apps to Xuda customers.

Open Marketplace
Checked against the dashboard on November 19, 2026

Selling from the Marketplace page, and buying from its checkout, are done in the dashboard. Creating, editing, putting on sale and deleting a listing, reading and changing the seller plan, and the purchase itself have no public methods today. What you can do from code is the plugin catalogue behind every Install button, and the consent screen shown before an install.

Six methods of the catalogue are reachable with an account API key: the catalogue reads, the install lifecycle, and uploading a plugin's own package. One more, on the Marketplace microservice, returns the consent screen.

Browsing and installing

Browse the catalogue

get_plugins returns the public catalogue (only approved, non-private listings unless you pass your own uid), filterable by category, tags and a free-text match, and get_plugins_categories returns the category facets with their counts.

See what is already on a project

get_app_plugins lists what a project has installed.

Install

install_plugin installs a named plugin onto an app_id. uninstall_plugin removes one.

curl -s https://xuda.ai/cpi/install_plugin \
  -H 'content-type: application/json' \
  -d '{"api_key":"YOUR_API_KEY","app_id":"YOUR_APP_ID","plugin_name":"@xuda.io/example-plugin"}'
const res = await fetch('https://xuda.ai/cpi/install_plugin', {
  method: 'POST',
  headers: { 'content-type': 'application/json' },
  body: JSON.stringify({
    api_key: 'YOUR_API_KEY',
    app_id: 'YOUR_APP_ID',
    plugin_name: '@xuda.io/example-plugin',
  }),
});
const { code, data } = await res.json();
import requests

res = requests.post(
    'https://xuda.ai/cpi/install_plugin',
    json={'api_key': 'YOUR_API_KEY', 'app_id': 'YOUR_APP_ID', 'plugin_name': '@xuda.io/example-plugin'},
)
Ids are unscoped on the way out

get_plugins strips the @xuda.io/ scope prefix from the _id it returns. Add it back when you pass a plugin name into install_plugin.

get_install_consent, on the Marketplace microservice itself, returns the consent screen for one AI agent or plugin: what it does, who published it, the liability text, and the content hash an install has to echo back, before install_plugin runs.

Publishing a plugin

upload_plugin creates or updates a plugin's own listing document, uploading its package and metadata. Putting a plugin in the Marketplace needs the Agency plan or above. A private upload is also allowed by the Plugins plan of the workspace it is uploaded in. Sending visibility: "private" or skip_publish_review: true keeps it out of the review queue and off the public catalogue, for a code or npm update that should not re-open review.

Listings you sell

Listings of your own apps, the way the Marketplace page makes them, are managed from the dashboard: the listing window and the new listing page do it control by control. Your seller plan is in the plans window.

How is this guide?

Last updated on November 12, 2026