Fused is available by license. Request access →
First-class ways into Fused

Give every builder the interface they want.

Artifacts shape Fused Engine into an interface each builder wants to use: a Capability SDK for application teams or a focused MCP server for agents.

One gateway, shaped for the way each product builds.
Clusters of applications and agents reach external services through Fused interfacesApplications use a Capability SDK and agents use a focused MCP server. Requests pass through Fused Engine before reaching approved external services.0102030102APPLICATION CLUSTERAGENT CLUSTERINTERFACE 01Capability SDKtyped capabilities+ selected incoming eventsINTERFACE 02MCP serversearch_docs + executeone call or a short sequenceFUSEDEnginePolicy-aware executioncredentials resolved here● LIVEEXTERNAL SERVICESREQUESTEXECUTE

Two ways into Fused

Choose the interface. Keep the same gateway.

Applications and agents build differently. Artifacts give each one a focused way to use the services already controlled by Engine.

MODE 01 · APPLICATIONS

A Capability SDK built around the product.

Give an application one typed package for the capabilities it owns. The SDK stays small even when the workspace grows.

Types generated from the service versions the product selected.
Selected incoming events arrive through the same product interface.
support-capabilities.ts
const support = new FusedSDK({ engineUrl });

await support.linear.getIssue({ id });
await support.slack.sendMessage({ channel, text });
linear.issue.created → your product
MODE 02 · AGENTS

Two tools. Plenty of room to work.

The agent discovers only the operations this MCP server was given, then uses execute for a single call or a short TypeScript sequence.

The script runs in an isolated process with no direct network or filesystem access.
Credentials never enter the script. Engine resolves them when an approved operation runs.
search_docsFind the approved operations and fetch the exact schema.
executeRun one request or compose several results in TypeScript.
EXECUTE SCRIPT
const issue = await call("getIssue", { id });
await call("sendMessage", { text: issue.title });
return issue;
Engine owns provider access. The agent only receives the result.
MODE 03 · INCOMING EVENTS

Webhooks arrive through the Capability SDK.

Select the provider events this product should receive. Engine verifies and queues them, while the generated SDK gives the application a typed receiver alongside its outgoing calls.

Signature verification and reliable delivery stay inside Engine.
The product handles only the events selected for its SDK.
CAPABILITY SDK · EVENTSsupport-events.ts
import { fusedWebhooks, LinearWebhook } from "@acme/support";

const receiver = fusedWebhooks.listen(
  "support-events", token
);

receiver.on(LinearWebhook.ISSUE_CREATED, async (event, ctx) => {
  await triage(event.body);
  ctx.ack();
});
Provider eventFused EngineCapability SDK

How it fits

Choose the capability. Fused shapes the way in.

01

Select what belongs

Choose the services and capabilities this product or agent should be able to use.

02

Choose the interface

Build a Capability SDK for an application or deploy a focused MCP server for an agent.

03

Run through Fused

Keep access, credentials, execution, and change visibility behind the same gateway.

Give every builder a focused way into Engine.

Request access to receive your Fused license key and start shaping Capability SDKs and MCP servers around the products that need them.

Request a license key