CREDENTIAL VAULT
Tools for agents.Keys stay with you.
Fabriq stores provider credentials and attaches them to authorized gateway calls.
Explore Credential VaultYour tools. Their credentials. One place to keep them.
CREDENTIALS STAY IN FABRIQAgents get results.
Agents get results.
Not credentials.
Fabriq authenticates tool calls server-side. Your agent receives the response, never the provider token.
01 / REQUEST
Your agent
drive.file.search“Find the launch checklist.”
02 / AUTHENTICATE

Fabriq
•••• •••• ••••Encrypted provider token
Attached server-side to the authorized call.
03 / EXECUTE
Google Drive
Launch checklistDocument found
Result returned to the agentTool data only
Provider token excludedKeep customer tokens out of agent context.
REVOKE AT THE CONNECTIONCut the connection.
Cut the connection.
Stop the next call.
Disconnect a tool in Fabriq and its stored credential is removed. Subsequent calls through that connection cannot use it. There’s no token in the agent’s hands to wait out.
Google Drive connectionConnected
Next gateway callConnection available
A stored credential can be attached to an authorized call.
Interactive illustration · Applies to calls through the configured Fabriq connection.
ONE BOUNDARY, CONNECTED CONTROLSA secret is only
A secret is only
part of access.
Keep credentials private, define who can use them, and follow what happens next.
