Quick Start
Purpose
Section titled “Purpose”The quick start helps technical buyers and integration teams move from capability discovery to a first approved API call.
External pressure
Section titled “External pressure”Integration projects often start with unclear ownership: which capability is relevant, which data is needed, and where execution boundaries sit. The quick-start path removes that ambiguity before technical work begins.
Three-step path
Section titled “Three-step path”1. Discover capabilities
Section titled “1. Discover capabilities”Start with the module pages. Each module states what it is for, which external pressure it makes visible, what data it may consume, what output it may expose, and what it does not do.
Recommended first read: Margin & Pricing Intelligence.
2. Confirm authentication
Section titled “2. Confirm authentication”Work with the CORTEX onboarding process to obtain tenant access, scopes and approved integration boundaries. Do not use undocumented routes or credentials.
3. Make the first API call
Section titled “3. Make the first API call”Use the approved API contract for the relevant module when a public API is available. If no public API is available, use the module page as capability reference and wait for the published OpenAPI contract.
Evidence boundary
Section titled “Evidence boundary”The quick start only describes the onboarding path. It does not certify that every module has a public API available today.
What it does not do
Section titled “What it does not do”It does not provide internal endpoints, private credentials, pricing terms or implementation details.