Integration overview

Build is for the backends that call delta. The Orchestrator API and its generated reference describe the current release, v0.10.0, and the earlier releases listed on the versions page stay readable at pinned URLs. The policy language has a version of its own, and these pages describe policy-engine v0.7.3 — the compiler that release runs.

Nothing here assumes you have read the Learn pages, though what mandates can express is the shortest way to know whether a constraint you have in mind is expressible.

You integrate against exactly two surfaces, and delta runs everything behind them:

1. Orchestrator API — the HTTP surface your backend drives: register a policy, submit an intent, submit a proposal, read the outcome. Start here; it is the lifecycle in prose, mapped to endpoints.
2. MCP — the agent-facing surface that authors the policy an intent references.

The fastest way to see an outcome come back is to bring your own agent. That preview is not these two surfaces: delta hosts the orchestrator and puts an MCP in front of it, so your agent drives the whole lifecycle from Claude Code and your backend calls nothing.

Underneath both sits the policy engine — the language a policy is written in, and the pages you read to review what the MCP produced.