Konnect Catalog Classic

A centralized catalog of all services running in your Konnect organization

You’re viewing the Catalog Classic docs. To see the new Catalog experience, see the Catalog documentation.

What is the Konnect Catalog Classic?

Catalog Classic provides a centralized catalog of all services and APIs running in your organization. By integrating with internal applications, like API Gateway and Service Mesh, and external tools, like GitHub and PagerDuty, it offers a 360-degree overview of your services, including:

Service ownership details
Upstream and downstream dependencies
Associated code repositories and CI/CD pipelines
API gateway and service mesh mappings
Comprehensive API and MCP server catalog

Create your catalog

APIs

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

APIs reference → API packages → Create an API catalog with the Konnect API → Create an API catalog with Terraform → Discover and govern APIs →

Services

Discover the systems that power your APIs—like microservices or backends—and centralize them for a complete view of your API infrastructure.

Learn about Catalog services →

MCP Registry (tech preview)

Discover and connect MCP servers to Konnect Catalog.

Enable in Konnect Labs. →

Explore more features

Integrations

Connect external tools like GitHub, PagerDuty, and CI/CD pipelines to map services, dependencies, and metadata.

See all integrations →

Scorecards

Monitor compliance, security, and best practices across services using automated scorecards.

Learn about scorecards →

Migrate to the new Catalog

The new Catalog experience is a unified, platform-level home for your interfaces. Here’s how it compares to Catalog Classic:

AI Models: The new Catalog adds support for AI Models as a first-class interface. You can opt to link these to AI Gateway 2.0 AI Model entities.
Agents (beta): The new Catalog introduces Agents as a first-class interface. You can opt to link these to AI Gateway 2.0 AI Agent entities.
Continued support for APIs, API packages, and MCP Registries: APIs, API packages, and MCP Registries (tech preview) work the same way in both experiences. APIs and API packages migrate over.

Services, Scorecards, and Integrations are only compatible with Catalog Classic.

An Org Admin can migrate to the new Catalog experience by enabling the New Catalog in Manage organization > Settings > Catalog.

Your APIs and API packages migrate to the new Catalog. Services, Scorecards, and Integrations data isn’t deleted, but becomes inaccessible in the UI after migrating. You can still manage these and access their data by using the API.

Frequently asked questions

How do I view service health and status?

Go to Services in Catalog Classic and select a service to view detailed health and status information.

How can I identify available resources for mapping?

Visit the Resources page in Catalog Classic to see all available ingested resources.

What if I notice discrepancies in Catalog data?

Check integration settings, verify connected tools, and ensure data synchronization is working correctly.

Can I control access to specific Catalog data?

Yes, access can be managed through teams and roles.