Scoped gateway tokens
They replace real credentials in agent-facing traffic.
Credential Brokering
Your secrets never leave your cloud.
Agents authenticate with a scoped gateway token. Fabric looks up and injects the real upstream credential inside your perimeter, never exposed to the agent.
- AgentHolds only a scoped gateway token
- Inside your perimeter
- Data planeResolves the token to the real credential
- Credential injectedAt request time
- UpstreamReceives the real credential
- 0
- upstream credentials the agent ever holds
- 1
- scoped gateway token replaces them
- 0
- brokered credentials visible to Postman
The problem
Handing an agent a real API key or database credential means that credential is only as safe as the agent's runtime, its logs, and every tool it calls. One leaked context window becomes a leaked secret.
How it works
The agent only ever holds a scoped gateway token. The data plane, running inside your VPC, resolves that token to the correct upstream credential and injects it at request time. Neither the agent nor Postman ever sees the underlying secret.
What you get
Injection inside your perimeter
Credential lookup and injection happen entirely within your environment.
Encrypted at rest
Secrets are encrypted with keys you control.
No Postman visibility
Postman has no visibility into brokered credentials.
Bring every AI interaction under control
Connect your first model, MCP server or internal API and apply consistent governance from one gateway.