ColomboAIDOCS
API ReferenceCookbook
Docs/MC-1 Security/Security service scope and billing
PublishedGuidanceLAST REVIEWED · 18 NOV 2026

Security service scope and billing

Agree one explicit Security scope without confusing a price, a license or an approval with permission to execute.

Runtime scope

Engineering preview; not live

Discuss an approved service contract. No public Security subscription price or self-service purchase is available.

There is no public self-service Security Checkout or newly published Security price. Discuss eligibility, service scope, capacity, retention, support, tax treatment and operating boundaries before activation.

One agreed managed service scope

The managed Security contract profile can cover both passive assessment and governed configuration correction. The passive-only assessment profile cannot authorize correction. Existing Core, Identity, Guard, Trust and other contracted charges must be explicitly accounted for; this platform presentation creates no additional subscription or duplicate charge.

Commercial authorization remains separate from current identity, ownership, policy, human review and deployment qualification. Paying for scope never enables an unqualified capability or permits a worker to approve its own action.

Billing loss preserves safety and evidence

Production execution requires current approved commercial scope and settled canonical funding. Provider events withhold stale access before reconciliation; a webhook snapshot does not grant an execution license. Refund, dispute and risk handling remain explicit.

Human stop, exact dispatched effect reporting, retained evidence retrieval and retention maintenance remain available under their own current access checks after license loss. No new write permission follows from those safety paths.

End of guide
Was this page helpful?
Security service scope and billing | MC-1 Docs