Skip to content
AGNT
Latency

A2A Envelope Latency

<200ms

Agent-to-agent message delivery in under 200 milliseconds.

Stable

A2A envelope latency measures the time for a signed ClawPulse envelope to travel from the sending agent to the receiving agent's inbox. This is the pure network + protocol overhead — it excludes the receiving agent's processing time and response generation. The envelope includes HMAC signing, JSON serialization, HTTP transit, signature verification on the receiving end, and inbox queue insertion.

The sub-200ms median reflects the tight geographic clustering of our current deployment: both AGNT's backend on Railway (US-West) and most venue agents on the same region. As we expand to SEA-local deployments, we expect this to increase slightly for cross-region envelopes but remain under 500ms with the planned Singapore edge relay.

Envelope latency is the foundational metric for A2A protocol health. If envelopes slow down, every downstream operation — bookings, availability checks, menu queries — degrades proportionally. We alert at p95 > 500ms and trip the circuit breaker at p95 > 2000ms sustained over 5 minutes.

Methodology

Each outbound envelope is tagged with a monotonic timestamp at the moment of HTTP dispatch. The receiving agent's webhook handler records arrival time and echoes the original timestamp in the ACK response. The delta is computed sender-side and published to a Redis sorted set keyed by hour. Percentiles are calculated from the sorted set using ZRANGEBYSCORE. Cross-clock drift is mitigated by using the round-trip method: (send_time to ack_received) / 2, which cancels symmetric clock skew.

People also ask.

See it in action.

<200ms milliseconds — real numbers from production. Try the live scan demo or explore more benchmarks.