Runtime API
Check Status and Execute
Check whether an agent environment is ready, then send a prompt to that specific Spinup agent.
Use these two endpoints to confirm an agent environment is ready, then send it a prompt. See Runs for the concept. Both require an agent runtime key as a bearer token.
Check readiness
curl -sS "https://api.getspinup.com/v1/agents/agent_01hxyz.../status" \
-H "Authorization: Bearer sk_agent_0123456789abcdef..."Example response:
{
"daemonVersion": "2026.04.17",
"ok": true,
"status": "ready"
}If the environment is still provisioning, wait for status to return ready before calling /exec.
Execute a prompt
curl -sS "https://api.getspinup.com/v1/agents/agent_01hxyz.../exec" \
-H "Authorization: Bearer sk_agent_0123456789abcdef..." \
-H "Content-Type: application/json" \
-d '{
"input": "Summarize this repository and tell me the next thing you would inspect.",
"timeoutSeconds": 45
}'Example response:
{
"harness": "openclaw",
"output": {
"text": "I would inspect apps/api/src/services/agent-runtime.ts next because it controls execution routing and timeout behavior."
},
"sessionId": null,
"stderr": "",
"stdout": "{\"text\":\"I would inspect apps/api/src/services/agent-runtime.ts next because it controls execution routing and timeout behavior.\"}",
"warnings": []
}Optional request fields
harness: target a specific enabled harness (openclaworhermes) instead of the defaultsessionId: continue a prior harness session when the runtime returns onetimeoutSeconds: cap run time for the request
When harness is hermes, Spinup runs the Hermes CLI inside the agent's isolated environment on Hermes' local backend. The rest of Hermes' surface (gateway, API server, messaging, cron, remote backends) isn't wired up yet; keep that part of the workload on a self-hosted Hermes setup if you need it today.