clawtarEnable autonomous agent payments by detecting HTTP 402 paywalls, settling Cashu challenges, retrying with tokens, and completing paid requests end-to-end.
Install via ClawdBot CLI:
clawdbot install robwoodgate/clawtarGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
POST → https://clawtar.cashutools.dev/v1/clawtar/ask`Calls external URL not in known-safe list
https://clawtar.cashutools.dev/v1/clawtar/ask`AI Analysis
The skill's external endpoint is explicitly documented and central to its stated demo purpose of practicing Cashu payment flows. No hidden instructions, credential harvesting, or obfuscation are present. The primary risk is the inherent uncertainty of an external API not on a pre-approved safe list, but the skill includes clear safety checks and permission prompts.
Audited Apr 17, 2026 · audit v1.0
Generated Mar 21, 2026
Developers use this skill to test and debug AI agents handling HTTP 402 payment challenges, ensuring agents correctly parse x-cashu headers, settle payments via cocod, and retry requests with tokens. It provides a safe sandbox for practicing the full Cashu integration loop without real financial risk.
Instructors leverage this skill in training sessions to teach students or teams about Cashu-gated APIs, demonstrating step-by-step payment flows, permission handling, and error recovery. The controlled endpoint allows hands-on learning with predictable outcomes.
Businesses showcase how their AI agents can autonomously handle small payments for services like fortune readings, using this skill to illustrate seamless 402 detection, token settlement, and retry mechanisms. It helps pitch potential use cases in content gating or premium features.
Organizations use this skill to train AI agents on ethical spending protocols, ensuring agents request human permission before using cocod or spending funds. It reinforces safety checks in autonomous systems dealing with financial transactions.
Companies offer basic API services for free but gate advanced features behind Cashu payments, using skills like Clawtar to demo how agents handle 402 responses. Revenue comes from microtransactions per API call, encouraging scalable usage.
Sell subscriptions to tools like cocod or integrated platforms that simplify Cashu payments for AI agents, with Clawtar serving as a demo to attract developers. Revenue is generated through monthly or annual licensing fees.
Offer paid courses or certifications on AI payment integrations, using Clawtar as a hands-on module to teach Cashu flows. Revenue comes from enrollment fees and certification renewals for professionals.
💬 Integration Tip
Always test the payment flow in a sandbox first, and ensure your agent requests human permission before any autonomous spending to comply with safety protocols.
Scored Apr 19, 2026
Access CoinMarketCap data via x402 pay-per-request protocol with USDC payments on Base. Use when users mention x402, want CMC data without API keys, ask abou...
关联交易台账逐项核对（逐行复算、合计勾稽、重复与空缺检测），每条结论引用原文。本免费版执行引擎声明的免费检查项。触发词包括 关联方交易与同期资料一致性核对、关联交易台账对不上。
Plisio integration. Manage Invoices, Payouts, Wallets, Transactions, Users. Use when the user wants to interact with Plisio data.
Send and receive money via Venmo using Strider Labs MCP connector. Pay friends, request payments, split bills, check balances. Complete autonomous P2P paymen...
Send and receive money via PayPal using Strider Labs MCP connector. Send payments, request money, check balance, view transactions. Complete autonomous onlin...
Operate the abracadabra local secrets vault (abra CLI, abra serve, abra MCP) only when the user names abracadabra or abra, the abracadabra MCP is registered, or ABRA_KEY is already set for this project. Covers discovering key names, reading secrets the human has scoped to this agent (issued abra key or Touch ID grant), key issue/scope/revoke, health checks, keygen/connectors, USB/LAN sync, cartridge checkpoints, and treasury USDC payments (Touch ID). Do not use for generic env var, API token, wallet, or SSH key questions, or for other vaults or .env files. Never print secret values in chat.