PaySpawn — On-Chain Spending Limits for AI Agents

Add spending controls to any AI agent that makes API payments. Supports x402 auto-pay, daily limits, per-transaction limits, address allowlists, and fleet pr...

This skill appears internally consistent for enforcing on-chain spending limits, but you should not hand it real funds without verification. Before installing or using it: (1) verify the npm package (@payspawn/sdk) and its maintainer (check the package page, author, and GitHub repo source code and commit history); (2) verify the smart contract address and source on Base (review verified contract code on a block explorer); (3) confirm the payspawn.ai dashboard domain is legitimate (check HTTPS, WHOIS, social proof); (4) test with a fresh wallet and a very small USDC amount and set conservative caps/whitelists; (5) store the PAYSPAWN_CREDENTIAL securely (it grants on-chain spend permissions within limits); (6) be cautious of npm typosquatting or malicious dependencies — audit dependencies before running in production. If you need higher assurance, ask the publisher for links to a verified GitHub repo and contract verification proof before trusting substantial funds.

Type: OpenClaw Skill Name: payspawn Version: 1.0.3 The OpenClaw skill bundle 'payspawn' is designed to provide spending controls for AI agents making API payments. The `SKILL.md` file clearly outlines its purpose, installation steps, and usage, emphasizing security features like scoped credentials (not private keys), on-chain enforcement of limits, and revocability. There is no evidence of intentional malicious behavior such as data exfiltration, unauthorized remote execution, persistence mechanisms, or prompt injection attempts against the agent. The skill's core functionality involves network requests and payments, which are high-risk by nature, but the skill is explicitly designed to manage and control these actions securely, aligning with its stated purpose.