Publish an app on Exchange
Make your app understandable, discoverable and ready for informed consent.
Write a listing around one useful outcome
Give the app a recognizable name and a short description of the job it performs. Include the publisher, supported platforms, version, price, support contact and a real launch or setup link.
Exchange currently displays the public app catalogue. A listing’s presence does not itself describe installation, permission grants or billing. Those steps belong in the app’s setup flow.
Describe capabilities before consent
| Include | Explain to the user |
|---|---|
| Inputs and data access | Which information the capability reads. |
| Actions and outputs | What it changes and what it returns. |
| Autonomy ceiling | How far the user may authorize it to act. |
| Approvals | When a person must confirm an action. |
| Costs and recovery | What usage may cost and how failures are handled. |
Prepare and test the application
- Package the models and services the application needs.
- Declare capability inputs, outputs and side effects.
- Test accepted and denied permissions on each supported surface.
- Provide setup instructions, release notes and a support path.
- Register the app with
POST /api/v1/platform/registerand your API key.
Publishing contract
POST /api/v1/platform/register takes the app manifest (unknown fields answer 400) and returns the app's token. Registering deploys nothing: a bundle only lists model paths. A manifest with market_listed set to true appears in the public catalogue, GET /api/v1/marketplace. Card fields are checked: an icon, color or link that is not one is cleared, and a vendor name that reads as Priostack is not listed.