HTTP Endpoints

The DriftQ-Core HTTP API surface.

DriftQ-Core exposes two main HTTP surfaces today: the stable /v1 broker API and a broad /debug/* runtime surface used for replay, governance, evals, and workflow inspection.

Note: /v1/consume streams responses as NDJSON until the client disconnects.

Stable broker API

This is the durable broker surface: health, topics, produce, consume, Ack / Nack, and related topic operations.

Health

GET /v1/healthz

Topics

GET  /v1/topics
POST /v1/topics?name=t&partitions=1

Produce

POST /v1/produce?topic=t&value=hello

Consume (streaming)

GET /v1/consume?topic=t&group=g&owner=o&lease_ms=5000

Response is NDJSON: newline-delimited JSON items streamed until the client disconnects.

Ack / Nack

POST /v1/ack?topic=t&group=g&owner=o&partition=0&offset=0
POST /v1/nack?topic=t&group=g&owner=o&partition=0&offset=0&error=some_reason

Runtime and orchestration debug API

DriftQ-Core also exposes a large /debug/* surface for running workflow specs, replaying runs, managing governance policies, inspecting artifacts, and operating the v3 runtime.

Mental model: /v1 is the stable broker API; /debug/* is the runtime and control-plane surface for the replayable workflow engine.

POST /debug/run-spec
POST /debug/run-replay
GET  /debug/evals/datasets
GET  /debug/policy
GET  /debug/risk-policy
GET  /debug/human/tasks
GET  /debug/agent-state
POST /debug/agent-memory/search
GET  /debug/tool-gateway
GET  /debug/tool-calls
GET  /debug/workflows/releases/versions
GET  /debug/self-heal/artifacts
GET  /debug/forensics/lineage
GET  /debug/replay/branches
POST /debug/brain/route

Exact route families may evolve, but this is the current surface area the core runtime ships today.