Konnect Catalog
Looking for Catalog Classic? See the Catalog Classic documentation.
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.
APIs
Create, discover, and govern APIs and specs. Catalog serves as a central repository for your APIs and the documentation files associated with them.
Use cases for Catalog
| Use case | Then use… |
|---|---|
| You need to know every API, AI Model, agent, and MCP server your org has built, without checking each team’s tools individually | 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 | 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 deployment, versus just defined on paper | 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 | 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 | 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 | API packages, 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 | Publish an API 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 for how to move to the new experience.
What happens to Integrations and Scorecards?
Integrations and Scorecards are compatible with 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.