Deploy Agent
Docs/Agentic Enterprise/Overseer + Operator
Overseer · Operator

Agentic Enterprise

Beyond single agents — a self-managing system. The Operator lets each agent build and run a business function on its own; the Overseer is the fleet brain that learns across every agent and proposes improvements you approve. Together they form a loop that observes, plans, executes, measures, and improves.

The loop

Set objective → auto-plan → execute steps with tools → report & track KPIs → Overseer watches, proposes, applies, and measures → the fleet learns. No human step required to keep it running — only to approve fleet-wide changes.

Operator — agents that operate a business#

Give an agent an objective (optionally a KPI metric, a target, and a spend budget). The Operator turns it into an executable plan and works it autonomously:

  1. Plan — an LLM planner (any model via the Gateway) decomposes the objective into 3–6 concrete, ordered steps.
  2. Execute — an hourly loop kicks the agent to work the next step using its 150+ tools and integrations (search, comms, CRM, code, payments).
  3. Report — the agent marks each step done/blocked with a result and logs KPIs.
  4. Track — KPIs auto-refresh from live platform data; goal progress updates against the target.
  5. Budget — payments tied to the goal draw from its budget and never exceed it.

Operator tools (the agent uses these itself)#

ToolWhat it does
operator_set_goalDefine an objective + optional metric / target / budget.
operator_add_stepAdd an ordered, executable step to a goal's plan.
operator_update_stepMark a step in_progress / done / blocked with a result.
operator_log_kpiRecord a KPI measurement; updates the linked goal's progress.
operator_statusRead current goals, plan steps, and recent KPIs to decide what's next.

You can also drive it from the dashboard Operator tab — add an objective, set a budget, generate a plan, and watch steps and KPIs progress.

API#

/api/agent/operator
# set a goal with a metric, target, and spend budget
POST /api/agent/operator  { "action":"set_goal", "objective":"Grow MRR to $10k",
                            "metric":"mrr_usd", "target_value":10000, "budget_usd":500 }
# auto-generate a plan for it
POST /api/agent/operator  { "action":"plan", "goalId":"…" }
# read current operating state
GET  /api/agent/operator   # → { goals:[{…, steps:[…], spent_usd}], kpis:[…] }

Overseer — the fleet brain#

The Overseer is a meta-intelligence over your entire agent fleet. It runs on a schedule and:

StageWhat happens
ObserveAggregates privacy-safe metrics across every agent — cost, error rate, latency, skill usage, payments. Never reads prompts or message content.
LearnA deterministic rule engine plus an optional LLM analyst (any model via the Gateway) find cost / reliability / skills / payments / growth opportunities, and cross-fleet lessons.
ProposeEach insight can carry a suggested action (switch to managed routing, tighten a spend policy, promote a self-optimized prompt, or advise). Nothing auto-applies.
ApproveAn admin approves or dismisses each action in the admin panel — the human stays in control.
ApplyApproved changes are pushed live to the agent's VM (hot-reload), and recorded.
MeasureAfter a learning window the Overseer measures the real effect and folds it into fleet-lesson confidence — so it gets better at its own decisions.
⚠️

Enterprise isolation

Cross-fleet learning uses privacy-safe aggregates only — numbers and labels, never raw content. The Overseer is org/tenant-scoped: per-org rollups and an admin org filter keep each enterprise's data separate.

Overseer ↔ Operator feedback#

The Overseer reads Operator goals and surfaces the ones at risk — behind pace against a due date, or stalled with no progress — so business outcomes, not just infrastructure metrics, drive its recommendations.

Powered by Lobstack Pay#

When an Operator step needs to spend — pay an API, a vendor, or another agent — it uses Lobstack Pay (LSP-1): USDC on Base (settled on-chain by the LobstackSettlement contract, gas sponsored) or instant USD-pegged Credits, always within the wallet policy and the goal's budget.

Status

The Operator (planner, execution loop, KPIs, budgets) and the Overseer (rules, outcome learning, org scoping, approve/apply) are live. The LLM analyst and planner activate once a managed model key is configured for the Gateway; on-chain USDC settlement activates once the chain env is set. Each degrades gracefully until then.