How It Works
- Record - The SDK captures LLM interactions as they happen
- Dual-Write - Raw logs go to your S3 bucket. SHA-256 hashes go to your chosen storage.
- Verify - Anyone with an audit ticket can verify logs
Hash Storage Options
Notary supports two hash storage methods. You can use one or both.| Option | Description | Verification |
|---|---|---|
| Arweave | Hashes stored on public blockchain | Independent verification with open-source CLI |
| Custodied | Hashes stored by AgentSystems API | Via portal |
agentsystems-verify CLI. No vendor lock-in.
Custodied is a managed option if you prefer AgentSystems to handle the complexity. Verify through our portal.
Components
| Component | URL | Purpose |
|---|---|---|
| Dashboard | notary.agentsystems.ai | View tenants, manage API keys, generate audit tickets |
| Verification Portal | verify.agentsystems.ai | Verify logs and download attestation packets |
| SDK | PyPI | Python SDK for LangChain and CrewAI |
| Verify CLI | npm | Open-source CLI for Arweave verification |
Key Concepts
Tenants represent your customers. They’re auto-discovered when the SDK logs its first interaction with a given slug. You don’t need to create them in advance. Audit Tickets are signed tokens that grant access to verify logs for a specific tenant and date range. They don’t contain the hashes themselves — they authorize the verification portal to check logs against AgentSystems records. Attestation Packets are self-contained proof bundles you can share with customers, compliance teams, or regulators. They contain the logs, audit ticket, a signed attestation certificate, and instructions for independent signature verification — everything needed to confirm the logs were checked against AgentSystems records.Quickstart
End-to-end tutorial: signup → integration → verification