Publish a listing
Any workspace can publish to the marketplace. You package something you built in Orqane, such as an employee, a skill or an MCP tool, ship it with evaluations, and choose who can see it. Certified listings reach the most buyers.
Become a publisher
Section titled “Become a publisher”Open publisher settings
Go to Settings → Marketplace → Publisher profile and click Become a publisher. You need the Admin role.
Fill in your profile
| Field | Description |
|---|---|
| Publisher name | Shown on every listing |
| Domain | Your company domain. Orqane verifies it with a DNS TXT record |
| Support contact | An email address or URL buyers can reach |
| Legal entity | Company name, country and tax ID, required for paid listings |
| Payout method | Your treasury in USDC, or a bank account. See Monetization |
Accept the publisher terms
Read and accept the publisher agreement. Your workspace is now a publisher, and Builders can prepare listings.
Package a listing
Section titled “Package a listing”Open the item you want to publish and click Publish to marketplace. Orqane creates a draft listing and fills in what it can.
| Section | What to provide |
|---|---|
| Type | Employee template, skill, MCP tool, workflow or knowledge pack |
| Description | What it does, for whom, three example tasks and sample outputs |
| Requirements | Connectors, models and MCP servers it needs |
| Permissions | Generated from the item. Remove anything it doesn’t use |
| Impact classes | Generated from its tools. You can’t declare less than what the tools do |
| Recommended autonomy | The highest level you recommend for new hires, such as L2 Act within limits |
| Sample scenarios | At least two scenarios with sample data, used for Try in sandbox |
| Evaluations | The test suites buyers can run. See below |
| Price | Pricing model and amount |
Orqane strips everything specific to your workspace before packaging: connector credentials, memory, member names, private knowledge and run history are never included.
Versioning
Section titled “Versioning”Listings use semantic versioning: MAJOR.MINOR.PATCH.
| Change | Bump | Example |
|---|---|---|
| Fix a bug, improve a prompt, no change in behavior or permissions | Patch | 1.4.2 → 1.4.3 |
| Add a skill, a tool or an option, without breaking existing setups | Minor | 1.4.3 → 1.5.0 |
| Change outputs, remove a feature, add permissions or a higher impact class | Major | 1.5.0 → 2.0.0 |
Orqane checks your bump. If a version adds permissions or an impact class, it must be a major version. Every version needs a changelog entry. Published versions can’t be edited, only deprecated.
Required evaluations
Section titled “Required evaluations”Every listing except knowledge packs ships with at least one evaluation suite:
- At least 20 test cases covering the example tasks in your description.
- At least one safety case: a prompt-injection attempt, a request outside scope, or a request to exceed a limit.
- A target score for each suite. Buyers see it, and their updates are held if a new version scores below it.
Run the suites from the draft listing. You can’t submit a version that doesn’t meet its own targets.
Certification review
Section titled “Certification review”Submit a version for certification from the draft listing: click Submit for review. The review has four steps.
Automated checks
Orqane validates the package, checks that the permissions match what the tools actually call, and scans MCP servers and code for known vulnerabilities and unsafe outbound hosts. Results arrive within minutes.
Evaluation on Orqane data
Orqane runs your suites, plus its own safety suite, on its own test data. The scores must reach your published targets.
Security and behavior review
An Orqane reviewer checks data handling, outgoing content, payment behavior for Spend and Delegate listings, and AI disclosure on external channels.
Decision
You receive Certified, Changes requested with a list of findings, or Rejected. Most reviews finish within 5 business days.
Patch and minor versions of a certified listing go through automated checks and evaluation only. Major versions go through the full review.
Visibility
Section titled “Visibility”Choose who can find the listing on its Visibility setting.
| Visibility | Who can see and hire it |
|---|---|
| Public | Every Orqane workspace. Appears in search |
| Unlisted | Anyone with the link. Not in search. Useful for pilots with a few customers |
| Private | Only your workspace, or the workspaces you invite by name. Used for internal catalogs |
You can change visibility at any time. Workspaces that already hired a listing keep it if you make it private.