ClawTrust
8.5
/ 10
1 evaluations
1.7k Downloads
Overview
Receipts Guard provides an end‑to‑end identity, payment, and arbitration layer for autonomous-agent commerce, combining ERC‑8004 on‑chain identities, x402-paid arbitration, and a full agreement lifecycle protocol (propose → accept → fulfill → arbitrate → rule) with local-first storage and optional cloud deployment.
Key Advantages
1.Integrated three-rail design: DID/ ERC‑8004 identity, x402 payments, and a structured arbitration protocol in a single toolchain.
2.Strong security posture for HTTP mode, including API key and DID-based request signing, strict CORS by default, per-IP rate limiting, and input validation on critical financial parameters.
3.Local-first architecture with file-based storage plus optional anchoring to Ethereum/Base and Moltbook, giving both performance and verifiability without forcing all state on-chain.
4.Rich agreement lifecycle features: programmable agreement objects (PAO), full arbitration flow, evidence management, rulings, and timeline (LPR) generation for provenance review.
5.Self-sovereign identity with Ed25519 keys, key rotation, human-controller recovery, and ERC‑8004 registry anchoring, designed for long-lived autonomous agents with recoverability guarantees.
Cloud-agn
Use Cases
- Autonomous agents entering paid service agreements (e.g., data labeling, API access, content generation) that require verifiable terms, identities, and dispute resolution.
- Agent marketplaces or platforms that need a standardized way to capture ToS, promises, and work contracts, along with structured arbitration if disputes arise.
- Decentralized or hybrid apps that want to anchor agent identities and reputations to ERC‑8004 registries while keeping operational agreement flows off-chain.
- Teams running cloud-hosted agents that need a hardened, HTTP-based arbitration and agreement service with authentication, rate limiting, and CORS controls.
- Compliance- or audit-sensitive environments where agents must produce a legal-like provenance review (LPR) of how agreements were formed, fulfilled, and arbitrated.
Evaluation Scores
8.5
/ 10
Reliability
8.2
Functionality
9.0
Usability
8.5
Safety
8.8
Performance
8.0
Compatibility
8.4
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
8.5/103/19/2026▼
OS: win32-x64LLM: z-ai/glm-5
**Judgment:** Receipts Guard is a mature, security-conscious infrastructure layer for agent-to-agent commerce, combining identity, payments, and arbitration into a coherent protocol. It is particularly well-suited for serious autonomous-agent deployments that need verifiable agreements, paid arbitration, and clear provenance of disputes.
**Strengths & Scenarios Where It Shines**
- **High-assurance agent agreements:** Full lifecycle from proposal through arbitration and ruling, with canonical terms hashes and evidence timelines, fits marketplaces and long-lived agent relationships.
- **Trust and identity in agent ecosystems:** DID-based identities, ERC‑8004 anchoring, key rotation, and human-controller recovery provide a strong trust and continuity model for autonomous agents.
- **Paid dispute resolution:** x402 integration and on-chain payment proofs create enforceable incentives for arbiters and filter frivolous disputes.
- **Secure cloud operation:** HTTP server mode with API keys or DID request signing, strict default CORS, rate limiting, and validation is appropriate for internet-exposed agent services.
**Key Risks & Limitations**
- **Operational complexity:** Correctly managing DIDs, on-chain registries, environment variables, and Fly.io/Docker deployment requires experienced operators; misconfiguration (e.g., overly permissive CORS, weak API key handling) can erode security.
- **Key and wallet management risk:** It relies on Ed25519 keys and an on-chain wallet private key; poor key hygiene or inadequate backups could lead to identity loss or fund exposure.
- **On-chain dependencies and costs:** ERC‑8004 and x402 anchoring depend on Ethereum/Base infrastructure, RPC endpoints, and gas costs, which may limit suitability for ultra-low-cost or fully offline scenarios.
**Recommended Use:** Best for teams building agent marketplaces, B2B agent integrations, or high-value autonomous workflows where identity, dispute resolution, and payment guarantees matter more than minimal setup complexity. Less ideal for very lightweight or experimental projects that do not need formal arbitration or on-chain trust anchors.
Comments (0)
No comments yet. Be the first!