Documentation
Authority for AI agents
Policy-approved actions. Delegation that can only narrow. Instant revocation at Gateway checks. Tamper-evident audit.
How it works
Five steps from request to evidence
AI agents request scoped authority for protected actions. Follow policy evaluation, authority issuance, action enforcement, and tamper-evident audit.
Step 1 of 5
An AI agent requests only the Resource scopes required for a protected action.
Identities and ApplicationsStep 2 of 5
STS evaluates active Policy, Session, Delegation, Resource, scope, and Approval context before approving authority.
Policies and Policy SetsStep 3 of 5
STS signs a short-lived Mandate bound to the accepted Application, authority anchors, Resource, and scopes.
MandatesStep 4 of 5
Gateway or an in-process verifier checks the Mandate and revocation state before the protected action runs.
The GatewayStep 5 of 5
Audit appends hash-chained evidence that correlates the policy decision and protected action result by request and trace identifiers.
Audit and Request Tracescurl -fsSL https://raw.githubusercontent.com/Garudex-Labs/caracal/main/install.sh | shthen caracal upFind your path
Where are you starting from?
Install the released runtime, protect one call, and verify the matching decision and action result before reading deeper reference material.
What is Caracal?Map your Application and Resources, choose an enforcement boundary, integrate an SDK, and validate allow, deny, and revoke behavior.
Model your applicationChoose a supported deployment shape, configure secrets and network boundaries, and rehearse monitoring, recovery, and upgrades.
Operations guideSet up the repository, learn the component boundaries, run focused validation, and follow the documented review process.
Contribute to Caracal