Use cases
Concrete scenarios that show how the gateway’s capabilities combine to address real operational and integration challenges.
| Use case | What it covers |
|---|---|
| Let agents work across companies | Connect to a partner’s gateway over an encrypted DIDComm tunnel, carry the agent’s identity and the caller it acts for in a signed presentation, and keep each company’s own policies and audit. |
| Share fraud signals, not data | Exchange risk signals with partner companies through your gateways, with policy on each side reading every message and blocking any that would carry personal data. |
| Maintain network isolation with VPC peering | Reach services by private address, including in peered VPCs, and connect other clouds or companies over an encrypted gateway-to-gateway tunnel. |
| Retire shared API keys | Give each client and partner its own revocable API key, keep Entra or Okta as the identity source, and show each agent only the MCP tools it needs. |
| Turn existing APIs into MCP tools | Publish a REST API’s operations as MCP tools from its OpenAPI specification, with no change to the API, and reach other MCP servers by direct URL or gateway connection. |
| Prove what every agent did | Record every policy decision with the exact policy version behind it, and send metrics, traces, and logs to the tools you already run. |
Was this page helpful?
Glad to hear it. Thanks for letting us know.
Sorry to hear that. Thanks for letting us know.
Still stuck? Ask the community on Discord or contact us.