Marketplace¶
The concept behind publications is explained in Sharing and reuse.
The Marketplace offers bundles that organisations have published and Artific has reviewed. You find and install what is offered through Installed.
A bundle may require an entitlement: the right to install it, recorded for your organisation once the system that took the payment says so. Payments and invoicing happen outside Core. This is separate from what your models and tools cost, which is on Usage.
Submit a bundle¶
Create a publication with the visibility Marketplace (see Sharing). It starts as a draft: it is on nobody's offer. Publish a version on it and then choose Submit for review.
After that the submission is with Artific. While it waits, nothing changes for the organisations already subscribed to you: they stay on the version they have until the new one is offered.
What your bundle asks for at install is part of the offer. The reviewer sees the version's parameters, and every organisation sees them before it installs, even when you withhold the content. If your bundle asks for credentials, or lets the installer choose an MCP server or API connector of their own, it works with the installer's access. Say in that parameter's explanation what the bundle uses that access for, so reviewer and installer can weigh it.
What a review decides¶
A review ends in one of two ways, and your publication page says which:
- Offered — the bundle goes onto the marketplace. That is also the moment it propagates: every subscription that follows the latest version gets it.
- Sent back — with a reason from a fixed list: the description is not enough, the changelog is not enough, the terms are unclear, the content is not safe, this is already listed, or not ready yet. The reasons are fixed rather than free text so that you read them in your own language. Fix what the reason names, publish a new version and submit again.
Nobody reviews their own submission, which is why the decision is not the publisher's to make.
When a bundle needs an entitlement¶
Where a version asks for an entitlement (the term Entitlement required), no organisation can subscribe to it without one. An entitlement names the publication, the period it covers and the payment system's own reference — an order, an invoice, a contract — and it is recorded for the organisation that is paying.
An entitlement that is revoked, or that lapses, ends access at that moment. Nothing is deleted: the copies installed under it stay and become unreachable, and a new entitlement puts them back without a reinstall.
An entitlement is a commercial fact about an organisation rather than a possession of it, so an organisation cannot record its own and a publisher cannot record its customers'. Ask your operator where an entitlement you expect is missing or wrong.