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

# Introduction

**Marketplace turns the APIs your organisation already runs into governed, discoverable products.** Connect any gateway, publish your APIs to a branded catalog, govern their quality, bundle them into subscribable products, monetize access, and watch how they are used.

It is a management plane, not a proxy. The marketplace reads from your gateways and runs the storefront, governance, subscriptions, and analytics around them, while live API traffic flows straight from consumers to the gateway. You reuse the gateways you already operate, with no migration and nothing new in the request path.

![Figure 1. Manage API Sources, where you connect the gateways and spec sources the marketplace reads from.](https://3824764996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6gIqo0LlXZlikuc0eKU2%2Fuploads%2Fgit-blob-b9b9a9d71daf54439e14853bd27bb64d9cd27a68%2Fmkt-apim-connections.png?alt=media)

## What you can do

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Connect &#x26; import</strong></td><td>Federate every gateway and spec source into one catalog.</td><td><a href="/marketplace/how-to-guides/features/feat-gateway-connections.md">Gateway connections</a></td></tr><tr><td><strong>Govern</strong></td><td>Score each API for security, style, and documentation before consumers see it.</td><td><a href="/marketplace/how-to-guides/features/feat-api-governance.md">API governance</a></td></tr><tr><td><strong>Publish &#x26; productize</strong></td><td>Move APIs to the catalog and bundle them into products and plans.</td><td><a href="/marketplace/how-to-guides/features/feat-publishing-apis.md">Publishing APIs</a></td></tr><tr><td><strong>Monetize</strong></td><td>Price access with plans, quotas, invoices, and payouts.</td><td><a href="/marketplace/how-to-guides/features/monetization.md">Monetization</a></td></tr><tr><td><strong>Operate</strong></td><td>Manage subscriptions, members, branding, and analytics.</td><td><a href="/marketplace/how-to-guides/administration.md">Administration</a></td></tr><tr><td><strong>Open to AI</strong></td><td>Expose APIs to agents as MCP servers and an API GPT assistant.</td><td><a href="/marketplace/how-to-guides/features/feat-mcp-servers.md">MCP servers</a></td></tr></tbody></table>

## How this guide is organised

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Concepts</strong></td><td>Understand the platform: what each capability is and why it matters.</td><td><a href="/marketplace/concepts/concept-foundations.md">Foundations</a></td></tr><tr><td><strong>How-to guides</strong></td><td>Step-by-step procedures for every surface, with field-level detail.</td><td><a href="/marketplace/how-to-guides/features.md">Features</a></td></tr><tr><td><strong>Reference</strong></td><td>Troubleshooting, FAQs, and a glossary of marketplace terms.</td><td><a href="/marketplace/reference/reference.md">Reference</a></td></tr></tbody></table>

{% hint style="success" %}
**New here?** Read the [Overview](/marketplace/overview.md) and follow [Getting started](/marketplace/getting-started.md) for your first day. Skim the [Concepts](/marketplace/concepts/concept-foundations.md) to build a mental model, then use the [How-to guides](/marketplace/how-to-guides/features.md) as you configure each surface.
{% endhint %}

{% hint style="info" %}
**Who this guide is for.** The API Provider and Portal Admin who run the marketplace day to day: you connect gateways, import and govern APIs, publish and productize them, approve subscriptions, monitor usage, and operate the administrative surfaces. The consumer-facing experience is documented in the Developer Portal guide.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digitalapi.ai/marketplace/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.