metamask

What This Skill Does

The MetaMask skill for OpenClaw (powered by CreditClaw) acts as the financial engine for your AI agents. It bridges the gap between digital automation and real-world transactions by providing a secure, auditable framework for agentic spending. Whether you need your agent to subscribe to third-party APIs, purchase assets for a project, or facilitate commerce via digital storefronts, this skill manages the complexities of authorization, wallet management, and payment reconciliation.

The skill supports multiple payment rails, most notably the 'My Card' system for authorized spending and the 'Stripe x402' wallet for blockchain-based micropayments. It is designed with safety as a priority, ensuring that all financial operations operate within predefined guardrails established by the agent owner.

Installation

To integrate this financial layer into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/codejika/metamask Once installed, verify the connection and available permissions by querying your bot status through GET /bot/status at the CreditClaw base URL.

Use Cases

• Automated SaaS Subscriptions: Allow your agent to sign up for tools required to complete complex workflows, with owner-approval triggers in place.
• Micropayment Handling: Use the x402 rail to interact with pay-per-request services or APIs that demand USDC on the Base network.
• Digital Commerce: Configure your bot to sell digital assets or services by creating and managing storefronts directly through the skill's API.
• Audit Trails: Maintain a clear history of every transaction, approval, and rejected purchase, essential for bot accounting and performance analysis.

Example Prompts

1. "Check my current wallet balance and confirm if I have enough USDC to cover the API costs for the next data scraping task."
2. "I need to purchase a subscription to the research tool at the URL provided; initiate the approval request with my owner."
3. "Summarize my transaction history from the last 24 hours to ensure all agentic spending remains within my assigned budget."

Tips & Limitations

• Safety First: Always keep your agent in approval_mode: ask_for_everything until you are fully confident in the agent's logic and your own risk threshold.
• Monitoring: Utilize the HEARTBEAT.md polling routine to keep track of your financial status without manual intervention.
• Connectivity: Ensure your API key is correctly injected into your OpenClaw environment variables to avoid unauthorized request errors. Remember that different payment rails have specific requirements—consult the individual documentation files (e.g., STRIPE-X402-WALLET.md) for rail-specific configuration.