Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.agentsystems.ai/llms.txt

Use this file to discover all available pages before exploring further.

This guide covers verification for custodied hash storage (AgentSystems API). For Arweave (decentralized) verification, see Independent Verification.
Verification compares logs against AgentSystems records to identify any discrepancies. Anyone with an audit ticket can verify — your customers, their compliance teams, or third-party reviewers.

​
What You Need

ItemHow to Get It
Audit TicketGenerate from notary.agentsystems.ai → Tenants → Audit
Logs ZIPExport from your S3 bucket (commands shown in the Audit modal)
The audit ticket is a signed token that grants access to check logs against AgentSystems records for a specific tenant and date range.

​
Running Verification

  1. Go to verify.agentsystems.ai
  2. Upload the audit ticket (.json)
  3. Upload the logs (.zip)
  4. Click Start Verification
No account is required to run verification.

​
Understanding Results

ResultMeaning
Verified RecordsRecords in the ZIP that match AgentSystems records
Unrecognized RecordsRecords in the ZIP that weren’t recorded by AgentSystems
Missing RecordsRecords that AgentSystems recorded but aren’t in the ZIP

​
Attestation Packets

After verification, download an attestation packet — a self-contained proof bundle you can share with customers, compliance teams, or regulators. Recipients can verify the cryptographic signature themselves without needing to re-run verification or trust your word.

​
Verifying the Signature

The attestation certificate is signed with AgentSystems’ notary key. To verify independently: 
# Download the public key
curl -o notary.pem https://verify-api.agentsystems.ai/.well-known/notary.pem

# Verify the signature
openssl dgst -sha256 -verify notary.pem -signature attestation.pdf.sig attestation.pdf
Expected output: Verified OK