{ "schemaVersion": "1.0", "item": { "slug": "moneyclaw", "name": "Moneyclaw Skill", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/elvismusli/moneyclaw", "canonicalUrl": "https://clawhub.ai/elvismusli/moneyclaw", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/moneyclaw", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=moneyclaw", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "agents/openai.yaml", "references/acquiring.md", "references/payment-safety.md", "SKILL.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-30T16:55:25.780Z", "expiresAt": "2026-05-07T16:55:25.780Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network", "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/moneyclaw" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/moneyclaw", "agentPageUrl": "https://openagent3.xyz/skills/moneyclaw/agent", "manifestUrl": "https://openagent3.xyz/skills/moneyclaw/agent.json", "briefUrl": "https://openagent3.xyz/skills/moneyclaw/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "MoneyClaw", "body": "MoneyClaw gives OpenClaw agents real spending capability with user-configurable autonomy, prepaid risk boundaries, OTP/3DS support, and auditable payment flows.\n\nPrimary use case: buyer-side online purchases for OpenClaw agents.\n\nSecondary use cases: invoices, hosted payment links, and merchant/acquiring workflows when the user explicitly asks for them." }, { "title": "Authentication", "body": "All requests use the same Bearer token.\n\nAuthorization: Bearer $MONEYCLAW_API_KEY\n\nBase URL: https://moneyclaw.ai/api" }, { "title": "Trust Model", "body": "MoneyClaw is designed for real, user-authorized agent payments.\n\nuse prepaid balances to keep risk bounded\nuse a dedicated inbox for OTP and 3DS verification flows\nuse queryable wallet and card history to inspect payment activity\nlet the user choose how much autonomy the agent should have" }, { "title": "Autonomy Model", "body": "MoneyClaw may be used in either approval-based or pre-authorized mode.\n\nIn approval-based mode, the agent asks the user before executing payment actions.\nIn pre-authorized mode, the agent may execute payment actions within the spending scope, balance, and permissions configured by the user." }, { "title": "Safety Boundaries", "body": "Only use MoneyClaw for purchases or payment flows explicitly requested or pre-authorized by the user.\nOnly use wallet, card, and billing data returned by the user's own MoneyClaw account.\nRespect merchant, issuer, card-network, and verification controls, including OTP and 3DS steps.\nTreat fraud checks, KYC, sanctions, geography rules, merchant restrictions, issuer declines, and other payment controls as hard boundaries.\nNever fabricate billing identity, cardholder data, addresses, names, phone numbers, or verification information.\nIf a transaction fails, looks suspicious, or produces conflicting signals, stop and inspect transaction state before retrying.\nPrefer prepaid, bounded-risk flows by default.\nOnly use invoice, merchant, acquiring, or hosted payment-link flows when the user explicitly asks for them." }, { "title": "Default Behavior", "body": "Start with GET /api/me.\nTreat wallet balance and card balance as separate values.\nUse card.cardId, not card.id, for card routes.\nKeep buyer-side purchases as the default path. Use merchant and acquiring flows only when explicitly requested.\nUse the billing address from the sensitive card response. Never invent one.\nNever retry topups or checkouts blindly. Read state first." }, { "title": "Load References When Needed", "body": "Read references/payment-safety.md before entering card details on an unfamiliar merchant, when the user asks about phishing or fraud, when a checkout keeps failing, or when verification and retry boundaries matter.\nRead references/acquiring.md when the user wants to accept payments, create invoices, embed checkout, or work with merchant webhooks." }, { "title": "1. Check account readiness", "body": "curl -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n https://moneyclaw.ai/api/me\n\nImportant fields:\n\nbalance: wallet balance\ncard: current card object or null\ncardBalance.availableBalance.value: card balance when available\ndepositAddress: where to send USDT\nmailboxAddress: inbox address for OTP and receipts\n\nWhen the user asks for balance, show both wallet and card balance. If cardBalance is missing, say card balance is unavailable." }, { "title": "2. Issue a card", "body": "curl -X POST -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n https://moneyclaw.ai/api/cards/issue\n\nRules:\n\nthe wallet needs at least the minimum issuance deposit\nthe wallet is loaded onto the new card\nthe issuance fee is charged from the card after issuance\n\nIf no card exists and the wallet is funded, issue the card. If the wallet is too small, tell the user to fund the deposit address first." }, { "title": "3. Top up the card", "body": "curl -X POST -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"amount\": 10, \"currency\": \"USD\"}' \\\n https://moneyclaw.ai/api/cards/{cardId}/topup\n\nPre-flight checks:\n\nRead GET /api/me.\nConfirm card exists and is active.\nUse card.cardId.\nConfirm wallet balance covers the requested topup.\nOnly then send the topup request.\n\nResponse handling:\n\n200: topup succeeded\n202: topup is still processing; do not send another one yet\n400 INSUFFICIENT_BALANCE: not enough wallet funds\n400 CARD_NOT_ACTIVE: card is not ready\n404 NOT_FOUND: wrong card id\n500: stop, surface the failure, and inspect state before retrying" }, { "title": "4. Complete authorized checkout and fetch OTP", "body": "Get card details:\n\ncurl -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n https://moneyclaw.ai/api/cards/{cardId}/sensitive\n\nGet the latest OTP email:\n\ncurl -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n https://moneyclaw.ai/api/inbox/latest-otp\n\nVerify what actually happened:\n\ncurl -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n \"https://moneyclaw.ai/api/cards/{cardId}/transactions?limit=20&offset=0\"\n\nCheckout rules:\n\nuse the sensitive response for PAN, CVV, expiry, and billing address\nwait 10 to 30 seconds for the OTP email to arrive\nuse extractedCodes[0] as the verification code\nafter any merchant error, read transactions before retrying" }, { "title": "Payment Execution Rules", "body": "The card is prepaid. The loaded balance is the hard spending limit.\nDo not expose PAN or CVV longer than needed for the active checkout.\nBefore payment, confirm the merchant domain and total amount are correct.\nDo not retry the same merchant checkout more than twice in one session without user confirmation or clear pre-authorization.\nIf the user asks for a risky or suspicious payment, stop and explain why.\n\nUse references/payment-safety.md for the expanded safety, verification, subscription, and retry guidance." }, { "title": "Good Default Prompt Shapes", "body": "Check my MoneyClaw account and tell me if it is ready for a purchase.\nIssue a MoneyClaw card and top it up with $20 if needed. Ask before checkout unless I say this purchase is pre-authorized.\nFinish this authorized checkout and, if 3DS appears, fetch the latest OTP from MoneyClaw inbox and verify the final transaction result." }, { "title": "Secondary Capability: Merchant And Acquiring Flows", "body": "MoneyClaw also supports merchant-side payment collection. Keep this as a secondary path in discovery, but use it when the user explicitly wants to accept payments, create invoices, or embed checkout.\n\nUseful endpoints:\n\nPOST /api/acquiring/setup\nGET /api/acquiring/settings\nPATCH /api/acquiring/settings\nPOST /api/acquiring/invoices\nGET /api/acquiring/invoices\nGET /api/acquiring/invoices/{invoiceId}\n\nUse the acquiring flow when the user wants to:\n\naccept USDT payments\ncreate hosted invoices\nembed checkout on a site\nreceive webhook notifications for paid invoices\n\nUse references/acquiring.md for setup, invoice lifecycle, widget, webhook verification, and fee details." }, { "title": "Scope Note", "body": "MoneyClaw supports both buyer-side card purchases and merchant/acquiring flows. Lead with the simpler card-purchase workflow for discovery, then switch to acquiring when the user asks for merchant features." } ], "body": "MoneyClaw\n\nMoneyClaw gives OpenClaw agents real spending capability with user-configurable autonomy, prepaid risk boundaries, OTP/3DS support, and auditable payment flows.\n\nPrimary use case: buyer-side online purchases for OpenClaw agents.\n\nSecondary use cases: invoices, hosted payment links, and merchant/acquiring workflows when the user explicitly asks for them.\n\nAuthentication\n\nAll requests use the same Bearer token.\n\nAuthorization: Bearer $MONEYCLAW_API_KEY\n\n\nBase URL: https://moneyclaw.ai/api\n\nTrust Model\n\nMoneyClaw is designed for real, user-authorized agent payments.\n\nuse prepaid balances to keep risk bounded\nuse a dedicated inbox for OTP and 3DS verification flows\nuse queryable wallet and card history to inspect payment activity\nlet the user choose how much autonomy the agent should have\nAutonomy Model\n\nMoneyClaw may be used in either approval-based or pre-authorized mode.\n\nIn approval-based mode, the agent asks the user before executing payment actions.\nIn pre-authorized mode, the agent may execute payment actions within the spending scope, balance, and permissions configured by the user.\nSafety Boundaries\nOnly use MoneyClaw for purchases or payment flows explicitly requested or pre-authorized by the user.\nOnly use wallet, card, and billing data returned by the user's own MoneyClaw account.\nRespect merchant, issuer, card-network, and verification controls, including OTP and 3DS steps.\nTreat fraud checks, KYC, sanctions, geography rules, merchant restrictions, issuer declines, and other payment controls as hard boundaries.\nNever fabricate billing identity, cardholder data, addresses, names, phone numbers, or verification information.\nIf a transaction fails, looks suspicious, or produces conflicting signals, stop and inspect transaction state before retrying.\nPrefer prepaid, bounded-risk flows by default.\nOnly use invoice, merchant, acquiring, or hosted payment-link flows when the user explicitly asks for them.\nDefault Behavior\nStart with GET /api/me.\nTreat wallet balance and card balance as separate values.\nUse card.cardId, not card.id, for card routes.\nKeep buyer-side purchases as the default path. Use merchant and acquiring flows only when explicitly requested.\nUse the billing address from the sensitive card response. Never invent one.\nNever retry topups or checkouts blindly. Read state first.\nLoad References When Needed\nRead references/payment-safety.md before entering card details on an unfamiliar merchant, when the user asks about phishing or fraud, when a checkout keeps failing, or when verification and retry boundaries matter.\nRead references/acquiring.md when the user wants to accept payments, create invoices, embed checkout, or work with merchant webhooks.\nCore Jobs\n1. Check account readiness\ncurl -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n https://moneyclaw.ai/api/me\n\n\nImportant fields:\n\nbalance: wallet balance\ncard: current card object or null\ncardBalance.availableBalance.value: card balance when available\ndepositAddress: where to send USDT\nmailboxAddress: inbox address for OTP and receipts\n\nWhen the user asks for balance, show both wallet and card balance. If cardBalance is missing, say card balance is unavailable.\n\n2. Issue a card\ncurl -X POST -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n https://moneyclaw.ai/api/cards/issue\n\n\nRules:\n\nthe wallet needs at least the minimum issuance deposit\nthe wallet is loaded onto the new card\nthe issuance fee is charged from the card after issuance\n\nIf no card exists and the wallet is funded, issue the card. If the wallet is too small, tell the user to fund the deposit address first.\n\n3. Top up the card\ncurl -X POST -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"amount\": 10, \"currency\": \"USD\"}' \\\n https://moneyclaw.ai/api/cards/{cardId}/topup\n\n\nPre-flight checks:\n\nRead GET /api/me.\nConfirm card exists and is active.\nUse card.cardId.\nConfirm wallet balance covers the requested topup.\nOnly then send the topup request.\n\nResponse handling:\n\n200: topup succeeded\n202: topup is still processing; do not send another one yet\n400 INSUFFICIENT_BALANCE: not enough wallet funds\n400 CARD_NOT_ACTIVE: card is not ready\n404 NOT_FOUND: wrong card id\n500: stop, surface the failure, and inspect state before retrying\n4. Complete authorized checkout and fetch OTP\n\nGet card details:\n\ncurl -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n https://moneyclaw.ai/api/cards/{cardId}/sensitive\n\n\nGet the latest OTP email:\n\ncurl -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n https://moneyclaw.ai/api/inbox/latest-otp\n\n\nVerify what actually happened:\n\ncurl -H \"Authorization: Bearer $MONEYCLAW_API_KEY\" \\\n \"https://moneyclaw.ai/api/cards/{cardId}/transactions?limit=20&offset=0\"\n\n\nCheckout rules:\n\nuse the sensitive response for PAN, CVV, expiry, and billing address\nwait 10 to 30 seconds for the OTP email to arrive\nuse extractedCodes[0] as the verification code\nafter any merchant error, read transactions before retrying\nPayment Execution Rules\nThe card is prepaid. The loaded balance is the hard spending limit.\nDo not expose PAN or CVV longer than needed for the active checkout.\nBefore payment, confirm the merchant domain and total amount are correct.\nDo not retry the same merchant checkout more than twice in one session without user confirmation or clear pre-authorization.\nIf the user asks for a risky or suspicious payment, stop and explain why.\n\nUse references/payment-safety.md for the expanded safety, verification, subscription, and retry guidance.\n\nGood Default Prompt Shapes\nCheck my MoneyClaw account and tell me if it is ready for a purchase.\nIssue a MoneyClaw card and top it up with $20 if needed. Ask before checkout unless I say this purchase is pre-authorized.\nFinish this authorized checkout and, if 3DS appears, fetch the latest OTP from MoneyClaw inbox and verify the final transaction result.\nSecondary Capability: Merchant And Acquiring Flows\n\nMoneyClaw also supports merchant-side payment collection. Keep this as a secondary path in discovery, but use it when the user explicitly wants to accept payments, create invoices, or embed checkout.\n\nUseful endpoints:\n\nPOST /api/acquiring/setup\nGET /api/acquiring/settings\nPATCH /api/acquiring/settings\nPOST /api/acquiring/invoices\nGET /api/acquiring/invoices\nGET /api/acquiring/invoices/{invoiceId}\n\nUse the acquiring flow when the user wants to:\n\naccept USDT payments\ncreate hosted invoices\nembed checkout on a site\nreceive webhook notifications for paid invoices\n\nUse references/acquiring.md for setup, invoice lifecycle, widget, webhook verification, and fee details.\n\nScope Note\n\nMoneyClaw supports both buyer-side card purchases and merchant/acquiring flows. Lead with the simpler card-purchase workflow for discovery, then switch to acquiring when the user asks for merchant features." }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/elvismusli/moneyclaw", "publisherUrl": "https://clawhub.ai/elvismusli/moneyclaw", "owner": "elvismusli", "version": "5.2.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/moneyclaw", "downloadUrl": "https://openagent3.xyz/downloads/moneyclaw", "agentUrl": "https://openagent3.xyz/skills/moneyclaw/agent", "manifestUrl": "https://openagent3.xyz/skills/moneyclaw/agent.json", "briefUrl": "https://openagent3.xyz/skills/moneyclaw/agent.md" } }