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 |
Core install currently materializes skill and tool packages into your workspace. Persona and agent packages can be published and browsed today; full persona/agent import is being rolled out.
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.
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 or tool in your organization.
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.