Screenshots for AI agents via x402

Browser screenshots and vision over MCP Streamable HTTP with x402 USDC micropayments at this deployment. Paid tools require an x402-aware MCP client and a fu...

This skill is coherent for remote, paid screenshot capture, but take these precautions before using it: - Read https://screenshotx402.com/discovery.json and call the free health tool to confirm pricing, network (e.g., base), and mcp.url before any paid call. - Understand that any URL you submit (and prompts for analyze_screenshot) will be fetched and rendered on the operator's infrastructure — do NOT submit non-public or sensitive URLs or URLs containing secrets. - Paid features require an x402-aware MCP client and on-chain USDC signing. Confirm how your platform will provide/store signing keys (do not paste private keys into prompts). Prefer a secure platform vault; verify who controls the private keys. - The skill metadata did not list required environment variables even though the docs reference AGENT_PRIVATE_KEY / X402_PRIVATE_KEY; ask the publisher or your platform how those credentials are expected to be provided and whether any automatic billing/charges can occur. - Test with the free health endpoint first and verify the deployment identity and TLS cert for https://screenshotx402.com. If you need to capture sensitive content, prefer local/self-hosted tooling instead of this remote paid service. - If you are uncertain about the facilitator or on-chain flow, consult an ops/devops person familiar with MCP/x402 before enabling paid calls.

Type: OpenClaw Skill Name: screenshots-for-ai-agents Version: 1.0.1 The skill bundle (SKILL.md) describes a remote screenshot service that requires USDC micropayments via the x402 protocol, instructing the agent to use private keys (e.g., `AGENT_PRIVATE_KEY`) for signing transactions. It directs all data, including URLs and vision prompts, to an external endpoint (https://screenshotx402.com/mcp) for off-host processing. While these behaviors are aligned with the stated service purpose, the requirement for wallet secrets and the potential for unauthorized financial transactions or data exposure via the remote service represent significant security risks.