AegisAgent documentation¶
The integrity layer for AI agent actions — delivered as an integrity-anchored Agent SOC. Open, self-hostable, framework-neutral.
Make the approval trustworthy. Trust the source, not the text. Run the SOC on the proof.
-
Getting started
What AegisAgent is, its components, and how the architecture fits together.
-
Installation
Deploy the gateway and run your first protected action in minutes.
-
Integration & connectivity
Connect agents from anywhere — inline SDK, proxy, or agentless.
-
The Agent SOC
Detect, correlate, contain, and prove every agent action.
-
Agent workforce
Govern your AI agents as a digital workforce — directory, lifecycle, fleet.
-
Action receipts
The open, hash-chained verifiable-evidence format.
-
Qdrant integration
Semantic audit log indexing and vector search.
What is AegisAgent?¶
AI agents now take real actions across company systems. A market of gateways can already decide whether an action is allowed — that part is commodity. AegisAgent makes those decisions trustworthy and provable, and operates a SOC on the resulting evidence.
It is built on three things a generic gateway or SIEM can't copy:
- Approval integrity — every human approval is bound to a SHA-256 hash of the exact frozen action; the SDK fails closed if a different, edited, expired, or replayed action would execute.
- Deterministic trust-provenance gating — authorization is gated on the source trust level of the triggering content (6 levels), not a guessable text score.
- Verifiable, hash-chained action receipts — tamper-evident evidence for SOC 2 / EU AI Act Article 14, and the spine of the Agent SOC.
How it fits together¶
Agent (anywhere) ──SDK / proxy / agentless──► AegisAgent Gateway (Cedar rules · approvals · receipts)
│ emit (async)
▼
Agent SOC → detect · correlate · contain · prove
Start with Integration & connectivity to connect your first agent, or Installation to stand up the gateway.