swarrm 0.3.2

Swarrm — signed receipts + transparency log + offline verification for AI agent actions

Swarrm

Swarrm makes AI agents auditable. Every action an AI agent takes — a decision, a payment, a data access — becomes a signed receipt in a tamper-evident log, exportable as a self-contained evidence bundle that any party it is shared with can verify offline. This makes AI insurable, and every interaction — with other agents, customers, counterparties, vendors, even attackers — generates legal evidence.

Companies running agents that take real actions (call models, run tools, approve refunds, move money) need proof of what happened when a dispute, audit, or regulator shows up — proof their own editable logs cannot provide. Payloads never leave the customer; we hold only hashes.

Quickstart

pipx install swarrm                     # Python 3.11+ (or: pip install swarrm)
swarrm demo                             # agent traffic → receipts → bundle → VERIFIED
swarrm verify demo_out/bundle.json      # (the demo tampers one byte → NOT VERIFIED)

Two minutes, no account, fully local. Hosted trial: one curl on swarrm.ai/quickstart. (Developing on the source tree instead: pip install -e ".[dev]".)

swarrm is the whole surface — one word, not a folder of services: up (the dev stack), demo, verify BUNDLE, wrap -- CMD (MCP capture), incident, status, and doctor (effective config + is it even recording?). Config is one knob: EVD_PROFILE=dev|trial|edge sets every defaultable variable, and swarrm doctor prints what's effective and what's missing. (evd stays as a back-compat alias; python -m pytest runs the full suite.)

Verify any bundle offline, any time: swarrm verify <bundle.json> — or, with no account, drop it into the in-browser verifier at swarrm.ai/verify, which checks it entirely client-side, nothing leaving the page. The verifier is open source (github.com/capxholding/swarrm-verify, Apache-2.0) — a second, independent Rust implementation that must agree with this package's Python verifier on a shared adversarial fixture suite. Put the "verify it yourself" trust badge (/verify/badge) on your own site.

Orientation

core/ cryptographic log (RFC 6962), receipts (DSSE/Ed25519), checkpoints · proxy/ recorder/ mcpwrap/ sdk/ plane/otel.py capture surfaces · anchor/ L2 anchoring + RFC 3161 timestamps · verify/ verify-rs/ offline verifiers · plane/ console/ report/ detect/ packs/ control plane, console, evidence reports, detection, compliance packs · SPEC/ normative wire formats.

Docs

Start with docs/A_BUILD.md — the execution runbook and single source of truth for what is built and what is next; all plans (website, hardening backlog, launch materials) are folded into its appendix. Then docs/THREAT_MODEL.md and the per-feature notes. The four design laws are non-negotiable: fail-open, payloads never persist, claims ≤ mechanism, boring crypto only. The brand is Swarrm; the wire-format namespace evd/* is frozen forever — never rename signed or anchored identifiers.