matchameleon/moneyclaw — explained in plain English
Analysis updated 2026-05-18
Give an OpenClaw AI agent a prepaid wallet to make online purchases within a set spending limit.
Set up recurring subscription payments that an AI agent can manage on a user's behalf.
Check payment task status and account inbox messages through the MoneyClaw skill.
| matchameleon/moneyclaw | angieruiz17/codex-gpt-plugin | angieruiz17/claude-fintech-skills | |
|---|---|---|---|
| Stars | 135 | 135 | 134 |
| Language | JavaScript | JavaScript | JavaScript |
| Setup difficulty | moderate | hard | easy |
| Complexity | 3/5 | 4/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires an OpenClaw environment, a MoneyClaw API key, and clawhub to install the skill.
This repository is the public documentation and skill for MoneyClaw, a system that gives OpenClaw agents a prepaid wallet so they can make online payments on a person's behalf. Instead of handing an AI agent a real credit card directly, MoneyClaw sits in between: the agent can check a wallet balance, create payment tasks, set up recurring subscriptions, complete a browser checkout, read messages in an account inbox, and confirm that a transaction went through. Behind the scenes, one hidden card tied to the account is reused for actual execution, but that card is treated as an internal detail rather than something the agent handles directly. The safety model is built around keeping risk limited and visible. Balances are prepaid, so spending is capped ahead of time. Payment tasks and subscriptions carry approval and audit information, receipts and messages stay in a dedicated inbox, and a user can choose to require manual approval for each payment or turn on automatic approval at the account level. The README is explicit that MoneyClaw is meant only for payments the user has authorized, and it is not designed to get around identity checks, fraud rules, or other verification controls that banks and merchants use. To get started, someone installs the MoneyClaw skill into OpenClaw with a command line tool called clawhub, creates an API key, and stores it as an environment variable inside OpenClaw. From there, a fresh OpenClaw session can be asked to check whether the wallet, inbox, and payment tasks are ready before making its first purchase. This particular repository is described as only the public facing piece of the project: documentation, the OpenClaw skill files, and example prompts. Internal infrastructure details, incident reports, and private operational notes are kept out of it on purpose. For local development, the repository also includes optional Redis based helpers for caching and locking, used mainly by people building tools around the public API rather than by typical skill users. The project is released under the MIT license.
A prepaid wallet system that lets OpenClaw AI agents make authorized online payments through a capped, auditable execution layer.
Mainly JavaScript. The stack also includes JavaScript, Node.js, Redis.
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.