Loading…
Loading…
This page replaces the disabled API reference placeholder with a clear status map. Public package setup is open; product and deployment APIs remain scoped to authenticated workspaces or customer-specific rollout material.
The package-facing surfaces are documented from the library installation page and should use the canonical package names.
Workspace API keys and service accounts are managed in the signed-in product. Public docs do not publish every internal route shape.
Self-hosted, managed private, and contract-specific API boundaries are documented in private rollout material, not public marketing pages.
Public API documentation should help developers integrate without exposing internal route topology, anti-abuse thresholds, or deployment-specific security controls. More detail is provided during private technical review when it is relevant to a customer rollout.