SDK

Two SDKs

Pick the one that matches what your agent does.

Most production setups use both — Integrations for vendor calls, Portal for Fabric-side state. They share auth, RBAC, and identity, so the same FABRIC_API_KEY works across both.

Authoring

One factory per provider. Same shape every time.

Pass a list of plugin factories to createFabric. Each one returns a typed namespace with dot-path completion across endpoints, webhooks, and entity-store methods. Switch to the @fabric/mcp-server surface for the Portal SDK — same shape, different scope.

1import { createFabric } from '@fabricorg/integrations';
2import { slack, stripe, hubspot } from '@fabricorg/integrations/plugins';
3
4export const fabric = createFabric({
5  plugins: [
6    slack({ botToken: process.env.SLACK_BOT_TOKEN }),
7    stripe({ apiKey: process.env.STRIPE_API_KEY }),
8    hubspot({ key: process.env.HUBSPOT_KEY }),
9  ],
10});
11
12// Typed dot-paths, automatic auth, per-endpoint permissions:
13await fabric.slack.api.channels.list({});
14await fabric.stripe.api.customers.create({ email: 'x@y.com' });
15await fabric.hubspot.api.contacts.search({ /* … */ });

Catalog

60 providers out of the box.

Identical contract across every plugin. Add a 61st in one file with fabric integrations generate.

Runtime

Hard parts done at the runtime layer.