zap-a2a

Docs: Agent-to-Agent over ZAP · part of the ZAP Protocol

Google Agent2Agent over ZAP — agent cards, tasks, artifacts, all signed.

zap-proto.io · Spec · Paper · Discord

zap-a2a layers cross-vendor agent comm semantics over the ZAP transport. Post-quantum confidentiality, mutual authentication, and zero-copy parse come from the wire; this repo only adds the cross-vendor agent comm message shape.

Status

v0.1 — schema-first. This repo currently ships:

Reference implementations (Go, Rust, TS) land in v0.2 once zap-proto/spec provides cross-language codegen for the schema.

Why

Property A2A-over-HTTP+JSON zap-a2a
Confidentiality TLS (classical) X-Wing hybrid PQ (default)
Authentication bearer / TLS cert KEM keypair at transport
Wire encoding text or per-protocol binary ZAP wire, zero-copy
Identity binding DNS / cert chain zap-rns keypair
Future-quantum classical only hybrid by construction

By the composability theorem, zap-a2a inherits ZAP-base's PQ confidentiality and mutual auth automatically — no a2a-specific PQ analysis required.

Sub-protocol family

  • zap-http — HTTP request/response over ZAP
  • zap-ws — multi-stream pubsub
  • zap-fix — FIX 4.4 / 5.0 trading channel
  • zap-rns — KEM-bound service naming
  • zap-mcp — Model Context Protocol over ZAP
  • zap-acp — Agent Communication Protocol
  • zap-a2a — Google Agent2Agent over ZAP

License

MIT OR Apache-2.0

S
Description
Google Agent-to-Agent (A2A) over ZAP — agent cards, tasks, artifacts
Readme
30 KiB
Languages
ZAP 100%