receipts-guard

What This Skill Does

RECEIPTS-GUARD provides the fundamental infrastructure for the autonomous machine economy. By leveraging ERC-8004 for on-chain identity, the x402 payment standard for automated settlements, and a robust arbitration protocol, this skill enables agents to conduct secure, trustless commerce. It acts as the legal and financial backbone for AI agents, allowing them to issue proposals, sign Programmable Agreement Objects (PAOs), and resolve contractual disputes without human intervention. The v0.7.1 update introduces critical security hardening, including HTTP authentication, rate limiting, and CORS configuration to ensure production-grade deployment.

Installation

To integrate receipts-guard into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/lazaruseth/receipts-guard

Ensure your node environment is prepared with the necessary dependencies for the CLI interface. You can initialize your agent's identity using node capture.js identity init by specifying your namespace and controller Twitter handle, which provides a human-readable recovery backstop for your agent's DID.

Use Cases

• Autonomous Service Provisioning: Agents can sell compute resources, API access, or data processing, with receipts-guard handling the payment and dispute resolution terms.
• Machine-to-Machine Settlements: Automate payments using USDC or ETH triggered strictly upon the fulfillment of verified agreement criteria.
• Dispute Resolution: Handle contractual disagreements through a programmed arbitration process, where an arbiter reviews evidence and issues final, binding rulings on-chain.
• Identity Verification: Establish a verifiable, rotating key-based identity that proves the agent's legitimacy to third-party services.

Example Prompts

1. "Propose a new agreement to AgentX for data cleaning services, set the deadline for Friday, and lock the fee at 50 USDC using the receipts-guard protocol."
2. "Check the status of agreement agr_xyz789 and submit the latest API documentation link as proof of fulfillment."
3. "Open a formal arbitration case for agreement agr_xyz789 because the counterparty failed to deliver the promised dataset by the agreed deadline."

Tips & Limitations

• Security: Always configure the CORS whitelist and API keys in your environment variables before moving to a cloud-deployed server mode.
• Identity: Regularly rotate your keys using the built-in rotation command to maintain a secure proof chain.
• Arbitration: Ensure that your arbitration outcomes are well-documented with clear evidence to avoid unfavorable rulings.
• Limitations: This skill is strictly for agents that can interact with the Ethereum/Base registries; it is not intended for off-chain-only operations where blockchain finality is irrelevant.