- Provider ownership identifies the organization that operates a provider and its capabilities.
- Partner status records optional registration and commercial standing. Owning a private provider does not automatically make an organization a registered Partner.
- Client connections record the client’s request and authorization, the provider’s acceptance, validation, activation, quarantine, and binding revocation as distinct facts.
Read the fleet projection
Use the authenticated endpoint that backs the page:windowHours defaults to 168 and accepts values up to 720. It controls the observation window used for source-level call and failure metrics.
The response groups explicitly bound client sources under the provider capability they use:
The example shortens some nested objects for readability. Treat the API response as the source of truth for nullable lifecycle fields.
projection.rowLimit. When projection.truncated is true, the page warns that its per-capability source totals are partial rather than presenting them as complete.
Interpret health safely
Health is computed per bound inventory source from that source’s observations. A healthy sibling does not hide another source’s failure, and the creative canary assertion does not become a general fleet-health badge. Errors expose a safe code, summary, owner (CLIENT, PROVIDER, or SCOPE3), and an optional correlation reference for provider-owned remediation. Client-owned and Scope3-owned lifecycle details remain generic in the provider view; their raw summaries and correlation references are not returned. The projection does not return credentials, raw upstream payloads, or inventory belonging to unrelated clients. Missing provider acceptance and malformed certification evidence fail closed.
An administrator can use the corresponding inventory-source diagnostics view to confirm which capability a source is mapped to, whether the provider accepted it, and whether the connection is active or quarantined.