final_decision. Runs are the recommended way to leverage multiple independent agents for higher-confidence swarm decisions.
POST /api/run/submit
Submits aRunSubmitSpec and registers the run in the queue. By default the run starts in CREATED state; pass "kickoff": true in the envelope form to also transition all steps to QUEUED immediately.
RunSubmitSpec object or wrapped in an envelope:
JSON inputs shared across all agent steps in the run.
POST /api/run/kickoff/:run_id
Transitions the run and all its constituent steps fromCREATED to QUEUED, making them eligible for executor pickup. Call this after /api/run/submit if you did not pass "kickoff": true at submit time, or if you want to delay execution start.
GET /api/run/watch/:run_id
Polls the current status of a run, including step-level counts broken down by state. Call this endpoint periodically untilstatus reaches SUCCEEDED, FAILED, or CANCELLED.
Step-level counts by state.
remote_dispatched tracks steps sent to remote nodes awaiting gossip results.GET /api/run/result/:run_id
Returns the aggregated final result of a completed run, including the final decision, final answer, and per-step conclusions.List of resolution strategies that were applied (e.g.
"quorum_match", "confidence_weighted", "stochastic").GET /api/run/events/:run_id
Returns the structured event log for a run. Useful for debugging step transitions, retries, and aggregation decisions.POST /api/run/cancel/:run_id
Cancels an active run. Any steps inQUEUED or CREATED state are moved to CANCELLED. Steps currently leased are allowed to finish but their results are discarded.
POST /api/run/retry/:run_id
Retries a failed run by re-queuing its failed steps from the beginning. Steps that already succeeded are not re-executed.POST /api/knowledge/export
Exports a knowledge bundle from the kernel store. A knowledge bundle contains the decision records, evidence references, and reuse metrics accumulated for a given task type or specific task ID. Provide exactly one oftask_type or task_id.
Export all knowledge records associated with this task type string (e.g.
"generic.qa.v1"). Mutually exclusive with task_id.Knowledge bundles are useful for fine-tuning prompts, auditing swarm consensus quality, and bootstrapping new nodes with historical decision context.