API edge boundaries
Use the customer-approved API edge at {{API_BASE_URL}}/v1/... only when your onboarding and Connection Profile documentation explicitly enables the requested capability. The API edge applies the customer credential, scopes, quota and usage policy before requests reach product services.
Do not call internal services
Do not call internal service hosts, ports, administrative routes or service-token endpoints. Do not send organisation or tenant headers to try to select a different boundary. The authenticated customer credential and approved profile determine scope.
Capability families
A configured edge can provide customer-facing capability families for knowledge, search, AI optimization, model access, product MCP, external MCP federation, workflow, communication, storage, CMS and other enabled services. Exact path, request schema, response schema and availability must come from the relevant approved contract or profile connect information.
OAuth and programmatic identity
Where a customer has approved OAuth machine-to-machine access, use the onboarding-supplied client registration and scopes. Do not treat an internal identity verifier, tenant administration route or service token as a public integration flow.