Control Center

What it is

The Control Center is fleet-wide governance. It has two surfaces: an open overview aggregating your agent registry, and an authenticated operational console for sessions, receipts and events.

Why it exists

Individual assessments answer "how is this operation?" The Control Center answers "how is the whole fleet?", and preserves the operational history behind it.

When to use it

Use the overview for fleet posture at a glance; use the operational console for recorded sessions, receipts and audit history.

Where it fits / architecture position

It aggregates the Registry and the recorded sessions into one governance view.

Typical workflow

• Read the fleet overview (open) via GET /api/v1/control-center/overview.
• Authenticate to the operational console for sessions, receipts and events.

Step-by-step usage

1) Fleet overview (open, no auth):

curl -s http://localhost:8000/api/v1/control-center/overview

2) Operational console (authenticated): the /api/control/* and /api/vai/* endpoints require a Control Center session. Bootstrap the first owner with the provided script, then sign in:

python scripts/cc_bootstrap_owner.py   # seed the first admin
# then sign in at the Control Center login

Inputs and outputs

Inputs: none for the overview; a valid session for the console. Outputs: the overview aggregate (fleet counts, average trust/reputation, level distributions, per-agent summaries) and, when authenticated, sessions/receipts/events.

Real example

The overview is open and returns the aggregate directly. The operational endpoints are authenticated, verified: without a session, they return 401:

curl -s http://localhost:8000/api/control/sessions

{
  "detail": "Authentication required"
}

Expected results

• Overview, JSON with total_agents, active_agents, average_trust_score, distributions and an agents array.
• Operational console without auth, 401 Authentication required.

Common mistakes

• Expecting sessions/receipts from the open overview, those live behind authentication.
• Skipping the owner bootstrap before first sign-in.

Troubleshooting

• 401 on /api/control or /api/vai: authenticate (bootstrap the owner, then sign in).
• Empty overview: the registry is empty, observe an agent first.

Related documentation

• Control Center: the product overview.
• Registry: what the overview aggregates.
• Flight Recorder: the sessions it surfaces.