Developer Quickstart

1. Register an agent

In the console, go to Agents → Register. You get back an app ID and an app secret.

Two settings on the agent matter for this flow, both under Settings → Connect & webhooks: the redirect URL your users return to after connecting, and (optionally) a webhook URL so your backend is told when a connection completes even if the user closes the tab.

2. Install the SDK

pip install agentic-fabriq-sdk        # Python — import as af_sdk
npm install @agenticfabriq/sdk        # TypeScriptcopy

Both clients read their credentials from the environment, so a quickstart fits on one screen:

AF_APP_ID=org-xxx_my-app
AF_APP_SECRET=...
# optional — defaults to https://dashboard.agenticfabriq.com
AF_BASE_URL=https://dashboard.agenticfabriq.comcopy

3. Connect a user's tool

initiate_connection returns a URL. Send your user there; they approve at the provider; the credential lands in Agentic Fabriq's vault. It never passes through your backend.

Python

from af_sdk import AgenticFabriq

af = AgenticFabriq()  # reads AF_APP_ID / AF_APP_SECRET / AF_BASE_URL

# inside your request handler
url = await af.initiate_connection(request, provider="gmail")
return redirect(url)copy

TypeScript

import { AgenticFabriq } from "@agenticfabriq/sdk";

const af = new AgenticFabriq();

const url = await af.initiateConnection(req, { provider: "gmail" });
res.redirect(url);copy

Optional arguments: connection_id (defaults to "default", letting one user hold several accounts for the same provider) and scopes (merged with the scopes configured on the agent).

4. Make a governed tool call

for_user mints a short-lived, user-scoped token and hands back a session whose identity is already baked in — no method on it takes a user id.

Python

async with await af.for_user(request) as session:
    tools = await session.get_tools()          # only what this user actually granted
    result = await session.call_tool(
        "google_gmail_list_messages",
        {"max_results": 5},
    )copy

If you are driving a model rather than calling tools directly, the session converts the same tool list into the shape your provider expects. Load the tools first — the adapters read the cached list:

await session.get_tools()
openai_tools    = session.to_openai_tools()
anthropic_tools = session.to_anthropic_tools()
langchain_tools = session.to_langchain_tools()   # needs langchain-core installedcopy

TypeScript

The TypeScript SDK deliberately does not wrap an MCP client. It gives you the token and the URL; hand them to the MCP client you already use.

const session = await af.forUser(req);

session.userId;     // the id your app authenticated
session.token;      // short-lived, user-scoped bearer token
session.expiresIn;  // seconds
session.mcpUrl;     // MCP endpoint to point your client atcopy

5. What just happened

The SDK is a thin wrapper over an HTTP API you can call directly. Every request authenticates with X-App-Id and X-App-Secret headers (HTTP Basic app_id:secret also works).

The full request and response shapes are in External Users (B2B2C).

Installing agentic-fabriq-sdk also installs afctl. The commands most useful while building:

afctl users list                       # everyone your product has connected
afctl sessions list --population external   # live tokens, and the proof behind each
afctl sessions revoke <jti>            # kill one immediately
afctl triggers list                    # provider-event subscriptions
afctl triggers deliveries              # did my webhook arrive?copy

Full command reference: CLI Reference (afctl).

What to read next