Marketplace
The Nexora Marketplace is a public, Parendum-hosted registry where the community publishes and installs Nexora packages. It runs as a standalone site at marketplace.nexora.parendum.com and is consumed by any Nexora or NexoraCloud instance through an Import Link.
You register a marketplace account (separate from your Nexora instance login), then browse, install, like, comment on, and publish packages. Every account can both publish and consume — there is no separate publisher tier.
Package types
The Marketplace hosts four package types, all installable into your Nexora workspace:
| Type | What it is |
|---|---|
| Skill | A named capability or behavior bundle |
| Tool | A function or integration |
| Persona | A character or personality |
| Agent | A complete autonomous AI agent |
All four package types — skill, tool, persona, and agent — import into your workspace. Importing an agent also auto-installs the leaf skill/tool/persona packages it declares as dependencies (nested agent dependencies are recorded but not recursively installed).
Browsing and searching
The Browse page is a searchable catalog with:
- Full-text search (
q) across package names and descriptions - Filter by type — skill, tool, persona, or agent
- Filter by tags — packages carry up to 10 lowercased tags
- Sort — newest, most popular (likes), or most downloaded
- Pagination — page through results
Each package card shows its name, icon, type, description, tags, and download/like counts. The home page surfaces overall stats (public package count, total downloads, registered users) and featured packages.
How packages are ranked
The default browse ranking favors packages the community has shown to be reputable and trending — established, well-liked, frequently downloaded packages rise to the top, and only those reach the Featured surface on the home page. Brand-new packages and those without much of a track record are demoted (shown lower and kept out of Featured) until they earn engagement.
Demotion is not hiding. A package is never removed from search — a direct text search by name still finds it regardless of its standing. The practical effect is that a freshly published package is simply harder to stumble upon by browsing until it accumulates likes, downloads, and age.
Trust tiers and warnings
Every package carries a trust tier that reflects how much the community has engaged with it and the publisher’s track record:
| Tier | Meaning |
|---|---|
| Trusted | Strong, sustained engagement from a publisher with a solid track record |
| Established | A proven package with meaningful adoption |
| Low | Limited track record so far |
| New | Recently published, no track record yet |
The tier is derived from signals such as a package’s popularity (likes and downloads), recent/trending activity, its age and maturity, and the publisher’s history (account age, verified-publisher status, their other packages, and total downloads), reduced by any unresolved abuse reports. You see only the tier itself — no raw scores are exposed.
Each package also shows a warning level that summarizes how cautious to be:
- Standard — trusted or established packages with enough engagement. No extra prompts.
- Elevated / High — new or low-track-record packages, or packages below the engagement thresholds. These show a prominent warning banner on the package page.
A high or elevated warning level is not an accusation that a package is malicious — it only means the community has not yet built up enough signal to vouch for it. Review what you install, especially for tools and skills that can run code or reach external services.
Third-party content and liability
Marketplace packages are published by other users, not by Parendum. Every package page carries a third-party disclaimer:
Third-party content. Nexora is not responsible for packages published by users. Install at your own risk.
For packages with an elevated or high warning level, this disclaimer is shown as a prominent banner, and downloading or installing the package opens an at-your-own-risk confirmation that you must explicitly accept before the action proceeds. Trusted and standard packages do not show the extra confirmation.
Installing a package
Packages are installed into a Nexora instance via an Import Link copied from the package detail page.
Copy the Import Link
On a package’s detail page (/p/{slug}) on the Marketplace, click Copy Import Link. The link points at the package’s metadata endpoint:
https://marketplace.nexora.parendum.com/api/packages/{slug}Import into your instance
In your Nexora instance, paste the link into the marketplace import field. Your instance calls POST /api/marketplace/import with that URL, fetches the package metadata, and creates the corresponding skill, tool, persona, or agent in your organization.
If the package has an elevated or high warning level, your instance shows the third-party disclaimer and asks you to explicitly acknowledge the risk before the import proceeds. Trusted and standard packages import without the extra prompt. This applies whether you import from the web UI or from the NexoraCLI terminal client.
Private packages
If the package is private, set your personal Marketplace API key in your Nexora instance first (see below). The instance attaches it as a bearer token so private packages resolve.
You can also download a package directly from the Marketplace as a ZIP (containing the package files plus a .nexora.deps manifest when the package declares dependencies).
Publishing a package
Sign in to the Marketplace and use the Publish wizard (/publish), a five-step flow:
Basic info
Name, type (skill / tool / persona / agent), description, icon, and tags.
Files
The file payload that makes up the package (stored as a {filename: content} map, zipped on download).
Dependencies
Optionally declare other marketplace packages (by slug) that this package depends on. They are resolved at read time and emitted into the download’s .nexora.deps manifest.
Readme
A markdown README rendered on the package detail page.
Review & publish
Confirm and publish. The slug is generated automatically as name-username. Packages are live immediately on publish.
You can edit a published package later (name, files, manifest, version, dependencies, visibility) from its edit page. Note that versioning is a single mutable string — there is no version history; updating overwrites the current files in place.
Private packages and access control
Each package has a visibility of public or private. Private packages are only resolvable by:
- The author
- Individual users granted access by username
- Members of a group the package is shared with
Groups are created and managed from your Marketplace Settings. You can invite members by username and share owned packages into a group.
Personal API keys
To let a Nexora instance install your private packages, mint a personal API key (nmk_…) from Marketplace Settings → API Keys. The raw key is shown once; store it in your Nexora instance so import requests authenticate. You can hold up to 10 keys and revoke any of them.
Likes, comments, and reports
- Likes — toggle a like on any package; the count is shown on the card and detail page.
- Comments — leave markdown comments on a package detail page; authors can delete comments on their packages.
- Reports — flag a package for moderation (spam, inappropriate, broken, duplicate, or other).
Related pages
The building blocks you install map to the local catalog pages in your instance:
| Component | Local page |
|---|---|
| Skills | /ui-guide/skills |
| Tools | /ui-guide/tools |
| Personas | /ui-guide/personas |
| Agents | /ui-guide/agents |
The backend marketplace endpoints are documented in the Tools API reference.