auditail (Python SDK)
The security layer for autonomous AI agents. Guardrails that block risky actions, and a tamper-evident audit trail of everything your agents do.
📖 Full Documentation · 🚀 Join the Private Beta
Install
pip install auditail
pip install "auditail[verify]" # adds verify_receipt() for the service that executes actions
Quickstart
from auditail import Auditail, rules
aegis = Auditail(api_key="your_key")
aegis.add_rules([
rules.no_external_email(internal_domains=["acme.com"]),
rules.no_data_deletion(),
])
result = aegis.guard(
action="send_email",
payload={"to": "client@example.com", "body": "Report attached."},
agent_id="financial-bot-01",
)
if result.approved:
send_email(...)
else:
print(f"Blocked: {result.reason}")
LangChain Integration
from langchain.agents import tool
from auditail import Auditail, rules
aegis = Auditail(api_key="your_key")
aegis.add_rule(rules.no_external_email(internal_domains=["acme.com"]))
@tool
def send_email(to: str, body: str) -> str:
"""Send an email to a recipient."""
result = aegis.guard(
action="send_email",
payload={"to": to, "body": body},
agent_id="langchain-agent",
)
if not result.approved:
return f"Action blocked by Auditail: {result.reason}"
# ... actual send logic
return "Email sent."
Private beta
The SDK, API and dashboard are live. Guardrail rules run locally in your process; every decision is delivered in the background to a hash-chained audit log you can browse and verify at app.auditail.io.
- Batched, retried, idempotent delivery.
guard()never waits on the network, and a delivery failure never reaches your agent. - Secrets are redacted before an event leaves your process (
password,token,apiKey, ... plus your ownredact_keys). - Call
aegis.flush()before a serverless function returns or the process exits.
Request an API key: keys are issued to design partners personally.
Human approval is live: a require_approval rule pauses the agent until someone approves or denies it in the dashboard or through your webhook (Slack, Teams, Discord, any HTTPS endpoint). No answer means denied. See the approval guide.
Signed receipts: every human approval returns a receipt your payment or email service can verify before acting (verifyReceipt), so an agent cannot skip the check. Logs export to a file anyone can verify offline: npx -p auditail-sdk auditail-verify. See receipts and evidence.
Roadmap (not available yet): native Slack and PagerDuty apps, private-cloud deployment.
License
MIT
Metadata
Release files for auditail 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| auditail-0.4.0.tar.gz | 15.2 kB | Without provenance | Details for auditail-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| auditail-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for auditail-0.4.0-py3-none-any.whl |
Total release size: 30.6 kB
Release files / auditail-0.4.0.tar.gz
| Download URL | auditail-0.4.0.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ec4702e4c5389c1ab32c45e0c2aa88ced386f0a6c3eb12b78aa773c5791759d
|
|
BLAKE2b-256 checksum How to use checksums |
b6f2f32306e8e50fc0f9a09a4e154e861fee907833e861a45452b0926d71d62d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Release files / auditail-0.4.0-py3-none-any.whl
| Download URL | auditail-0.4.0-py3-none-any.whl |
|---|---|
| Size | 15.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d76b65e52e7b2f3a0e49cc1149f4197f140f90e92825c66662b05bbc9e4d8855
|
|
BLAKE2b-256 checksum How to use checksums |
2c72c43886a3a2ede5a3de3a48bd1df5e45f79e81235c664726019c1373286e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Security for auditail 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.