/health endpoint that returns 200 OK when healthy. The Executor Registry API lets you register executors by name, list all registered entries, and verify that a named executor is reachable and healthy.
Executor Naming
Each executor must be registered with a uniquename. Names are opaque strings — use descriptive slugs that reflect the agent type or deployment environment (e.g. "local-llm", "gpt-4-remote", "verifier-strict"). The name is the identifier you reference in RunSubmitSpec agent entries, POST /api/task/run-real, and the core_agent startup configuration.
If you register an executor with a name that already exists in the registry, the existing entry is replaced.
Multi-Executor Patterns
You can register multiple executors to serve different agent roles:- Proposal executor — a capable LLM or reasoning agent used as the primary proposer.
- Verification executor — a lighter-weight or rule-based agent used only for verification steps.
- Remote executor — an executor running on a different node, dispatched via the p2p overlay.
RunSubmitSpec.agents[].executor to route individual steps to specific runtimes.
Remote Executor Dispatch
Set"remote": true and provide a target_node_id to register an executor that lives on a remote WattSwarm node. When the kernel dispatches a step to a remote executor, it routes the request over the p2p network to the target node. The target node must have a local executor registered under the same base_url.
Remote executor dispatch requires the background network service to be running on both nodes. Ensure both nodes are online and connected before submitting tasks that reference remote executors.
POST /api/executors/add
Registers a new executor in the local registry, or replaces an existing entry with the same name.Base URL of the executor’s HTTP API (e.g.
"http://127.0.0.1:8080"). The kernel appends /health for health checks and executor-specific paths for task dispatch.For remote executors, the node ID of the peer that hosts this executor. Required when
remote is true.Optional URL the kernel uses to push agent event callbacks to this executor. Useful when the executor needs to react to swarm events asynchronously.
Absolute path on the kernel host to a file containing an auth token for the commit-plane endpoint.
GET /api/executors/list
Returns all executors currently registered in the local registry.POST /api/executors/check
Performs a live health check against the named executor by issuing aGET request to <base_url>/health. Returns {"ok": true} if the executor responds with a 2xx status code.