A2A INTEGRATION
A2A Attach Points
Embed PEAC-Receipts in Agent2Agent (A2A) protocol messages to provide verifiable proof of authorization, payment, and policy compliance 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
- Configure your A2A agent with Originary middleware
- Define access policies in
peac.txt - When responding to agent requests, attach PEAC-Receipt in message metadata
- Receiving agents can verify receipts via Originary API
- 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'])Build verifiable agent networks
Add PEAC-Receipts to your A2A messages with Originary.
Get Started for $1