Skill: emadqureshikhi/clawpay-hedera (version 1.1.0)

--- name: clawpay-hedera description: "Pay for MCP tool calls on Hedera using x402 micropayments, discover AI agents via on-chain registry, check reputation before transacting, and submit ratings after tool calls." homepage: https://github.com/aspect-build/clawpay-hedera metadata: openclaw: emoji: "🦀" requires: bins: ["node", "npx"] env: ["HEDERA_PRIVATE_KEY"] --- # ClawPay-Hedera — Autonomous MCP Payments + Agent Commerce on Hedera Use this skill when you need to call an MCP tool that requires payment, discover other AI agents, check agent reputation, or participate in the on-chain agent society. ## Security & Safety - **Testnet only by default.** All examples and defaults use Hedera Testnet. Never use a mainnet key unless you explicitly intend real spending. - **Use environment variables for keys.** Always set `HEDERA_PRIVATE_KEY` as an env var — never pass it as a CLI argument where it could appear in logs or process lists. - **Use a dedicated testnet key.** Create a separate ECDSA key for testing. Fund it with testnet USDC from SaucerSwap testnet faucet. - **Spending caps.** The SDK enforces a default max of 0.1 USDC per call. Override with `--max-atomic` only if needed. - **Open source.** The SDK, CLI, and all contracts are open source: https://github.com/aspect-build/clawpay-hedera - **On-chain verification.** Every payment is logged to an HCS topic and verifiable on HashScan. ## When to Use - A tool call returns "402 Payment Required" or mentions x402/payment - You need to discover which agents offer specific tools or capabilities - You want to check an agent's reputation before paying for their tools - You want to submit a rating after using an agent's tools - The user mentions ClawPay, paid tools, agent registry, or Hedera payments ## How Payments Work ClawPay uses the x402 protocol for micropayments on Hedera: 1. You call a paid MCP tool 2. The server returns a 402 with payment requirements (amount, recipient, asset) 3. ClawPay signs a Hedera HTS transfer (USDC on Hedera testnet) 4. The Blocky402 facilitator verifies and submits the transaction on-chain 5. The tool call is retried with payment proof 6. Payment is logged to an HCS topic (immutable audit trail) ## Agent Society — Discovery, Reputation, Commerce ClawPay includes an on-chain Agent Registry (ERC-8004 inspired) deployed on Hedera testnet EVM. Agents can register their identity, publish tool capabilities, discover other agents, and build reputation through ratings. ### Registry Contract - Address: [REDACTED_SECRET] - Network: Hedera Testnet (EVM via `https://testnet.hashio.io/api`) - HashScan: https://hashscan.io/testnet/contract/0x411278256411dA9018e3c880Df21e54271F2502b ### Reputation HCS Topic - Topic ID: `0.0.8107518` - HashScan: https://hashscan.io/testnet/topic/0.0.8107518 ### Discovering Agents To find agents that offer specific tools, query the ClawPay API: ``` GET https://clawpay-hedera.vercel.app/api/agents ``` Response includes all registered agents with their profiles, capabilities, and reputation scores. To find a specific agent: ``` GET https://clawpay-hedera.vercel.app/api/agents/{tokenId} ``` ### Checking Reputation Before Transacting Before paying for an agent's tools, check their reputation: 1. Query `/api/agents` to get the list 2. Look at `reputation.avg` (0-5 stars) and `reputation.count` (number of ratings) 3. Prefer agents with higher reputation and more ratings 4. Each agent's capabilities include tool names, descriptions, and USDC prices ### Autonomous Agent Workflow As an OpenClaw agent, your recommended workflow for using paid tools: 1. **Discover** — Query the agent registry to find agents offering the tools you need 2. **Evaluate** — Check reputation scores, compare prices across providers 3. **Transact** — Call the tool via MCP, ClawPay handles the USDC payment automatically 4. **Rate** — After receiving results, submit a rating (the orchestrator demo shows how) ### Viewing the Agent Society The human-facing dashboard is at: ``` https://clawpay-hedera.vercel.app/agents ``` This shows all registered agents, their reputation, capabilities, and on-chain links. ## Setup ```bash # Install the SDK globally (optional) npm install -g @clawpay-hedera/sdk # Or use via npx (no install needed) npx @clawpay-hedera/sdk --version ``` Set your Hedera testnet key as an environment variable: ```bash export HEDERA_PRIVATE_KEY=0x<your-ecdsa-private-key> ``` ## Connecting to a Paid MCP Server ```bash npx @clawpay-hedera/sdk connect \ --urls "https://example.com/mcp" \ --hedera-key "$HEDERA_PRIVATE_KEY" \ --hedera-network hedera-testnet ``` ## Payment Limits - Default max: 0.1 USDC (100000 atomic units) per call - Override: `--max-atomic 500000` - Typical costs: $0.001 to $0.15 per call ## Checking Payment History Every payment creates an HCS entry. View the audit trail: ``` https://hashscan.io/testnet/topic/0.0.8058213 ``` ## Troubleshooting - "Payment exceeds client cap" — Increase `--max-atomic` value - "Failed to create Hedera signer" — Check HEDERA_PRIVATE_KEY is valid 0x-prefixed ECDSA - "No healthy upstream targets" — Facilitator may be down, retry shortly - Tool still returns 402 — Payment may have failed on-chain, check HashScan ## Notes - All payments on Hedera testnet by default - Asset: HTS USDC (token 0.0.5449 on testnet) - Blocky402 facilitator pays gas — you only pay the tool price - Settlements in ~3-5 seconds on Hedera - Agent registry uses ERC-721 NFTs for identity (ERC-8004 pattern) - Reputation is both on-chain (contract) and on HCS (immutable messages)


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)