> For the complete documentation index, see [llms.txt](https://docs.mediafier.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediafier.ai/partners/marketplace.md).

# The Marketplace

Composable governed resources under one enforcement chain, from first-party tools to partner-published listings.

> **Composable, AI-native governed resources that make the customer's existing media systems agent-addressable.** The Marketplace is where new tools, capabilities, MediaClaws, skills, and integrations ship into the platform, and where the customer's catalog of governed resources grows over time.

***

## What the Marketplace is

The Marketplace is the discovery and governance surface for every governed resource any organization can turn on inside Mediafier — MCP-servers, CLI-based tools, Skills, MediaClaw super-agents, workflows, and other invocable surfaces. Each listed resource is:

* **Authored** by a tool publisher (internal team, partner, or third party).
* **Verified** through Mediafier's onboarding process (identity, ownership, billing setup).
* **Listed** in the Marketplace once approved, with a structured capability description.
* **Installed** per organization — listing visibility is platform-wide, but execution requires explicit installation and binding by an org admin.
* **Commercially classified** according to its Offering. Some tools are metered; BYOK and OAuth offerings use customer-provided credentials without Mediafier provider-usage metering.

The Marketplace is where the catalog of governed resources available to customer agents grows over time: operators discover and adopt new capabilities from the catalog; publishers ship into the catalog under the platform's governance contract.

***

## How operators use the Marketplace

A typical adoption flow:

1. Browse listed resources by capability or domain.
2. Read the published capability description and surface contracts — what each resource exposes, what each surface's input and output shape is.
3. Click install. The platform binds the resource to the org under the org admin's authority.
4. Bind credentials (where the resource requires them) through the org's credential vault. Credentials never leave the vault scope.
5. Hand the org's agents the new tool surface — discovery picks it up automatically.

After installation, the resource's surfaces are reachable from any of the platform's entry points (agent-first CLI/MCP, Slack/Teams, Pippa chat) and governed by the same gateway chain as any first-party capability.

***

## How tool publishers use the Marketplace

Publishing a governed resource is a controlled path:

1. Build the resource against the platform's spec — endpoints, schemas, capability descriptions.
2. Submit for review. The platform verifies the contract, identity, and billing setup.
3. Once approved, the resource is listed. Listing makes it discoverable org-wide; installation remains per-org.
4. Earnings accrue on a per-call basis through the platform's Marketplace economics. (See [Provider Earnings & Marketplace Economics](/partners/provider-earnings-and-marketplace-economics.md) for the full split, ledger semantics, and clearing model.)

The publishing orientation is on [Publishing to Mediafier's Marketplace](/partners/publishing-to-the-marketplace.md); detailed specs, schemas, and the certification checklist arrive with the qualified partner onboarding packet after [requesting access](https://mediafier.ai/request-access).

***

## What tool publishers control

Publishers choose how their resource appears in the catalog and who can install it. Two independent control axes:

### Visibility

* **Listed.** The default. The resource appears in the Marketplace catalog; any organization on the platform can discover it through the standard browse and search surfaces.
* **Unlisted.** The resource is installable but does not appear in the catalog. Useful for private partnerships, early-access pilots, or organization-specific integrations that aren't intended for general distribution. Discovery happens through a direct reference the publisher shares.

### Access

* **Public.** Any org admin can install the resource into their organization, subject to the platform's standard onboarding and credential-binding flow.
* **Allowlist.** The resource is installable only by organizations the publisher has explicitly authorized. The platform enforces the allowlist at install time; orgs outside it cannot bind the resource even if they discover it.

The two axes combine freely. A publisher can ship a listed + public-install resource (the default growth path), a listed + allowlisted resource (the catalog signals it exists, but installing requires publisher approval), an unlisted + public-install resource (anyone with the reference can install), or an unlisted + allowlisted resource (fully private to a named set of orgs).

Visibility and access are publisher-controlled and changeable at any time; the platform applies the current setting at the next discovery refresh and the next install attempt. Listing approval gates first publication; ongoing visibility and access decisions stay with the publisher.

***

## What the Marketplace governs

Every listed resource is bound by the platform's standard contract:

* **Discovery is governed**: the platform decides what an org sees.
* **Execution follows the approved integration model**: Mediafier supports multiple integration models, and every model runs through the same governed access, metering, and audit contract. Provider-operated integrations execute in the provider's runtime.
* **Identity is platform-side**: the gateway resolves the caller's identity and hands the resource a principal. The resource doesn't see the raw token.
* **Credentials are gateway-injected**: when a resource needs upstream API credentials, the gateway resolves and injects them from Mediafier-managed credential stores. The resource receives ready-to-use credentials per call and works against a single source of truth for credential resolution.
* **Audit is inherited**: every call to a Marketplace resource produces the same audit row, the same trace ID, the same evidence as a first-party capability.

The Marketplace contract is uniform across every listing. The same governance contract that fronts first-party capabilities fronts Marketplace capabilities, so the customer's security team reviews one chain regardless of who shipped the resource.

***

## Why the Marketplace matters for customers

A media organization adopting Mediafier doesn't have to wait on Mediafier's roadmap to reach a new system. As tool publishers ship resources for the systems the customer already uses, those systems become agent-addressable inside the platform. The customer's first day on the Marketplace is the smallest catalog they will ever see.

Two practical effects:

* **Wider agent reach over time.** Every new listed resource becomes installable — no per-system integration project on the customer's side.
* **Consistent governance across systems.** The same enforcement chain applies to every listed resource, regardless of who shipped it.

***

## What the Marketplace is not

* It is not a free directory. Listed resources are reviewed and approved.
* It is not autonomous. Listing is platform-wide; installation is per-org and admin-controlled.
* It is not a way to bypass identity, billing, or audit. Every call goes through the same gateway as a first-party capability.

***

## Where to go next

| If you're…                                        | Read next                                                                                             |
| ------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Looking for an architectural overview             | [Platform Architecture](/platform/platform-architecture.md)                                           |
| Building a resource to publish                    | [Publishing to Mediafier's Marketplace](/partners/publishing-to-the-marketplace.md)                   |
| Looking at Marketplace economics for publishers   | [Provider Earnings & Marketplace Economics](/partners/provider-earnings-and-marketplace-economics.md) |
| Connecting your existing tools without publishing | [MCP Access](/connect/mcp-access.md)                                                                  |