Control plane OpenAPI

The OpenCloud control plane specification is the canonical OpenAPI 3.1 contract for creating, building, deploying, verifying, and operating apps.

The contract is generated from the same typed operation registry used by:

• the standalone OpenCloud CLI; and
• the control-plane request and response validators.

The CLI uses the same operation IDs, paths, scopes, idempotency rules, and server-side validation as the control plane.

Development capabilities

Every development session returns the same exact capability vector. Frontend, database, Functions, background jobs, managed Files, and synthetic Auth are available. Cron and production secrets are not. There is no client-version negotiation or legacy shape to interpret.

Owner-authorized production diagnostics include retained background-job totals, per-queue depth and policy, cursor-paged execution metadata, and one-job detail. Those responses intentionally exclude payloads, idempotency keys, and enqueuing user identifiers. They expose no cancellation or redrive mutation.

Security boundary

The CLI may read a secret from its local environment for backwards compatibility, but generated and browser-entry secrets are preferred. It uploads local source into the server-side draft model before invoking the authoritative validator and deployer. Legacy owner-only lifecycle endpoints remain available to operators and older CLI releases.

Stable URLs

https://docs.opencloud.ai/control-plane-openapi.yaml
https://api.opencloud.ai

The app runtime OpenAPI is separate because it describes APIs available inside a deployed application.