Clients & SDKs

Beyond MCP, you can drive a project programmatically.

REST

Every engine capability is a REST endpoint, reached through the gateway's /engine proxy and authenticated with a tr_sk_… key:

curl "$GATEWAY/engine/api/v1/ws/$WS/health" \
  -H "Authorization: Bearer tr_sk_…"

Responses use a uniform { ok, data, error } envelope. See the API Reference for authentication, the envelope contract, and the endpoint surface.

The root CLI

The open-source root CLI talks to an engine (local or remote) over the same REST API. It's ideal for scripting and local development:

root compile ./docs          # ingest + compile
root ask "what owns billing?" # grounded answer
root function deploy …        # manage Root Functions
root prompt list              # manage Compiled Prompts

See the CLI Reference.

Open-source SDKs

The engine, the root CLI, the desktop app, and the language SDKs are open source and live in the engine repository — the cloud consumes the same engine you can self-host. For the boundary between what's open and what the cloud adds, see Cloud vs Self-host.