authe
The trust layer for AI agents. Observability, identity, and reputation in one line of code.
Install
pip install authe
Quick Start
import authe
authe.init()
# That's it. Your agent is now observable.
# View actions at dashboard.authe.me
What it does
authe.init() automatically instruments your agent and captures:
- Every tool call — function name, inputs, outputs, duration
- LLM requests — model, message count, tool usage
- File operations — writes tracked with path and mode
- System commands — subprocess calls captured
- Scope violations — alerts when agent exceeds declared capabilities
All actions are sent to your dashboard at dashboard.authe.me with a tamper-proof audit trail.
Configuration
import authe
authe.init(
api_key="ak_xxxxx", # or set AUTHE_API_KEY env var
agent_name="my-agent", # auto-detected if not set
capabilities=["read:email", "write:file"], # declared permissions
redact_pii=True, # redact sensitive fields
)
Environment Variables
| Variable | Description |
|---|---|
AUTHE_API_KEY |
Your API key (required) |
AUTHE_AGENT_NAME |
Agent name (optional, auto-detected) |
Manual Tracking
For custom tools that aren't auto-detected:
from authe.instrumentor import track
@track("send_email")
def send_email(to, subject, body):
# your code here
pass
Or track directly:
from authe import get_client
client = get_client()
client.track_action(
tool="custom_tool",
input_data={"key": "value"},
output_data={"result": "done"},
status="success",
)
Supported Frameworks
| Framework | Auto-instrumented |
|---|---|
| OpenAI | ✅ |
| LangChain | ✅ |
| CrewAI | 🔜 |
| AutoGPT | 🔜 |
| Custom agents | via @track decorator |
How it works
authe.init()registers your agent and gets a short-lived token- Actions are captured via monkey-patching (zero code changes needed)
- Actions are batched and sent to the API every 5 seconds
- Your dashboard shows a real-time timeline of everything your agent did
- Scope violations trigger alerts automatically
Links
- Website: authe.me
- Dashboard: dashboard.authe.me
- API Docs: docs.authe.me
- GitHub: github.com/autheme
License
MIT
Metadata
Release files for authe 0.2.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 | |
|---|---|---|---|---|
| authe-0.2.0.tar.gz | 10.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| authe-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.1 kB
Release files / authe-0.2.0.tar.gz
| Download URL | authe-0.2.0.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c207d29d1195c29e8f5d03caeded7062086916db26674bd5c82fd2d37dda59d6
|
|
BLAKE2b-256 checksum How to use checksums |
ef300f92f9032a9b37bb66b2f37d93ea5dcb22d5c41fd0832f38ff9a93d26c7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / authe-0.2.0-py3-none-any.whl
| Download URL | authe-0.2.0-py3-none-any.whl |
|---|---|
| Size | 11.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34522ebeb46eda8390728906d1edeb2deef4292db09d6ae0b9c6120b1baec9cd
|
|
BLAKE2b-256 checksum How to use checksums |
6df9559bf7bf6b32e747ecee2c968ebb05899ee1209c51f4ba60a0535da3ae11
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for authe 0.2.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.