Design direction

API CATALOG

Build an API catalog from authoritative contracts

Catalog entries should resolve to stored contracts, owners, environments, deployments, and audit evidence.

Last reviewed

The operating problem

An inventory becomes stale when it is detached from import, deployment, runtime ownership, or deprecation processes.

The intended control surface

This capability is part of the reviewed product architecture, not a decorative console module.

  • Cross-project discovery with permissions
  • Ownership and lifecycle metadata
  • Products, consumers, dependencies, and versions
  • Documentation quality and security findings

What exists today

Tenant-scoped API list/detail and normalized OpenAPI operation indexes are implemented. Cross-tenant discovery and product publishing are not.

Work with the implementation team

Reallexi is accepting architecture conversations with teams whose requirements can shape this production slice. An inquiry does not imply that an unshipped feature is available.

Frequently asked questions

Is this capability generally available?

No. The page describes a reviewed implementation direction. The current capability boundary is stated above and in the public changelog.

Can Reallexi evaluate our requirements?

Yes. Use the enterprise inquiry form without including credentials, private payloads, or regulated data.

NEXT STEP

Shape the requirements before implementation.

Talk to ReallexiRequest platform access