Skip to main content
A2A INTEGRATION

A2A Attach Points

A2A protocol documentation for agent to agent transactions and agent-to-agent communication. Learn how to embed PEAC-Receipts in A2A protocol messages to provide verifiable proof of authorization, payment, and policy compliance for agent to agent transactions in multi-agent systems.

A2A + PEAC Integration

The Agent2Agent (A2A) protocol by Google enables communication and interoperability between AI agents. Originary extends A2A by attaching PEAC-Receipts to agent messages, creating an auditable chain of custody.

When one agent requests data or action from another, the response can include a PEAC-Receipt proving payment was made, policies were respected, and the transaction is verifiable.

5-Minute Quickstart

  1. Configure your A2A agent with Originary middleware
  2. Define access policies in peac.txt
  3. When responding to agent requests, attach PEAC-Receipt in message metadata
  4. Receiving agents can verify receipts via Originary API
  5. Build trust chains across multi-agent workflows

Code Example

// A2A message with PEAC-Receipt
const message = {
  to: 'agent-b@example.com',
  from: 'agent-a@example.com',
  content: { /* agent message */ },
  metadata: {
    'peac-receipt': signedJWT,
    'payment-evidence': { status: 'verified' }
  }
}

// Receiving agent verifies
await originary.verify(message.metadata['peac-receipt'])

Related Resources

Build verifiable agent networks

Add PEAC-Receipts to your A2A protocol messages and enable agent to agent transactions with Originary.

Get Started