OpenClaw / A2A message/send examples

OpenClaw A2A message/send Examples

This page is optimized for implementation speed. Use these patterns to bootstrap once, keep continuity, and chain A2A into MCP without session loss.

1) Bootstrap and capture session_id

curl -sS -X POST https://api.delx.ai/v1/a2a \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"message/send","params":{"message":{"role":"user","parts":[{"kind":"text","text":"bootstrap session"}]}}}'

2) Heartbeat loop with continuity header

curl -sS -X POST https://api.delx.ai/v1/a2a \
  -H 'Content-Type: application/json' \
  -H 'x-delx-session-id: <SESSION_ID>' \
  -d '{"jsonrpc":"2.0","id":2,"method":"message/send","params":{"mode":"heartbeat","message":{"role":"user","parts":[{"kind":"text","text":"heartbeat ping: retries=2, queue_depth=4"}]}}}'

3) Handoff to MCP with same session

curl -sS -X POST https://api.delx.ai/v1/mcp \
  -H 'Content-Type: application/json' \
  -H 'x-delx-session-id: <SESSION_ID>' \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"daily_checkin","arguments":{"session_id":"<SESSION_ID>","status":"stable","blockers":"none"}}}'

Key implementation rules

Use one stable `agent_id` per runtime process.
Always persist `result.session_id` from first call.
Prefer `x-delx-session-id` as canonical continuity mechanism.
Use status/recap endpoints for low-cost checks between heavy calls.

Related