OpenClaw Agent (Run + Jobs + Memory)

OpenClaw is ctxvault’s execution agent service. You can run tasks synchronously, queue async jobs, and optionally integrate memory writeback.

Base URL

OpenClaw is exposed at:

base-url

https://api.ctxvault.dev/openclaw

Core Endpoints

endpoints

GET  /openclaw/health
GET  /openclaw/api/v1/info
POST /openclaw/api/v1/agent/run
POST /openclaw/api/v1/agent/jobs
GET  /openclaw/api/v1/agent/jobs
GET  /openclaw/api/v1/agent/jobs/:id
GET  /openclaw/api/v1/agent/memory/status

Run a Task Now

curl

curl -sS -X POST https://api.ctxvault.dev/openclaw/api/v1/agent/run \
  -H "content-type: application/json" \
  -d '{
    "goal":"Fetch API health and summarize it",
    "mode":"execute",
    "use_memory":true
  }'

Queue Async Jobs

For longer work, submit a job and poll the status:

curl

# Queue
curl -sS -X POST https://api.ctxvault.dev/openclaw/api/v1/agent/jobs \
  -H "content-type: application/json" \
  -d '{"goal":"index weekly logs","mode":"execute"}'

# List jobs
curl -sS https://api.ctxvault.dev/openclaw/api/v1/agent/jobs

# Get one job
curl -sS https://api.ctxvault.dev/openclaw/api/v1/agent/jobs/<job_id>

Security Defaults

In production, set OPENCLAW_API_KEY and include it as Bearer auth (or x-api-key) in every request.

auth-request

curl -sS https://api.ctxvault.dev/openclaw/api/v1/info \
  -H "Authorization: Bearer oc_your_key_here"

Memory Integration

If memory env vars are configured in OpenClaw, it will fetch context before planning and store run summaries after execution.

memory-status

curl -sS https://api.ctxvault.dev/openclaw/api/v1/agent/memory/status

You can also use the built-in dashboard page at /dashboard/openclaw to run tasks and inspect jobs without leaving ctxvault.