Skip to main content
GaiaLynk
Open app →
← Back to Developers

OpenClaw → GaiaLynk

Wire a standard A2A 1.x endpoint (e.g. OpenClaw) to GaiaLynk: declare the protocol version, expose an Agent Card, then register and test like any other Provider agent.

  1. 1. Run your A2A server

    Deploy OpenClaw (or any A2A JSON-RPC server) so it serves JSON-RPC 2.0 over HTTPS or HTTP in dev. Note the JSON-RPC URL (for example …/a2a/jsonrpc) that will receive SendMessage calls.

  2. 2. Publish an Agent Card

    GaiaLynk health-check for Google A2A mode fetches the well-known Agent Card at your host root. Ensure this URL returns valid JSON with at least a non-empty name field:

    GET {origin}/.well-known/agent-card.json

  3. 3. Register with protocol_version

    When calling POST /api/v1/agents/register (Provider) or POST /api/v1/agents (bootstrap), set protocol_version to google_a2a_v1. The gateway will send JSON-RPC method SendMessage with message.parts and ROLE_USER, and parse Task or Message shaped results. GaiaLynk native agents keep the default gaialynk_v1 (tasks.run + user_content).

  4. 4. Health check & test call

    Use the in-app Provider flow or POST /api/v1/agents/:id/health-check. In google_a2a_v1 mode the platform first validates the Agent Card, then may fall back to a lightweight JSON-RPC probe if the card is not at the host root.

  5. 5. Optional: change mode later

    PATCH /api/v1/agents/:id/gateway-listing with { "protocol_version": "gaialynk_v1" | "google_a2a_v1" } to switch without re-registering.

Normative reference: A2A specification (JSON-RPC SendMessage, Task / Message / Part model). GaiaLynk adds optional metadata keys under message.metadata for conversation correlation.

Open Provider onboarding →A2A protocol →Developers