← Back to Skills Marketplace
Payclaw Io Pub
by
PayClaw, Inc.
· GitHub ↗
· v0.7.1
506
Downloads
0
Stars
0
Active Installs
12
Versions
Install in OpenClaw
/install payclaw-io
Description
Agents are not bots. PayClaw proves it — then lets them pay. UCP Credential Provider: Badge declares your agent as an authorized actor at any UCP-compliant m...
Usage Guidance
This skill appears to do what it says: it runs an MCP server (via npx) that provides identity badges and single-use cards. Before installing: (1) Verify the npm package (@payclaw/mcp-server) and its publisher (review package source, version history, and GitHub repo linked in SKILL.md); (2) Understand where the 'Consent Key' will be stored on your agent and how to revoke or delete it; (3) Be aware that npx will download and execute remote code at runtime — if you need stronger guarantees, request a vetted binary or vendor-signed release rather than running npx on-the-fly; (4) Test in a sandbox environment and use the sandbox/test money option before using with real payments.
Capability Analysis
Type: OpenClaw Skill
Name: payclaw-io
Version: 0.7.1
The payclaw-io skill provides a legitimate framework for AI agent identity (Badge) and single-use virtual payments (Spend) via the PayClaw platform. It utilizes a standard MCP server configuration executed via npx (@payclaw/mcp-server) and communicates with a dedicated API (api.payclaw.io). The instructions and tool definitions are consistent with the stated purpose of facilitating authorized commerce, including built-in human-in-the-loop approval for transactions and no evidence of data exfiltration or malicious prompt injection.
Capability Assessment
Purpose & Capability
Name/description match what the instructions require: the skill asks for npx and instructs the agent to run an @payclaw/mcp-server process to provide Badge and Spend functionality. Requiring npx and a Node 20 runtime is proportionate for an npm-based MCP server.
Instruction Scope
SKILL.md only instructs adding the MCP server to the agent config and calling well-scoped RPCs (payclaw_getAgentIdentity, payclaw_getCard, payclaw_reportPurchase). It does not ask the agent to read unrelated files or to exfiltrate data to unexpected endpoints beyond the declared PAYCLAW_API_URL.
Install Mechanism
No install spec is present, but the skill expects runtime use of 'npx -y @payclaw/mcp-server'. That downloads and executes package code from npm at runtime (moderate risk). This is expected for an npm-based MCP server but you should verify the npm package and publisher before trusting it.
Credentials
The skill declares no required secret environment variables. The metadata binds PAYCLAW_API_URL to the official domain which matches the service. The only implicit credential behavior is the device auth/Consent Key stored on first use; this is consistent with the described device auth flow but you should confirm where that key is persisted and how to revoke it.
Persistence & Privilege
always:false (normal). The skill will persist a Consent Key on first use (SKILL.md: 'Consent Key is stored automatically'); persisting that credential in agent storage is expected but worth reviewing — confirm storage location, lifetime, and revocation. Autonomous invocation is allowed (normal default).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install payclaw-io - After installation, invoke the skill by name or use
/payclaw-io - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.7.1
- Added a requirement for Node.js 20+ in the setup instructions (Node 18 is now end-of-life).
- Provided guidance for resolving Node.js engine errors, including upgrade instructions.
v0.7.0
V1.2 UCP: no API key required (device auth), UCP Credential Provider, updated tool descriptions, /merchants link
v0.6.0
Formatted CLI output, merchant param, brand v2 alignment, new example with declaration flow
v0.5.0
Brand v2: authorized actor framing, skeleton key, KYA. MCP sampling (DQ-54). Badge + Spend unified. npm 0.3.0.
v1.2.0
Badge + Spend positioning, identity-first flow, account protection framing
v0.4.0
Sandbox launch: test card setup, pk_test_ keys, sandbox pricing, updated tool schema
v0.3.0
Sandbox now live. Updated install instructions, real MCP tool names (payclaw_getCard, payclaw_reportPurchase), Stripe test card, links to payclaw.io/dev and payclaw.io/trust.
v2.0.0
V1 launch: virtual cards for AI agents — MCP server config, intent-based auth, post-purchase audit, mandatory MFA
v1.1.0
V1: virtual cards for AI agents — MCP config, intent-based auth, post-purchase audit
v0.2.0
Full skill with MCP config, setup guide, security docs, and usage examples
v0.1.0
Initial release — virtual cards for AI agents
v1.0.0
Initial release of PayClaw:
- Introduces virtual Visa card issuance for AI agents, enabling autonomous online purchases without exposing your real card.
- User funds a limited balance via Stripe; agents receive capped virtual cards issued by Lithic, accepted anywhere Visa works.
- Instant card freezing in case an agent is compromised.
- Spend limits and merchant restrictions configurable per task.
- Early access and integration details available for developers.
Metadata
Frequently Asked Questions
What is Payclaw Io Pub?
Agents are not bots. PayClaw proves it — then lets them pay. UCP Credential Provider: Badge declares your agent as an authorized actor at any UCP-compliant m... It is an AI Agent Skill for Claude Code / OpenClaw, with 506 downloads so far.
How do I install Payclaw Io Pub?
Run "/install payclaw-io" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Payclaw Io Pub free?
Yes, Payclaw Io Pub is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Payclaw Io Pub support?
Payclaw Io Pub is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Payclaw Io Pub?
It is built and maintained by PayClaw, Inc. (@payclawinc); the current version is v0.7.1.
More Skills