Dual identity validation
Agent token and user context token, both required.
Agents
Agent-to-agent traffic, governed
Route A2A calls through the same gateway as everything else, with identity checked on both the agent and the human behind it.
- 2
- identities validated per request
- 1
- trace across every agent hop
- Per hop
- purpose-scoped tokens
The problem
When agents call other agents, authority can quietly grow beyond what any human granted, and traces break across the hand-offs.
How it works
Fabric validates the agent token and the user context token on every A2A request, issues a purpose-scoped token per hop, and denies the request if policy cannot be verified. Every hop lands in the same trace.
What you get
Scoped delegation
Each hop gets its own purpose-scoped token.
End-to-end traces
A single trace follows an action across every agent hop.
Bring every AI interaction under control
Connect your first model, MCP server or internal API and apply consistent governance from one gateway.