Platform API
Developer previewProgrammatic access to Continual's control plane.
The platform API manages Continual's control plane: workspaces, projects, branches, deployments, memberships, roles, and other platform resources. It is distinct from each project's MCP interface, which publishes the backend to people through apps and to the Continual agent and external agents through governed tools.
The Continual app and CLI are ordinary platform API clients. Neither has a private path.
Every resource follows the same shape:
| Operation | Meaning |
|---|---|
create | Create one. |
get | Read one by ID. |
list | Page through them, with filters. |
update | Patch one. |
delete | Remove one. |
Reads are scoped to what your identity can see: a resource you may not read is indistinguishable from one that does not exist.
Platform and project APIs
The platform API manages the control plane. A project’s generated tool and MCP contracts operate the Company Runtime. Keep these APIs separate: one manages projects and releases; the other performs business work under the project’s rules.
Resource operations
Resources use predictable create, get, list, update, and delete operations where each operation is supported. Pagination, filtering, and generated reference will be documented alongside the resource rather than hidden in a generic page.
Access and errors
Identity and membership determine which resources are visible. A resource the caller cannot read should not leak whether it exists. Errors should include a stable code, a useful message, and enough request context to diagnose the failure without exposing secrets.