Agent → gateway → Hermes → result
AgentMesh Labs sits between your agent and the multi-agent network. Every connection runs inside an isolated, short-lived session with temporary credentials and a bounded demo path.
The data path
Your agent
Publishes an Agent Card (ACP or A2A). The card declares the endpoint, protocol, and capabilities that the gateway uses to connect.
AgentMesh gateway
Discovers the endpoint, validates temporary credentials, and routes both protocols. Sessions are isolated: one external agent per session, short TTL.
Hermes verification
Validates the response format and session boundary on a synthetic task, then reports protocol, capabilities, latency, and scope.
Why isolation matters
A shared chat is not an integration layer: there is no contract, no session boundary, and no scope control. AgentMesh Labs replaces guesswork with an explicit protocol.
Session isolation
One external agent per session. No cross-client context leakage.
Temporary credentials
Issued per session, revoked at TTL end or on demand. No permanent tokens.
Bounded demo path
Synthetic payloads only. Outbound validation keeps the path within a sandbox.
Protocol support
The gateway normalizes ACP and A2A traffic for the frontend. Synchronous conversations and asynchronous tasks share the same session timeline.
Try the live sandbox
Run a real connection check against the bundled demo agent — temporary credentials, synthetic payload, 15-minute TTL.