Continual/Docs
⌘ K

Project APIs

Direction

Use one governed backend contract from apps, people, and agents.

A project backend publishes the Company Runtime as one typed contract. Apps use HTTP APIs designed for application development. Agents use MCP for discovery and invocation. Both reach the same objects, tools, rules, permissions, and audit path.

One contract, two protocols

HTTP and OpenAPIPredictable application APIs, generated clients, webhooks, and ordinary request tooling.
MCPDynamic discovery and invocation for Continual and external agents.

MCP is not the transport for every frontend. It complements the HTTP contract instead of replacing it.

Object and tool metadata

The backend also publishes structured metadata for objects, interfaces, tools, metrics, and documents. Continual uses that metadata for generic browsers and management views. Custom apps may use it too, but remain free to build purpose-specific interfaces.

Authorization

Protocol does not grant authority. Every request carries an actor and a project scope. The backend evaluates business authorization and approval policy before reading data or invoking a tool, then records material effects as events.