A2A

Integration steps

1. Read /.well-known/agent-card.json. Send POST /api/a2a with a2a-version: 1.0 and a scoped developer credential.
2. SendMessage accepts one application/json data part containing passportRef, idempotencyKey, requestedAction and proposal. The result is a completed task whose artifact contains the shared authority response.
3. GetTask reads a captured result scoped to the caller. Streaming, push notifications and Google marketplace acceptance are not implemented claims.
4. Request the authority lifecycle extension explicitly for leases/proofs. Verify candidate/context commitments, audience, expiry, trust and current status before relying on a proof.

{
  "jsonrpc": "2.0", "id": 1, "method": "SendMessage",
  "params": { "message": { "messageId": "unique-message-id",
    "role": "ROLE_USER", "parts": [{
      "mediaType": "application/json",
      "data": { "passportRef": "YOUR_PASSPORT_REF",
        "idempotencyKey": "unique-request-key",
        "requestedAction": "SHORTLIST", "proposal": {
          "agentId": "travel-agent", "expectedStateVersion": 1,
          "candidate": { "id": "QLOO_ENTITY_ID", "name": "Reviewed candidate", "type": "place" },
          "context": { "key": "weekend", "domain": "place" }
        } } }] } }
}