AAC Docs

AAC documentation

AAC platform · developer betaMarkdownDocs 42797a46037e

Carry delegated authority between agents. Learn how AAC binds identity, limits and verification, then add its components to the environment where your agents already run.

Understand AAC · Start the AAC journey

Components

AAC CLI

Register tenants, configure agents and maintain identities and credentials. The aac-cli package supplies both aac and aeg.

Runs on: your workstation or administration host.

Get it on PyPI · Install and use the CLI

Sidecar

Carry delegated authority and verify incoming requests beside each agent. Choose the container or a standalone Linux/macOS binary.

Runs in: your agent's network environment.

Get it on Docker Hub · Install the sidecar

Trust anchor publisher

Publish your tenant's public root keys and CA certificates so other sidecars can verify its authority and workload identities.

Runs in: your tenant, with access to its prepared public trust material.

Get it on PyPI or GHCR · Install and operate the publisher

Control Plane

Use AAC's shared API service for tenant administration, identity, public-trust distribution and authorized execution queries.

Runs as: an AAC-hosted service in the developer beta.

Connect to the service · View its endpoints

Agent Execution Graphs (AEG)

Find an execution, combine available evidence and inspect its authority, application actions and receipt-verification results.

Runs on: your workstation, using aeg from aac-cli.

Get it with AAC CLI on PyPI · Read the AEG guide

Agent integration

Authenticate calls between a Python agent and its paired sidecar with aac-invoke-auth. Its package page includes the FastAPI quick start and framework-independent helpers.

Runs inside: your Python agent application.

Get it on PyPI · Connect your agent

Documentation policy

These stable pages describe the latest supported released components. Each guide identifies its applicability and documentation revision; CLI and sidecar versions advance independently. The PyPI and registry pages also include installation and usage documentation.

Use Keys and certificates to understand custody and renewal across the components. Release notes provide upgrade guidance. Historical artifacts and release evidence remain with their publishers. This is a public developer beta; consult the license and support information before deployment.