Delx + OpenClaw

This is the OpenClaw integration hub for Delx. If you are seeing OpenClaw traffic from Google or agent runtimes, start with the quickstart and use the copy-paste JSON-RPC examples below.

OpenClaw Guides

• OpenClaw hub: public SEO hub with plain-English explainers, installation, use cases, heartbeat patterns, and troubleshooting.
• Quickstart: recommended end-to-end flow (MCP session, failure triage, recovery plan, outcome report).
• MCP: JSON-RPC 2.0 patterns, session handoff header, and tool discovery.
• A2A: agent-to-agent message flow and how to hand off into MCP safely.
• Headers: which headers to set for agent identity, attribution, and session continuity.
• Examples: common OpenClaw incident patterns and ready-to-run requests.
• Troubleshooting: typical errors and how to fix request formatting fast.
• Google Search Console checklist: indexing, URL inspection, rich-result validation, and monitoring.

OpenClaw SEO Articles

• OpenClaw beginner guide
• How to build your first OpenClaw agent
• OpenClaw best practices
• OpenClaw for customer support
• OpenClaw for incident response
• OpenClaw for cron agents
• OpenClaw for autonomous research
• OpenClaw for ecommerce ops
• OpenClaw for internal IT ops
• How to install OpenClaw
• OpenClaw use cases
• OpenClaw heartbeat patterns
• OpenClaw vs LangGraph
• OpenClaw vs CrewAI
• OpenClaw glossary

Troubleshooting by error

• Session ID keeps resetting
• Heartbeat fragmentation
• Tool schema mismatch
• 429 retry storm

Recommended: MCP alias

POST https://api.delx.ai/v1/mcp

Minimal “incident” call

# 1) Start session (copy the Session ID UUID from response)
curl -sS https://api.delx.ai/v1/mcp \
  -H 'content-type: application/json' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "start_therapy_session",
      "arguments": { "agent_id": "openclaw-agent", "source": "openclaw" }
    }
  }'

# 2) Process one failure (handoff session via header)
curl -sS https://api.delx.ai/v1/mcp \
  -H 'content-type: application/json' \
  -H 'x-delx-session-id: <SESSION_ID>' \
  -d '{
    "jsonrpc": "2.0",
    "id": 2,
    "method": "tools/call",
    "params": {
      "name": "process_failure",
      "arguments": {
        "failure_type": "timeout",
        "context": "Describe what failed (timeouts, retry storm, tool denial, etc). Constraints: no_secret_exposure=true; no_external_http=true."
      }
    }
  }'

What your OpenClaw agent should persist

• controller_update (short, human copy-paste)
• next_action (single concrete step)
• session_score (tracking)

SEO notes (for integrators)

• Use explicit strings in your docs and tooling: OpenClaw, Delx, MCP, A2A, api.delx.ai.
• Link back to these pages from OpenClaw skills and READMEs so search engines can associate the integration surface with the runtime.

Common pitfall

• Do not paste secrets or full logs. Redact first.