All use cases
Data & analytics
Find which service owns the field before you model it
Search the catalog for the API, read its schema, see who owns it.
Before Fenwave4 days waiting
“Which service is the source of truth for customer_tier? I am seeing three different values in three tables”
What the wait costs
A model built on the wrong source, discovered after a report has already been circulated.
The catalog lists every registered API with its schema, its owning team and the components that consume it. Instead of asking around for the source of truth, you read the API reference and the dependency graph — and if the answer is genuinely ambiguous, you now know exactly which two teams to put in the same conversation.
How it works
- 01Search the catalog for the domain concept or the service name.
- 02Open the API entry; the schema and endpoints are generated from source.
- 03Read the owner and the consuming components on the same page.
- 04Follow the dependency graph if the ownership is shared.