Make an unauthenticated or token-bearing GET request to {catalogBaseUrl}/v1/config, optionally passing ?warehouse={warehouseId} as a query parameter
Parse the response: the 'defaults' object contains properties the server sets as defaults; 'overrides' contains properties that must override client-side config
Merge overrides on top of defaults and then on top of client-supplied configuration to produce the final catalog configuration
Use the resolved 'prefix' value from the config response as the path prefix for all subsequent catalog API calls (e.g., /v1/{prefix}/namespaces)
Proceed to authenticate (if not already done) and list namespaces to confirm the catalog is reachable
Known gotchas
The 'overrides' map in the config response takes precedence over everything, including client config; ignoring it can cause misrouted requests or authentication failures
Some catalog implementations return a 'prefix' that is not the warehouse name — always use the prefix from the config response rather than deriving it from the warehouse identifier
The /v1/config endpoint is catalog-implementation-specific; not all implementations support multi-warehouse routing via the 'warehouse' query parameter
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp