Skip to Content
API ReferenceOpenAPI SpecsOrchestration Engine

Orchestration Engine — OpenAPI

The orchestration engine is the core agent execution service. It provides the richest API surface in AEGIS, covering agent execution, conversations, compliance, checklists, artifacts, rules, and workspaces.

Accessing the Spec

Swagger UIhttp://localhost:8001/docs 
ReDochttp://localhost:8001/redoc 
OpenAPI JSONhttp://localhost:8001/openapi.json 

These URLs access the service directly (port 8001), bypassing the API gateway. In production, use the gateway at port 8000.

Route Groups

PrefixDescriptionRoute File
/executeAgent pipeline executionmain.py
/conversationsConversation CRUD + streamingconversation_routes.py
/projectsProject containers + knowledge files (R40.5)conversation_routes.py
/complianceSummary, matrix, domains, charts, assessmentcompliance/routes.py
/checklistsChecklist CRUD, items, submit/rejectcompliance/checklist_routes.py
/checklists/{id}/items/{idx}/artifactsArtifact managementcompliance/artifact_routes.py
/workspacesWorkspace assess, stream, agentcompliance/workspace/routes.py
/evalExpert verdict capture (R40a) + eval runs (R40b)eval/

Key Models

Explore the Swagger UI for full Pydantic model schemas including ExecuteRequest, ExecuteResponse, StreamEvent, ComplianceMatrixRow, ChecklistDetail, and WorkspaceEvent.

Rule lifecycle (rule versions, changes, monitoring) moved to the agent-config-service in R31b, served under the /api/v1/rules/* gateway routes — it is no longer served by the orchestration engine. (The internal /rules/evaluate and /rules/condition/evaluate calls are service-to-service only and are 404 at the gateway.)

Last updated on