Skip to main content

Ontology & SDKs

There are three programmatic ways into System9 beyond the wire protocols and REST: generated SDK clients, the agent-tool (MCP) surface, and semantic-model emitters. All three carry the same identity, policy, and audit as a console click.

Direction: both. Status: Partial. The available surfaces are named below.

SDK clients generated from the ontology​

The ontology, the object, link, and action types that define a workspace's world model, is the source of truth for programmatic clients. SDK emitters generate OpenAPI, Python, and TypeScript clients from that ontology, so an application speaks the workspace's own model rather than a generic API. An ontology subset also synchronizes to edge devices, so capture-point extraction uses the same model as the core.

Because the client is generated from the ontology, it stays in step with the model as the model evolves, and every call it makes still resolves through the governed plan on the server side.

A generated OpenAPI client, or any tool that consumes an OpenAPI document, reads the node's served, curated spec at GET /api/public/v1/openapi.json (browse it interactively at /api/public/v1/docs). That document is deny-by-default and carries each operation's status. See the Public API reference and API conventions.

The agent-tool (MCP) surface​

A cell serves an agent-tool surface speaking the Model Context Protocol, an information endpoint, a JSON-RPC endpoint, and an SSE stream, exposing the platform's measured agent tools. An MCP-capable client reaches governed platform capability as tools rather than as raw API calls, with the agent's workspace scope carried through. The platform also ships an outbound MCP client, so an agent can consume an external MCP server's tools under the same governance.

Alongside it, an agent-to-agent surface publishes a signed agent card with its own JWKS and accepts tasks, so another organization's agent can be registered, cryptographically identified, and given a scoped, audited, refusable seat. See Tools & MCP.

The MCP surface is on by default

The MCP router mounts with the protocol enabled by default and is not exposed as an operator toggle in the shipped configuration, worth noting in a security review. Read tool availability as reach, not as agent-governance assurance; agent governance is a separate plane.

Semantic-model emitters​

For business intelligence, the platform emits native semantic models, tabular BI models, dashboards, and best-practice analysis, as open-format files a reporting tool imports. This outbound path is a governed chokepoint: a publish, refresh, or export is deny-by-default, must clear the value gate, and its egress is checked before any byte leaves. See Reporting & BI.