MasterCard Agent Pay Compatible compatible cards, wallets & payments. Financial management for Agents and OpenClaw bots.
Security Analysis
high confidenceThe skill's requests and runtime instructions are consistent with a payment/checkout integration and only require the single CreditClaw API key it declares.
Name/description describe a payments platform and the skill only requests CREDITCLAW_API_KEY and documents API calls to https://creditclaw.com/api/v1 — these requirements match the stated purpose (creating checkouts, wallet signing, encrypted-card flow, management).
SKILL.md and companion docs instruct the agent to call CreditClaw API endpoints, poll status, request single-use decryption keys, and perform ephemeral decryption in memory. They do not instruct reading unrelated files or exfiltrating secrets to other domains; the docs explicitly warn not to send the API key to any domain except creditclaw.com/api/*.
This is an instruction-only skill with no install spec and no code files to execute. No packages, downloads, or extract steps are required — minimal surface area for code-install risk.
Only a single environment variable (CREDITCLAW_API_KEY) is declared and used. That is appropriate and proportional for a service that performs authenticated payment operations. No unrelated credentials or config paths are requested.
The skill is not marked always:true and does not request system-wide configuration or credentials belonging to other skills. It does instruct ephemeral handling of decrypted card data (must be kept only in memory), which is appropriate for its function.
Guidance
This skill appears coherent for enabling agent payments. Before installing: (1) Only provide a CreditClaw API key you control and understand grants spending capability; treat it as a secret. (2) Ensure the agent runtime can keep decrypted card data strictly ephemeral (in-memory) and that logs/telemetry will not capture card fields or the API key. (3) Confirm your owner-approved spending limits, approval_mode, and blocked categories in spending.md to avoid unexpected charges. (4) If you do not want autonomous spending, disable or tightly scope agent autonomy (or keep approval_mode set to ask_for_everything). If you want more assurance, verify the service at https://creditclaw.com and confirm its ownership and privacy policies before handing over real payment credentials.
Latest Release
v2.3.4
agent-pay 2.3.4 (2026-03-12) - Expanded documentation for MasterCard Agent Pay compatibility, supported cards, wallets, and agent/bot-focused financial management. - Added detailed security section, including strict API key handling, server-enforced spend controls, and advanced safety/visibility features for owners. - Introduced multi-rail payments: Owner Card (live), Stripe x402 wallet (private beta), and upcoming Crossmint wallet. - Outlined new files and API endpoints for bot registration, spending rules, wallet operations, checkouts, and balance polling. - Updated quick-start guide and end-to-end flow for registering bots and onboarding owners securely.
More by @codejika
CreditClaw Amazon | Order & Checkout at Amazon.com securely
4 stars
ShopClaw | Give your claw shopping tasks with strict controls
4 stars
CreditClaw | Give your agent a wallet or credit card
2 stars
CashClaw | Give your agent a wallet or credit card
1 stars
Perplexity Computer Payments | Make payments with Perplexity Computer
0 stars
Authorize.net Agentic Payments - Add agentic cards and wallets to your stack
0 stars
Published by @codejika on ClawHub