clawpay

What This Skill Does

The Clawpay skill is a robust, hybrid payment orchestration layer designed for the OpenClaw ecosystem. It bridges the gap between AI-driven task execution and monetary settlement. By providing a standardized API for creating payment requests, tracking transaction status through polling, and delivering results post-payment, Clawpay allows AI agents to act as service providers or intermediaries. Whether an agent is performing a data analysis, summarizing a document, or executing a custom function, Clawpay ensures the agent is compensated for its compute time and effort before exposing sensitive outputs.

Installation

To integrate Clawpay into your local OpenClaw agent, execute the following command in your terminal:

clawhub install openclaw/skills/skills/kirch/clawpay

For manual local installation, create a directory at ~/.openclaw/skills/clawpay and use curl to fetch the SKILL.md, HEARTBEAT.md, and package.json files from the official repository URLs. Ensure your environment variables are configured if you intend to use a default PAY_TO address.

Use Cases

• Agent-to-Agent Marketplace: Use Clawpay to pay a secondary specialized agent to process a specific complex prompt that requires a subscription or fee.
• Human-to-Agent Service: Allow a human user to request a report or piece of generated media, where the agent generates the content only after the human completes the payment.
• Subscription Tiers: Restrict access to high-compute features by requiring a micropayment for every execution.

Example Prompts

1. "Clawpay, create a payment request for 10 USDC to generate a financial report on the latest market trends, and send the request link to my workspace."
2. "Check the status of request ID req_99283; if it has been paid, proceed with the delivery of the analysis file."
3. "Set my default receiving address to 0x... and start listening for payment requests for the new data scraping task."

Tips & Limitations

• Polling Efficiency: Do not poll the status endpoint more than once every 5 seconds to avoid rate limiting on the API server.
• Security: Always verify the payment status via a server-side request before delivering sensitive payload data. Never rely solely on client-side notification triggers.
• Error Handling: Ensure your agent handles HTTP 402 codes gracefully, as this indicates the payment has not yet been processed for the specific resource.