The contract is MCP.

Three surfaces, all three stable, all three documented here: the MCP server, the kastel command, and the export format.

All three are part of the open interface: the protocol, the schema, the export format and the connectors are published under Apache-2.0. You can build on them without asking us, and without touching the engine.

The hosted console has no public API. The HTTP routes it calls are its own backend: they authenticate through the signed-in person's session, there is no API key, they are not versioned and we make no stability promise about them.

We do not document them, and that is a choice rather than an oversight: documenting them would promise a contract we do not keep. An integration built on them would break at the first screen change.

• Read your company's context from a program. The MCP server over HTTP, with an access carried in the Authorization header. It is the same contract your AI reads.
• Automate an operation. The kastel command: ingestion, access, governance, export. It exposes everything the engine does.
• Take your data out. kastel export produces a portable archive whose format is published in the open interface. Nothing holds you.

Write to us and describe what you want to automate. We announce no date: we would rather promise nothing than publish a surface we would have to break.

Hand-written page, reviewed on 2026-08-23. The three other pages of this rubric are generated.