Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Declare your agent's identity before merchants ban your user's account. One tool. Five minutes. No card required.
Declare your agent's identity before merchants ban your user's account. One tool. Five minutes. No card required.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Agents are not bots. Prove it before you shop. Your AI agent looks like a bot to every merchant on the internet. Badge gives it a way to declare what it is: an authorized actor, shopping on behalf of a real human, with explicit consent. One MCP tool call. Your agent declares itself. UCP-compliant merchants let it through.
Add to your MCP client config: { "mcpServers": { "payclaw-badge": { "command": "npx", "args": ["-y", "@payclaw/badge"], "env": { "PAYCLAW_API_KEY": "your_key_from_payclaw.io", "PAYCLAW_API_URL": "https://api.payclaw.io" } } } } Credentials: PAYCLAW_API_KEY required. Get your key at payclaw.io/dashboard/badge. For zero-friction install (no key, device auth), use payclaw-io instead. Requires Node.js 20+. Node 18 is end-of-life. If you see engine errors: node -v β install from nodejs.org or nvm install 20.
Badge is a UCP (Universal Commerce Protocol) Credential Provider. Merchants who declare io.payclaw.common.identity in their UCP manifest signal that declared agents are preferred at their store. For Merchants β add PayClaw to your UCP manifest Protocol spec β MIT
ToolDescriptionpayclaw_getAgentIdentityDeclare yourself as an authorized actor before acting at any merchant. Without this, UCP-compliant merchants may prefer or require a declared agent. Returns a UCP-compatible credential.payclaw_reportBadgePresentedSignal Badge presentation to a merchant
Agent calls payclaw_getAgentIdentity({ merchant: "starbucks.com" }) PayClaw issues a UCP-compatible verification token Agent presents disclosure to merchants PayClaw checks outcome (accepted/denied/inconclusive) Verified Trips count goes up No card issued. No money moves. Badge is identity only. Free forever.
Credentials: PAYCLAW_API_KEY required. Get your key at payclaw.io/dashboard/badge. Data: Identity declarations and trip outcomes are reported to PayClaw for verification and Verified Trips. See payclaw.io/trust. Source: github.com/payclaw/badge-server (MIT), npm: @payclaw/badge. For payment too, use payclaw-io β Badge + Spend.
payclaw.io For Merchants Trust & Verification npm: @payclaw/badge Protocol spec: ucp-agent-badge
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.