A2A Integration

This section is advisory and non-prescriptive. The illustrations describe current possibilities and limitations rather than canonical shapes. The A2A stewards are invited to publish authoritative LCP integration guidance for the protocol.

What it is

An open protocol for communication between AI agents. Task metadata is a key-value map explicitly defined as free for custom fields. Agent Cards published at /.well-known/agent-card.json carry a formal extensions mechanism.

Tier A — Available today

Task metadata accepts arbitrary keys without coordination:

{
  "task": {
    "id": "...",
    "metadata": {
      "legalContext": {
        "type": "sha256",
        "value": "0x7f83b165..."
      }
    }
  }
}

Agent Cards can declare LCP requirements in a custom extensions block, enabling pre-interaction compatibility evaluation:

{
  "name": "...",
  "skills": [...],
  "legalContext": {
    "required": true,
    "minimumLevel": 2,
    "acceptedJurisdictions": ["..."],
    "acceptedDisputeMethods": ["..."]
  }
}

Tier B — Forward work

A formal extensions registration in the A2A schema would give parsers standardized handling across implementations.

Limitations

Custom keys in task metadata are interoperable only as far as receiving agents recognize them. Agent Card extensions surface compatibility but do not enforce it across the protocol.

Steward invitation

The A2A stewards are invited to register legalContext as a first-class extension in both task metadata and Agent Cards, and to publish guidance on skill-level LCP requirements as part of capability negotiation.