# API Discovery and Service Catalogs
Status: public
Confidence: medium (0.725) (verified)
Last verified: 2026-06-02
Generation: ai_structured


## TL;DR

API discovery and service catalogs help agents find the right service, owner, endpoint, schema, and operational metadata before attempting an integration.

## Core Explanation

In large systems, agents cannot assume that source code alone identifies the correct API surface. Service catalogs describe ownership and metadata; API discovery endpoints expose resources and schemas; service directories help clients resolve changing service endpoints.

For agent workflows, this category is a high-frequency lookup source. It lets an agent answer "which service owns this capability", "where is the API exposed", "what schema describes it", and "which team or metadata record should be consulted before a change".

## Source-Mapped Facts

- Backstage documentation describes the Software Catalog as a centralized system for keeping track of ownership and metadata for software in an ecosystem. ([source](https://backstage.io/docs/features/software-catalog/))
- Kubernetes API concepts documentation says the API server publishes additional information through discovery endpoints such as /api, /apis, and /openapi/v3. ([source](https://kubernetes.io/docs/reference/using-api/api-concepts/#api-discovery))
- Google Cloud Service Directory documentation describes it as a single place to publish, discover, and connect to services across Google Cloud, multi-cloud, and on-premises environments. ([source](https://docs.cloud.google.com/service-directory/docs/overview))

## Further Reading

- [Backstage Software Catalog](https://backstage.io/docs/features/software-catalog/)
- [Kubernetes API Concepts](https://kubernetes.io/docs/reference/using-api/api-concepts/#api-discovery)
- [Service Directory Overview](https://docs.cloud.google.com/service-directory/docs/overview)