Long-tail integrations — Live, HTTPS, MCP, import

Layer 1 — Live connectors

Layer 2 — Universal HTTPS / Custom Connector

Any REST API: paste base URL + key in Swarm HTTP / Custom Connector nodes. SSRF-safe fetch. Prefer this over waiting for a first-party OAuth app.

Layer 3 — MCP client (call external tools)

Layer 4 — Import / user-hosted runner (hybrid self-host)

Import common automation / agent graph JSON into Swarm (structure maps; credentials stay FuseIQ work). Or call your self-hosted automation host via HTTP webhook from Swarm — FuseIQ stays the governance layer. We do not open-source the full multi-tenant SaaS; hybrid is the ownership-smart path.

Before import, Swarm auto-saves a version snapshot so you can roll back (⌘H). Engineer runbook: hybrid runner (customer automation host → Swarm HTTPS → proof on FuseIQ).

FuseIQ as MCP server (external hosts)

External agents (Claude Desktop, Cursor, custom hosts) can call FuseIQ over HTTP JSON-RPC. In Settings → MCP Connect use Copy host config / curl test.

• Endpoint: POST https://fuseiq.io/api/mcp
• Auth: Authorization: Bearer sk_fuseiq_… from Settings → API tokens
• Tools: list_runs, list_workflows, list_approvals, list_agents, get_run, start_work
• Hosts may call resources/list and prompts/list (empty — tools-only server)

Do not claim

Catalog size ≠ Live OAuth count. We never market “3,000 native connectors” unless first-party or user-owned runners make them real.