---
title: "Konnect Catalog"
description: Learn how to create, discover, and govern the interfaces your organization
  publishes and consumes with Konnect Catalog.
url: "/catalog/"
canonical_url: "/catalog/"
content_type: landing_page
products:
- Catalog
tags:
- governance
canonical: true


---






# Konnect Catalog

A platform-level home for the interfaces your organization publishes and consumes

> Looking for Catalog Classic?
> See the [Catalog Classic documentation](/catalog-classic/).



## What is Konnect Catalog?
Teams build APIs and configure AI models independently, each in their own tools, with no shared record of what already exists.
An API might be well documented within its own team, but invisible to everyone else.
An LLM integration might work fine until someone in security asks which providers you're actually sending data to, and there's no fast way to answer.

Catalog is where these interfaces live instead: APIs, AI Models, and more. Instead of digging through individual products
to find what already exists, Catalog gives you a
platform-level home for creating, describing, and governing them.

<!-- TODO: add screenshot of the Catalog view -->




## Create your catalog



## APIs

Create, discover, and govern APIs and specs.
Catalog serves as a central repository for your APIs and the documentation files associated with them.



* [APIs reference](/catalog/apis/)

* [Create an API catalog with the Konnect API](/how-to/automate-api-catalog/)

* [Create an API catalog with Terraform](/how-to/automate-api-catalog-with-terraform/)



## API packages

Compose API packages from existing operations to serve specific partners or use cases.


[API packages reference](/catalog/api-packaging/)


## AI Models

Model your organization's AI models as first-class interfaces in Catalog.


[Learn about AI Models](/catalog/ai-models/)


## MCP servers

Model individual MCP servers as first-class interfaces in Catalog.


[Learn about MCP servers](/catalog/mcp-servers/)


## MCP registries (tech preview)

Register and discover MCP servers as first-class interfaces in Catalog.


[Learn about MCP Registries](/catalog/mcp-registry/)


## Agents (beta)

Register agents your organization builds or consumes as first-class interfaces in Catalog. 


[Learn about Agents](/catalog/agents/)


## Use cases for Catalog

### You need to know every API, AI Model, agent, and MCP server your org has built, without checking each team's tools individually


- **Then use...**: Catalog as one inventory across APIs, API packages, AI Models, MCP servers, and agents


### Before building a new LLM integration, you want to check whether another team already has one you can reuse


- **Then use...**: [AI Models](/catalog/ai-models/), browsable with their providers and target models visible


### You need to see which AI Models are actually connected to a real [AI Gateway 2.0](/ai-gateway/) deployment, versus just defined on paper


- **Then use...**: Filter AI Models by whether they're linked to AI Gateway 2.0


### Your teams are building MCP servers for AI agents, but they're scattered across repos and local configs with no shared place to register them


- **Then use...**: [MCP servers](/catalog/mcp-servers/), where you publish MCP servers with their packages and remote endpoints


### Your teams are building agents across different frameworks, with no shared place to see what already exists and whether it's safe to reuse


- **Then use...**: [Agents](/catalog/agents/), inventoried alongside APIs, AI Models, and MCP Registries


### A partner or internal team needs access to a specific slice of your APIs, not everything, without creating separate infrastructure for it


- **Then use...**: [API packages](/catalog/api-packaging/), composed from existing API operations for that audience


### You want developers to register their own applications and get credentials for an API without provisioning each one manually


- **Then use...**: Publish an [API](/catalog/apis/#publish-your-api-to-dev-portal) to a Dev Portal with an authentication strategy





## Frequently asked questions


- What's different between Catalog and Catalog Classic?
  Catalog is the unified, platform-level experience for APIs, API packages, AI Models, MCP servers, Agents (beta), and MCP registries (tech preview) today, with more interface types coming. Catalog Classic remains available with Services. See [Migrate to the new Catalog](/catalog-classic/#migrate-to-the-new-catalog) for how to move to the new experience.

- What happens to Integrations and Scorecards?
  Integrations and Scorecards are compatible with [Catalog Classic](/catalog-classic/) today. Kong plans to bring them into the new Catalog experience in the future, with a focus on APIs and AI interfaces rather than Services.

- Can I control access to specific Catalog data?
  Yes, access can be managed through [teams and roles](/konnect-platform/teams-and-roles/).