Badge by PayClaw

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.

Setup

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.

UCP Identity Linking

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

Tools

How It Works

1. Agent calls payclaw_getAgentIdentity({ merchant: "starbucks.com" })
2. PayClaw issues a UCP-compatible verification token
3. Agent presents disclosure to merchants
4. PayClaw checks outcome (accepted/denied/inconclusive)
5. Verified Trips count goes up

No card issued. No money moves. Badge is identity only. Free forever.

Security & Privacy

• 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.

Links

• payclaw.io
• For Merchants
• Trust & Verification
• npm: @payclaw/badge
• Protocol spec: ucp-agent-badge