API Overview

The Clinia Context Engine exposes two API surfaces backed by the same underlying data:

• REST API, for server-side integrations, dashboards and ingestion. Each operation has a page under REST, grouped by tag. The sessions endpoints follow the lifecycle in Sessions. The graph endpoints read the patient graph directly, as Audit the Patient Graph shows, and are all Technical preview.
• MCP server, for AI agents. MCP Server covers connecting and the tools it exposes; Connect an AI Agent walks through wiring them to a model.

Base URL

https://<workspace-id>.w.clinia.cloud

Replace <workspace-id> with your workspace identifier.

OAuth scopes

Every endpoint declares the scope it requires, read or write, on its reference page. Authentication and Credentials explains how a credential's access level sets its scopes and what to do when a call returns 403 insufficient_scope.

API stability

The /v{n} prefix does not indicate stability. Every endpoint declares a tier, published as x-state on its operation in the OpenAPI spec:

• Generally available — breaks only at a new version prefix.
• Technical preview — promises nothing. It may change or disappear in any release, including a patch.
• Deprecated — still works, unchanged, and will be removed in a future release.

Anything other than generally available sends a runtime warning header:

Warning: 299 ContextEngine-1.4.0 "Deprecated: this endpoint will be removed in a future release."

MCP server stability is never guaranteed; its tools are optimized for agents and change with the product.