Five kinds of thing on the shelf. Two of them install.
The catalog holds AI agents, components, plugins, projects and Pro listings, plus the people who publish them. One method installs exactly two of those five. A plugin is installed from inside your own project, a project button reads Fork, and a Pro listing is a purchase followed by provisioning. Knowing which one you are about to click is most of what this page is for.
Item types the install button installs, out of five on the shelf
Fields stamped on every installed document, naming where it came from
Named checks the reviewer returns, each with its own severity
The cut Xuda keeps by default, falling to 5 percent on the top tier
One method, one switch, and five different places you end up.
Install is a single method that loads the record and switches on what kind of record it is. There are exactly two real cases. Everything the switch does not recognise comes straight back as installation not supported, which is why three of the five things you can press Install on never reach it at all.
An installed agent is a pointer, not a copy.
The install writes a document with seven fields into your default project: an id, a type, a state, a provenance block, one property naming what kind of unit it is, and the account and project ids that belong to the publisher. No configuration, no instructions, no tools, no name. The real document stays with the publisher, and the platform reads it back through the project id stamped on your copy.
- Your copy keeps the document id the publisher gave it, which is also how the site knows to show you Open rather than Install the next time you visit.
- The upside of a pointer: an improvement the publisher makes reaches you with nothing to reinstall and no version to chase.
- The downside, stated plainly: if the publisher takes the agent down, or that project becomes unreachable, what you keep is the stub rather than the agent.
- An agent always lands in your default project. Only a component lets you choose which project it goes into.
- You press InstallSigned out, the intent parks in your browser for fifteen minutes and resumes after login
- Three gates runThe marketplace record live, the source agent live, and its visibility set to public
- A seven field stub is writtenInto your default project, keeping the document id the publisher gave it
- Five provenance fields are stampedWhen, from which project, from which account, by whom, and from which listing
A component is a real copy, and it tells you what it is missing.
A component install walks its dependencies before it writes anything. It serialises each program and looks for the ids of other programs in the same project, then recurses into whatever it finds. Tables come from one field, the table each program has its datasource bound to. Plugins come from two, the interface framework on a program and the database connector on a table.
- It is a reference walk over the documents themselves rather than a manifest anyone declared, which makes it capable and approximate at the same time.
- Plugins are a precondition, not something the installer fetches. A missing one stops the install by name, and the site then offers to install that plugin and try again, one plugin at a time.
- That check runs before the first write, which matters: there is no rollback past it, so a save that fails midway leaves the earlier documents in your project.
- Reinstalling over something you deleted in Studio is allowed on purpose. A studio delete leaves a tombstone rather than removing the document, and the installer treats a tombstone as free space.
Every way onto the shelf, and the rule that decides it.
A Pro listing, an agent published with its project, and a plugin all take different routes to the catalog, and every one of them arrives at the same gate. Deterministic checks run first and the reviewer runs second, then two numeric thresholds are applied to whatever it said. Read this picture downward: each branch is an outcome, and the cards under it are the rules that produce it.
What it costs to sell, and what you keep.
A seller tier decides three separate things, and each one is enforced somewhere different: the cut at the moment of the charge, how many listings may be live at once when you publish, and which kinds of listing you can create at all. An account that never picked a tier is treated as Free and pays twenty percent, so nothing changed for sellers who were already trading when the ladder shipped.
- A slot is taken only while a listing is live or waiting on the review queue, so pausing one frees it immediately. A downgrade that would strand listings is refused with the count rather than by taking anything down.
- Creating a paid listing also needs an Agency membership at $399 a month. That is the gate most people meet first, and it sits on the create, update and publish methods rather than on the tier.
- Seller status is a payability check, not a competence check. It passes on an active Stripe connected account, an active Xuda finance account, or Xuda Network partner standing, and none of those assesses your work.
- Publishing is not free form: at least 3 keywords, a description of 500 to 3,000 characters, a name of 5 to 50, at least one image, and a price between $5 and $100,000. A Pro listing therefore can never be free.
The charge splits at the moment of payment, and the thing you bought is built afterwards.
There is exactly one call in the whole marketplace that moves money, and it only ever runs for a Pro listing. Agents and components install through a different method that contains no payment code at all. The split is not a payout Xuda runs later: it is one charge with two destinations, settled by Stripe as the card is charged, so no seller share ever sits in a Xuda balance.
What the marketplace does not do
Five of these six answers are a limit. They are here because you would meet them in the first week anyway.
Watch an install land in a real project.
Install one and watch where it lands.
A free agent takes a click and a login: three gates, a stub in your default project, and five fields naming exactly where it came from. If you would rather not open a dashboard at all, three commands will run one from a terminal.