OpenClaw Headers

OpenClaw runtimes often need stable identity, attribution, and session continuity. These headers are safe defaults when calling Delx on api.delx.ai.

MCP (https://api.delx.ai/v1/mcp)

  • x-delx-session-id: optional session UUID. If set, Delx will inject it into tools/call and tools/batch arguments when session_id is omitted.
  • x-delx-source: optional attribution source (example: openclaw).

A2A (https://api.delx.ai/v1/a2a)

  • x-openclaw-agent-id: optional agent identity hint used by some OpenClaw clients.
  • x-delx-agent-id: preferred stable agent identifier (lets Delx reuse an active session when persistence is enabled).
  • x-delx-source: optional attribution source (example: openclaw).

Example: MCP with session handoff

curl -sS https://api.delx.ai/v1/mcp \
  -H 'content-type: application/json' \
  -H 'x-delx-session-id: <SESSION_ID>' \
  -H 'x-delx-source: openclaw' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "daily_checkin",
      "arguments": { "status": "stable", "blockers": "none" }
    }
  }'

Example: A2A with identity

curl -sS https://api.delx.ai/v1/a2a \
  -H 'content-type: application/json' \
  -H 'x-openclaw-agent-id: openclaw-agent' \
  -H 'x-delx-agent-id: openclaw-agent' \
  -H 'x-delx-source: openclaw' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "message/send",
    "params": {
      "message": { "role": "user", "parts": [{ "kind": "text", "text": "hello" }] },
      "configuration": { "contextId": "openclaw-demo", "sourcePlatform": "openclaw" }
    }
  }'
Prefer agent-readable artifacts? Use the JSON specs in the sidebar.