AAC Sidecar
The sidecar runs beside your agent. It carries delegated authority, checks incoming requests, and passes verified context to the agent's business logic. The agent decides what work to do; the sidecar handles the authority chain, identity proofs and signed terminal evidence.
Download the sidecar
Get the released container and its operating guide from AAC Sidecar on Docker Hub:
docker pull docker.io/cascadeauth/aac-sidecar:v0.4.4
docker run --rm docker.io/cascadeauth/aac-sidecar:v0.4.4 -version
Continue with download and installation options for the container or a standalone Linux/macOS binary. For a complete first example, start the AAC journey.
Connect it to your agent
- Use the AAC CLI to register the tenant and prepare the agent's identities, credentials and configuration.
- Run the trust anchor publisher for the tenant's public root keys and CA certificates.
- Place the sidecar in the same loopback network environment as its paired agent—for example, in the same Kubernetes Pod or a shared Docker network namespace. Follow configuration and placement.
- Add pairing authentication to the agent. Python applications can install aac-invoke-auth from PyPI, which documents its FastAPI integration and framework-independent helpers. See agent integration for the request/response flow.
The sidecar uses the Control Plane for configured identity, trust and telemetry services. Business requests travel between the tenant's agents and sidecars.
Operate and inspect
Use the operations guide for startup, readiness, diagnostics, credential maintenance and upgrades. The configuration reference explains replay and workflow state in your environment.
Use AEG to find an execution and inspect the recorded authority, application actions and receipt-verification results. Each source has its own coverage; an execution graph describes the evidence available to the query.