Skip to main content

​
Connectors & Capabilities

Every action the agent can call is a ConnectorCapability — a (connector_type, connector_action, activity_name, risk) tuple in the registry, exposed at:
A brand’s AutomationConfig.tool_definitions selects which capabilities that brand’s agent may call, with per-tool params, idempotency keys, and policy caps. At runtime the LLM emits a tool call → generic connector dispatch routes it to the activity → the result re-enters the deterministic workflow.
Adding a system is data, not code: one connector plus N capability rows. Dispatch, idempotency, the review gate, and spend caps all apply automatically by risk tier — so breadth doesn’t erode safety.

​
Risk tiers

Risk tier is the mechanism that connects capability breadth to the review gate and policy controls.
A new FinancialWrite or OperationalWrite capability inherits gate and cap behavior automatically — but only if the tier is set correctly. Mis-tiering a money-moving action as Write silently removes both protections.

​
Coverage

99 agent-callable capabilities in the registry. The engine covers the highest-risk, highest-value commerce and finance actions — the ones that move money or order state. The breadth gaps are in marketing reach and fulfillment execution. Remaining build work (not just registration): Klaviyo campaigns and flows, ShipStation label and rate creation, Amazon SP-API, and Stripe disputes and payouts.

​
StateSet-native connectors

The engine drives StateSet’s own managed infrastructure as first-class connectors, so a brand can run these on the engine: Together these close the managed support email loop — connect a domain, inbound email arrives, the agent acts, the reply threads back — and add agentic X12 automation, both on the same deterministic engine and risk-gated dispatch.

​
Adding capabilities

  1. Register the connector and its capability rows. The deterministic engine, dispatch, idempotency, review gate, and spend caps apply automatically by risk tier.
  2. Set the risk tier honestly. This is the only place the safety behavior is decided.
  3. Measure with the scorecard. Every capability’s outcomes flow into per-brand and fleet quality scorecards, so expansion stays evidence-driven.