Tamper-evident action log

Every agent action sealed with a SHA-256 content hash and chained to the record before it. Re-verify the whole chain anytime — any edit after the fact breaks it, loudly.

THE PROBLEM

“The agent did it” is not an audit trail.

When an autonomous agent exports an invoice, changes a record, or emails a customer, someone will eventually ask: what exactly happened, and can you prove the log wasn't cleaned up afterwards? An ordinary application log can be edited by anyone with database access — it proves nothing.

CanaryAudit seals every action with a SHA-256 content hash at write time and chains each record to the previous one. Recompute the hashes anytime — you, your customer, an auditor, opposing counsel. A record edited after sealing breaks its hash; a deleted record breaks the chain. History becomes something you can demonstrate, not just assert.

Send actions to the API

One call per action from your agent framework — actor, action, payload. One HTTPS call with your API key.

Records are hashed and chained

Each record's SHA-256 covers its content plus the previous record's hash — an unbroken chain from the first action.

Re-verify on demand

One click (or one API call) recomputes the whole chain. Intact means untouched; a break tells you exactly which record changed.

WHAT YOU GET

Everything reports into the same console.

curl -X POST https://api.canaryvaults.com/canaryaudit/log \
  -H "X-API-Key: $CV_KEY" -H "Content-Type: application/json" \
  -d '{
    "user_id": "<your-user-uuid>",
    "agent_id": "billing-agent",
    "action_type": "invoice_export",
    "input_trigger": "cron:invoice-run",
    "action_detail": "Exported invoice batch 2026-08 to S3",
    "outcome": "success"
  }'
# → record id + content hash, returned for independent verification

The response carries the record id and a 64-character content hash. Hand over the content hash — the public verifier takes that and rejects a record id.

Is this court-admissible evidence?

It's tamper-evident, not automatically admissible — we prove a record hasn't changed since logging. Whether that satisfies a court is a legal question for your counsel; the PDF export gives them everything they need to make that argument.

Where is my data stored?

In your workspace. Verification only needs the hashes — you can keep payloads in your own systems and send content hashes alone if your data can't leave.