> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dataharbor.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Global Marketplace

> Publish governed Virtual APIs for discovery and monetization in the DataHarbor registry.

<Note>
  Global Marketplace is currently in **Preview**. Functionality may change.
</Note>

# Global Marketplace

**Make your data discoverable. Monetize it if you want.**

Publish governed Virtual APIs for discovery — free or per-request — with privacy rules that travel with every call. Partners and buyers browse listings, preview schemas, and request access through marketplace keys.

## Registry endpoint

The registry is the machine-readable index of all listed agents. It's live today:

```text theme={null}
https://service.dataharbor.co/api/registry/search
```

AI agents query the registry to discover governed endpoints ready for instant connection. Every Virtual API with **Listed Open** [visibility](../core/agents#listed-open) is automatically indexed.

For MCP-native discovery, clients can also start at:

```text theme={null}
https://service.dataharbor.co/mcp
```

The platform MCP endpoint is a discovery surface, not an anonymous data-access surface. Anonymous sessions can browse a narrow set of discovery tools, then configure auth when they want richer metadata or direct access to a specific Virtual API.

## How it works

1. **Create a Virtual API** — Define your source, apply privacy controls, and set access rules.
2. **Set visibility to Listed Open** — Your Virtual API must have [Listed Open](../core/agents#listed-open) visibility to appear in the registry and catalog.
3. **Buyers discover and connect** — Buyers browse listings, preview schemas, see governance policies, create a marketplace key from the account settings page, and connect.
4. **Authorize specific organizations** — As an alternative to public listing, data owners can authorize specific partner organizations for direct relay access via [Organization Authorizations](../core/api-access#organization-authorizations). Authorized orgs use their existing marketplace key — no new credentials required.
5. **Access flows through controls** — Every request goes through your Virtual API's governance. Usage is metered, logged, and auditable. Revoke anytime.

## Visibility requirement

Only Virtual APIs with **Listed Open** visibility appear in the Global Marketplace. This is the most open discovery setting — the agent card and registry listing are public, while runtime access still requires credentials such as marketplace keys for relay access or authentication for lease-scoped MCP.

| Visibility      | In Registry | In Catalog |
| --------------- | ----------- | ---------- |
| Disabled        | No          | No         |
| Private         | No          | No         |
| Unlisted Open   | No          | No         |
| **Listed Open** | **Yes**     | **Yes**    |

To configure visibility, see [Agent Visibility](../core/agents).

## Agent Catalog

The Global Marketplace makes your data discoverable to humans. The Agent Catalog makes the same listings discoverable by machines — programmatically, via the A2A protocol.

* **Agent discovery** — Every listed Virtual API auto-generates a standards-compliant A2A agent card. Zero-config discoverability.
* **Agent-to-agent access** — Agents query, discover, and negotiate access to your governed data through the registry.

Generated discovery metadata reflects your current control configuration. Transform-only outputs are described as transformed rather than raw access, and cleanup controls such as `delete` do not advertise fields that are removed from the final response shape.

## Use cases

| Use case                   | Description                                                                    |
| -------------------------- | ------------------------------------------------------------------------------ |
| **Data monetization**      | Turn proprietary datasets into revenue streams with free or per-request access |
| **Partner data exchange**  | Share tokenized or redacted data with partners without losing control          |
| **AI-ready endpoints**     | List MCP-enabled Virtual APIs in the live registry for AI agent discovery      |
| **Industry data networks** | Participate in vertical-specific exchanges with anonymized benchmarks          |

## Governance travels with data

Every marketplace consumer is bound by your Virtual API's controls:

* Privacy controls (tokenization, redaction) are enforced on every call
* Access controls (geo restrictions, expiration) apply
* Marketplace relay requests use marketplace keys (`mkp_...`)
* Organization authorization relay usage is billed against the consuming organization's marketplace quota — not the data owner's
* Usage is metered, logged, and auditable
* Revocation is instant

## Next steps

<CardGroup cols={2}>
  <Card title="Agent Visibility" icon="eye" href="../core/agents">
    Configure how listed Virtual APIs are discovered
  </Card>

  <Card title="Private Marketplace" icon="building" href="./private">
    Internal data catalog
  </Card>
</CardGroup>