Signed receipts for AI agents, no trust required

What it does

asqav-sdk provides Python and TypeScript clients for the Asqav evidence layer, generating signed compliance receipts for AI agent actions. Because all cryptography runs server-side, the SDKs are thin, zero-dependency wrappers: you call agent.sign() and receive a hash-chained, witness-timestamped receipt signed with ML-DSA-65 under FIPS 204. Anyone can then verify that receipt offline or online without an Asqav account or trust in the vendor.

The interesting bit

The verification design is deliberately adversarial: the docs include a fake signature_id that returns verified: false, teaching users that a proper verifier must refuse bad evidence rather than wave it through. For the truly paranoid, verify_receipt_offline reproduces the signature check locally using the receipt’s own declared algorithm—ML-DSA-65 for cloud receipts, Ed25519 or ES256 for local ones—so you never have to take the vendor’s word for it.

Key highlights

• Post-quantum signing via ML-DSA-65 (FIPS 204) with zero native dependencies in either SDK.
• Portable receipts verifiable by anyone without an Asqav account; chain hashes are recomputed locally using RFC 8785 canonical JSON.
• Offline verification path that validates the actual signature algorithm declared in the receipt rather than calling home.
• Cross-language conformance fixtures keep the Python and TypeScript SDKs in lockstep; CI reruns both whenever shared tests change.
• Profiled in an IETF Internet-Draft and aligned with NIST, RFC 8785, and NSA CSI standards.

Caveats

• The SDKs are thin API clients, not standalone cryptographic tools; signing always requires the Asqav service and an API key.
• Released under the Elastic License 2.0, which carries usage restrictions not found in standard open-source licenses.
• Some capabilities are plan-gated across Free, Pro, and Enterprise tiers.

Verdict

Worth evaluating if you need auditable, tamper-evident records of AI agent behavior for compliance or counterparty trust. Skip it if you require a fully offline, self-hosted signing authority; the cryptography lives on Asqav’s servers, not yours.