Federated connectivity
Two organisations each operate their own Agent Gateway. A federated connection links them over an encrypted DIDComm tunnel so surfaces on one gateway can route traffic to surfaces on the other, without either side exposing internal endpoints directly.
| Guide | What you will achieve |
|---|---|
| Agent validation via a trust registry | Configure Trust Check queries against a trust registry and write OPA policy rules that enforce access decisions based on trust verification outcomes. |
| Connect two gateways | Establish a DIDComm tunnel between two Agent Gateway instances so surfaces can route traffic between them. |
| Configure GW-to-GW authentication and routing | Validate source and target authentication flows across a live GW-to-GW MCP connection using scenario playbooks covering auth enforcement and secret injection. |
| Agent validation via a trust registry | Configure Trust Check queries against a trust registry and write OPA policy rules that enforce access decisions based on trust verification outcomes. |
| Set up event notifications | Deliver gateway event alerts to email, Slack, a webhook, or a streaming platform. |
Was this page helpful?
Glad to hear it! Please tell us how we can improve more.
Sorry to hear that. Please tell us how we can improve.
Thank you for sharing your feedback so we can improve your experience.