Crate lex_api 

M8: agent API server. Spec §12.3.

HTTP/JSON server exposing the same operations as the CLI. The server is stateful (it owns a Store instance) so agents don’t pay sandbox startup cost per request.

Endpoints: POST /v1/parse { source } → CanonicalAst | [SyntaxError] POST /v1/check { source } → { ok: true } | [TypeError] POST /v1/publish { source, activate? } → [{ stage_id, sig_id, status }] GET /v1/stage/ → { metadata, ast, status } GET /v1/stage//attestations → { attestations: [Attestation] } POST /v1/run { source, fn, args, policy } → { run_id, output | error } GET /v1/trace/<run_id> → TraceTree POST /v1/replay { source, fn, args, policy, overrides } → { run_id, output | error } GET /v1/diff?a=&b= → Divergence | { divergence: null } POST /v1/merge/start { src_branch, dst_branch } → { merge_id, conflicts, … } POST /v1/merge//resolve { resolutions: […] } → { verdicts, remaining_conflicts } POST /v1/merge//commit → { new_head_op, dst_branch } | 422 conflicts remaining GET /v1/health → { ok: true }

Web (lex-tea v2, read-only HTML; human-only audit + triage): GET / → activity stream (recent attestations) GET /web/attention → exceptions queue (Failed / Inconclusive, stale merge sessions) GET /web/trust → per-producer rollup (pass rate, latest failure) GET /web/branches → branch list GET /web/branch/ → fns on a branch (detail) GET /web/stage/ → stage info + attestation trail (detail)

Modules

handlers

Request routing for the agent API.

mcp

Model Context Protocol server (#171).

Functions

serve

serve_mcp_stdio

MCP server (#171). Same State shape as the HTTP server, stdio transport instead of TCP. Designed for hosts that spawn lex serve --mcp as a subprocess and pipe JSON-RPC over stdin/stdout.

serve_on

Test/embedded entry: takes an already-bound Server and runs until it stops accepting requests. Returns immediately when the Server is dropped on another thread.