Integration: Cryptographic tool-call receipts from Signet

[willamhou]

AgentOps captures the observability side of agent runs well. A complementary layer is cryptographic evidence: proving what each tool call sent, who signed it, and that the audit trail hasn't been tampered with.

Signet generates Ed25519-signed receipts for every tool call, chained into a tamper-evident audit log. It already integrates with the same frameworks AgentOps supports (LangChain, CrewAI, OpenAI Agents SDK, Pydantic AI).

A lightweight integration could:

1. Attach the Signet receipt ID to the AgentOps event for cross-referencing
2. Surface signed/unsigned status in the AgentOps dashboard
3. Let users export AgentOps sessions with cryptographic proof attached

Signet is local-first (no SaaS dependency, offline-verifiable), so it wouldn't require users to create accounts with a third party. The receipts are JSON with Ed25519 signatures — straightforward to include as event metadata.

Available as pip install signet-auth (Python) and npm install @signet-auth/core (TypeScript).

Happy to prototype the integration or discuss what telemetry signals would be most useful.

[0xbrainkid]

Cryptographic tool-call receipts address a real gap — AgentOps captures the observability record, but that record is mutable (log files, databases) rather than tamper-evident. Signet receipt IDs cross-referenced in AgentOps events would let operators distinguish "this event was observed and logged" from "this event was signed and is cryptographically provable."

A few additions to the integration that would make it more valuable for cross-org trust:

1. Agent identity on each receipt. A Signet receipt proves what tool call happened and that the log has not been tampered with. Adding the agent identity (from AgentFolio verification or SATP) to the receipt signature ties the tool call to a specific verifiable agent, not just a session. This enables cross-org audit: "agent X with trust score 0.91 called tool Y at timestamp Z, here is the signed proof."

2. Receipt chain as behavioral attestation source. A sequence of signed receipts for an agent across many sessions is a behavioral track record — verifiable, tamper-evident, and attributable. AgentFolio could consume Signet receipt chains as one input to behavioral trust scoring: agents with clean, complete receipt chains earn higher trust scores than agents with gaps or unsigned events.

3. Export format for compliance. The EU AI Act Article 12 requires "records of operations of AI systems." A Signet-signed AgentOps export (session metadata + receipt chain + agent identity attestation) is a machine-verifiable compliance artifact. Much stronger than log files alone.

The Signet + AgentOps + AgentFolio stack is a natural fit: Signet = tamper-evident what, AgentOps = observability context, AgentFolio = verifiable who.