Eight-case credential-free live conformance before setup
Integrations
Enforce AAC at the boundary you already control.
Use AAC before an MCP tool, API route, workflow step, transaction service, or downstream agent. The protected operation proceeds only on an exact permit.
Designed for Python, JavaScript, gateway, MCP, automation, and observability integrations.
Operational outcomes
What AAC changes.
Bearer-authenticated AAC authority verification
Portable AACP agreement and evidence verification
Framework-neutral fail-closed enforcement pattern
Organization value
Why make AAC part of your product.
Introduce consequential agent capabilities with a deterministic authority checkpoint before execution.
Bring portable decision evidence into customer security reviews, enterprise procurement, audit correlation, and internal controls.
Use one fail-closed integration contract across tools, services, workflows, transactions, and agent frameworks.
Build measurable authenticated usage and, with explicit consent, public visibility as a verified AAC organization.
Enforcement pattern
Permit is explicit.
Everything else denies.
client = AACClient(credential=AAC_API_CREDENTIAL)
receipt = client.verify(signed_scenario)
# verify() raises AACDenied on denial, timeout, malformed output, or bad receipt signature
execute_protected_operation(receipt)See the machine-readable OpenAPI contract for the current request and response schema.
Official integration starters
Download. Configure. Enforce.
Open AAC WikiRun all 8 live testsPython adapter v0.5.2JavaScript adapter v0.5.2MCP adapter v0.5.2AI test manifestAACP reference package
Credentials are supplied at runtime. Private signing keys never leave your environment.
First authenticated permit
From test to real enforcement.
Every package contains its own install-and-test guide. Run all eight fixed cases first. After domain verification, the signed-in console provides a domain-bound First Permit Kit that generates the private key locally, registers only the public key, and obtains the first real authenticated permit.
Built for the control owners
Continue by role.
Security teams
Evaluate the trust boundary, fail-closed behavior and decision evidence.
Platform engineering
Place one authority decision contract across agent and tool execution paths.
Evaluation questions
Questions AAC answers.
Gateway or service middleware
MCP tool wrapper
Workflow and transaction guard
Self-service authority enforcement
Verify the organization.
Strengthen the product.
Start free, add authority enforcement to a real workflow, and build decision evidence your engineering, security, customers, and partners can inspect.