DEVELOPERS

A focused contract for controlled execution.

Build around runs, state, events, and plugins without coupling external automation directly to interpretation logic.

correlation_id
run_id
status
events[]

STANDARD RUN CONTRACT

A small interface with an operational story.

Create a run, query its status, follow the event stream, and retrieve its history. Structured identifiers keep the initiating request connected to every transition.

Read the documentationExplore the source 
POST /v1/runs
GET  /v1/runs/{run_id}
GET  /v1/runs/{run_id}/timeline
GET  /v1/runs/{run_id}/stream

{
  "correlation_id": "corr_7a31",
  "run_id": "run_8f4c",
  "status": "awaiting_approval"
}

EXTENSION BOUNDARY

Keep execution behind plugins.

External tools, MCP servers, workflow engines, and automation systems are untrusted boundaries. Typed interfaces and versioned contracts constrain that crossing.

INPUT

Explicit action request

Validated context, identifiers, and workflow parameters.

BOUNDARY

Plugin interface

A defined executor contract between the control plane and external systems.

OUTPUT

Structured result

Status transitions and evidence represented as run events.

DOCUMENTATION PATHS

Move from contract to operating environment.

Use the documentation for current setup and integration details, then verify behavior against the repository source.

PRIMARY RESOURCES

Read the contracts. Inspect the implementation.

The documentation is the starting point for integration details; the repository is the source for current behavior.

DocumentationGitHub source