One3 Ecosystem · Module
Marketplace
Find, check and install governed Packs, agents, connectors and MCP servers
The Marketplace is where tenants will discover, evaluate, install and pay for third-party and first-party extensions. Every listing shows a permission diff generated from its signed manifest before anything is enabled.
The Marketplace is planned as the storefront of the One3 Ecosystem. It is sold on a revenue-share basis: the tenant pays the listing price and One3 keeps a published take-rate. It is eligible from W2 in the catalog, with an invited-partner alpha scheduled for Year 2 H2. In Year 1, the first-party Digital Employee Store in AI Workforce is the substitute.
What you can install
Listings cover Packs (apps), agent templates, workflow and automation templates, snapshots and tenant templates, connectors, MCP servers, dashboard and report packs, design and content templates, and partner services such as implementation, migration and training. Third-party rentable Digital Employees appear here with their KPIs and certification level, and the "Rent" button hands off to the AI Workforce rental flow.
How an install works
- A user requests a listing with a business reason.
- The entitlement engine checks plan, modules and kernel version, and shows "requires module X" when something is missing.
- Approvers see the permission and risk panel: objects and fields read or written, Actions with risk tiers and reversibility classes, data classifications, egress domains, MCP tools and agent autonomy ceilings. This is generated from the signed manifest, not from marketing copy.
- On approval, a rollback point is created, the artifact signature is verified and the listing's Actions are registered with the kernel under a scope ceiling.
- Paid plans create an order and a line on the tenant's single One3 invoice.
What is different
- Outcome evidence over stars. Listing pages show install-to-active rate, task success, reverse rate, uptime and SLA adherence, or "insufficient data" when the sample is small. Ranking uses a published formula with no paid override.
- No silent scope creep. Any update that adds scope, egress or risk needs re-consent while the current version keeps running.
- Kill switch. One3 and tenant admins can disable a listing instantly; its Actions stop and in-flight approvals are voided.
- Same rules for One3. First-party listings are labelled "by One3" and pass the same review and ranking.
- Agency tools. Agencies can install or update a listing across selected client sub-accounts, with consent inherited only where each sub-account's policy allows it.
Features
What Marketplace includes
Listing types
Packs, agent templates, workflow templates, snapshots, connectors, MCP servers, dashboard packs and design or content templates, each with a type-specific manifest and runtime.
Services listings
Implementation, migration, training and managed-service offers from verified partners, with scope, deliverables, pricing model and linked certifications.
Rental Digital Employee listings
Third-party rentable agents shown with role, KPIs, certification level, Eval Coverage Score and simulator results; renting hands off to the AI Workforce trial and contract flow.
Entitlement-aware search
Keyword and semantic search whose results say "works with your subscription", "requires module X" or "requires plan Y".
Permission and risk panel
Objects, fields, Actions with risk tiers and reversibility classes, data classes, egress domains, MCP tools and scheduled jobs, generated from the signed manifest.
Outcome and reliability panel
Install-to-active rate, task success, reverse rate, error rate, uptime, SLA adherence, incident history and refund rate, with "insufficient data" for small samples.
Install request and approval
Users without install rights request a listing with a reason; approval policy can depend on certification level, scope risk and cost.
Sandbox trial install
Try a listing in a synthetic-data sandbox tenant before production and see a summary of the trial.
Update policy and re-consent
Patch updates apply automatically, on a schedule or manually; any increase in scope, egress or risk requires re-consent while the current version keeps running.
Uninstall with data disposition
See the data a listing created and choose keep read-only, export or delete after retention; dependent automations and agent skills are paused and listed.
Organisation catalogue policy
Allow-lists, block-lists, category bans and auto-approve rules, such as free Verified listings with low-risk scopes only.
Agency bulk install and update
Install, update or uninstall a listing across chosen client sub-accounts with a per-client results report.
Kill switch and security advisories
Instant disable by One3 or the tenant admin, plus advisories pushed to installing tenants with severity, affected versions and remediation.
Verified reviews and outcome-weighted ranking
Reviews only from verified installs with minimum usage; ranking uses a published factor list with no paid override.
Workflow
Submission, review and publish
- 1
Publisher submits a listing version with a signed artifact and manifest
- 2
Automated checks run: signature, manifest schema, static analysis, dependency CVEs, secrets, malware, licence and prompt-injection patterns
- 3
Scope analysis compares requested and used Actions, egress and data classes
- 4
Contract tests run against supported kernel versions, plus an eval pack for agents
- 5
Light or deep human review depending on risk class
- 6
Private release to publisher test tenants, then opt-in beta, then public catalogue
- 7
Continuous anomaly monitoring, advisories and re-review on major version or scope increase
Workflow
Install with permission diff
- 1
Tenant user requests an install with a business reason
- 2
Entitlement engine checks plan, modules and kernel version
- 3
Approver reviews the permission diff, cost and risk in the Approvals Inbox
- 4
Install service creates a rollback point and verifies the artifact signature
- 5
Kernel registers the listing's Actions, objects, views and jobs under a scope ceiling
- 6
Paid plans create an order and a subscription item on the One3 invoice
- 7
Post-install checks run and the listing appears in the installed-listings inventory
AI
AI skills and Digital Employees
Recommendations from goals and stack
Suggests listings from tenant goals, subscribed modules, industry and failed searches, explains why, and never installs anything by itself.
Permission-diff plain-language summary
Explains the authoritative permission table in plain words beside it.
Update impact summary
Describes what an update changes for this tenant, from the changelog and the tenant's own usage.
Comparison assistant
Normalises differing listing claims into comparable rows and says what could not be compared.
Copilot and MCP discovery
Answers questions like "is there a connector for Tally" across listings and MCP servers.
Digital Employees that use this module
- AI Agent Governance Auditor
- AI Access Reviewer
- AI Technical Writer
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Is the Marketplace available in Year 1?
No. It is eligible from W2 in the catalog, with an invited-partner alpha planned for Year 2 H2. In Year 1 the first-party Digital Employee Store in AI Workforce is the substitute.
How do I know what a listing can access?
Before install you see a permission diff generated from the listing's signed manifest: objects, fields, Actions with risk tiers and reversibility classes, data classes and egress domains.
What happens when a listing asks for more permissions?
Any increase in scope, egress or risk requires re-consent. The current version keeps running until you decide.
Can paid placement push a listing up the rankings?
Ranking uses a published formula with no paid override. Paid placement is only an open decision and, if ever approved, would be labelled and never override trust thresholds.
How are marketplace purchases billed?
Paid listings are planned to appear as lines on the tenant's single One3 invoice. Publisher payouts go through licensed payout partners.
See Marketplace in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.