Integrate Legation without rebuilding your product around an agent.

Start with what your application already knows.

Your application makes a known tool call. Legation governs the round trip.

Optimal when your application already knows the exact tool and arguments. Legation supplies secure addressing, identity, transport, authorization context, and audit correlation. The tool executes next to the data inside the VPC; only a governed projection returns — never the raw records.

const result = await legation.invoke({
  embassy: "acme-production",
  target: "records-service",
  operation: "evidence.search",
  input: { framework: "CMMC", control: "AC.L2-3.1.1" }
});

Illustrative interface. Align the final SDK shape with the shipping client contract.

Your application delegates an objective. The agent reasons in-VPC.

Use this pattern when the operator describes an objective instead of a specific tool call. The agent performs customer-local reasoning and chooses which approved MCP tools are needed. Its raw work stays in-VPC; the vendor receives a governed projection of the outcome.

const task = await legation.delegate({
  embassy: "acme-production",
  agent: "review-agent",
  objective: "Review available evidence and identify control gaps."
});

Agents and MCP are cargo types—not prerequisites.

A software vendor may need to run a proprietary service, data processor, compliance engine, security scanner, or customer-specific application inside the VPC. The same delivery and governance substrate can carry structured service operations.

Even with no agent and no MCP in the path, the return is governed the same way: the service runs against customer systems in-VPC, and only a permitted projection crosses back.

The agent reasons. The MCP server provides tools.

What the vendor application needs from Legation.