ADMIN_TOKEN in this terminal to match the server. The examples use its deterministic fixture provider; configuration operations and the shown run make no model calls.
createAdminRouter() creates and updates Agents and Teams. Workflow routes only store name/description metadata; they do not accept steps or create executable Workflows. Every route is part of your trusted operator API. The host must authenticate it separately from application transport.
Endpoints
Agents
Teams
Workflows
Tools
Toolkit Catalog
Toolkit Configs (Credentials Management)
Create Agent
Agent Blueprint
Model ID accepted by the selected provider. This walkthrough uses
"local-v1"; choose a live provider/model from example models when adapting it.Provider-specific configuration passed to
modelRegistry.resolve(). It is persisted privately and omitted from public responses; prefer host environment credentials where supported.Update Agent
Create Team
First createwriter with the Agent request above and "name": "writer". Then submit the Team with both existing member names:
writer using the same Agent request with "name": "writer". The local fixture demonstrates configuration wiring; it does not perform useful model coordination. Use real providers when testing Team behavior.
Team Blueprint
Validation & Error Codes
Workflow metadata
APOST /workflows body accepts name and optional description. There is no workflow-update route or serialized step graph. To execute a Workflow, define its steps in application code and register it with core. Deleting metadata also removes a matching live registry entry, if one exists.
Toolkit configuration
Browse/toolkit-catalog for registered toolkit types and configuration fields. Save an instance with toolkitId, instanceName, config, and optional enabled. Enabling it exposes its tools to subsequent Agent creation; inspect /tools for the exact names before adding them to a blueprint.
Toolkit response masking follows catalog fields marked secret. Masked placeholder values on update preserve those existing secret values. Storage retains the original settings; see storage ownership and sensitive values.
Verify an integration
Check missing credentials, unknown tool names, duplicate entity names, and restart hydration before connecting an operator UI. Distinguish/admin/agents (persisted blueprints) from the transport registry (currently executable instances). Continue with Socket.IO for configuration-change notifications.