You connect to us. We connect to your customers’ tools — and secure the access.
Name the app your agents run under and pick the scopes it may ever ask for — one form, one-time secret, no provider paperwork.
afctl applications register --app-id my-agentYour customer approves the provider’s consent screen on a page we host. No Fabriq account, no sign-up. The only user identifier you send is your own user ID.
POST {AF_API_URL}/api/v1/apps/{AF_APP_ID}
/external-users/{our_user_id}/oauth/{provider}/initiate
headers: X-App-Id, X-App-Secret
body: {"connection_id": "<our_user_id>-<provider>",
"scopes": [...]}
# redirect the user to the returned oauth_url.Mint a token for your own user ID, then call tools through the gateway. The Python SDK is the shipping client.
POST {AF_API_URL}/api/v1/apps/{AF_APP_ID}
/external-users/{our_user_id}/token
-> {"access_token": "...", "expires_in": 3600}Two steps to ship. We handle the rest.
tools/call · gmail_send_emailacting for customer_8842, as customer-agent
grant: gmail.send · chat:writeTokens injected server-side · never in your process
{"ok": true, "id": "msg_01H9"}Logged with the user it acted for, the agent, the tool, and the verdict.
external_user_id = "customer_8842"One call to mint it, and it is constrained to that customer user for the rest of its life. You keep your own user IDs; the walls below are not something you have to build.
Gmail
Slack
Google Drivegmail.list_messagesAllowedThe token was minted for this external user, so the call reaches exactly what they connected — and nothing they did not.
gmail_send_emailHeldA named human approver has to say yes first. The draft waits; nothing leaves the room.
HubSpotGmailhubspot.contacts.listBlockedSame agent, same gateway, different room. The token names one external user, so this call has no door — it fails at Fabriq, not inside your code.
Notion
GitHub—No routeThe tool list is built for the user the token names. A room this token does not open is not a room the agent can see.
Illustrative customers · each call is recorded with the customer user it acted for and the agent that acted.
Give the application an identity and define the scopes it may request.
Customers authorize their own tools. Keep your own external user IDs.
Each request carries the customer identity and is constrained to their access.
Fabriq handles credentials, refresh, permissions, and a record of each call.
Explore the context attached to every request.
customer-agent has a defined purpose and a bounded set of tools.
The request acts for customer user, using that person’s permissions.
The policy applies to the requested action within Customer integrations, before the tool executes.
# pip install agentic-fabriq-sdk
from af_sdk import MCPClient
token = await af_client.get_mcp_token(
external_user_id="customer_8842",
)
async with MCPClient(
method="token",
app_id=AF_APP_ID,
app_secret=AF_APP_SECRET,
af_token=token["access_token"],
gateway_url=AF_GATEWAY_URL,
) as client:
await client.call_tool(
"gmail_send_email",
{"to": "bob@example.com", "subject": "Hi"},
)One endpoint. The token is injected into the call server-side, so your agent never handles or refreshes it.
/oauth/{provider}/initiateConnect a tool/connectionsWhat they connected/tokenMint a scoped token/connections/{id}/disconnectRevokeThe Python SDK is the shipping client: mint a token for your own user ID, then list and call tools as that user.
pip install agentic-fabriq-sdkclient.list_tools()client.call_tool(name, arguments)Register the application your agents run under, and see the connections and the record from the terminal.
afctl applications register --app-id my-agent