@payclaw/badge 0.4.0 → 0.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +26 -17
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -17,15 +17,23 @@ Add to your MCP client config:
|
|
|
17
17
|
"command": "npx",
|
|
18
18
|
"args": ["-y", "@payclaw/badge"],
|
|
19
19
|
"env": {
|
|
20
|
-
"
|
|
21
|
-
"PAYCLAW_API_URL": "https://payclaw.io"
|
|
20
|
+
"PAYCLAW_API_URL": "https://api.payclaw.io"
|
|
22
21
|
}
|
|
23
22
|
}
|
|
24
23
|
}
|
|
25
24
|
}
|
|
26
25
|
```
|
|
27
26
|
|
|
28
|
-
|
|
27
|
+
No API key required. On first use, your agent will show a code and URL — approve on your phone in one tap, and your Consent Key is stored. Optional: set `PAYCLAW_API_KEY` for existing accounts (backward compatible).
|
|
28
|
+
|
|
29
|
+
## UCP Identity Linking
|
|
30
|
+
|
|
31
|
+
Badge is a [UCP (Universal Commerce Protocol)](https://ucp.dev) Credential Provider. Merchants who declare the PayClaw identity extension signal to every UCP-compliant agent that authorized agents are preferred at their store.
|
|
32
|
+
|
|
33
|
+
When your agent encounters a UCP merchant with PayClaw installed, it presents a cryptographic badge automatically — no extra steps.
|
|
34
|
+
|
|
35
|
+
- Extension spec + schema: [github.com/payclaw/ucp-agent-badge](https://github.com/payclaw/ucp-agent-badge)
|
|
36
|
+
- Merchant documentation: [payclaw.io/merchants](https://payclaw.io/merchants)
|
|
29
37
|
|
|
30
38
|
## Why Your Agent Needs This
|
|
31
39
|
|
|
@@ -37,15 +45,13 @@ Merchants don't ask "is this agent helpful?" They ask "is this a bot?" And they
|
|
|
37
45
|
|
|
38
46
|
**With Badge:** Your agent calls `payclaw_getAgentIdentity` → receives a verification token → presents it to the merchant. The merchant sees: authorized actor, verified human behind it, declared intent. Your agent gets through. Task succeeds.
|
|
39
47
|
|
|
40
|
-
Your agent will recognize when it needs this. When it encounters a merchant that may challenge automated traffic, it tells you: "I need PayClaw Badge installed to complete this safely." You click Allow. Done.
|
|
41
|
-
|
|
42
48
|
## What Badge Declares
|
|
43
49
|
|
|
44
|
-
Every time your agent calls `payclaw_getAgentIdentity`, it receives a
|
|
50
|
+
Every time your agent calls `payclaw_getAgentIdentity`, it receives a UCP-compatible credential that declares:
|
|
45
51
|
|
|
46
52
|
- **Agent type:** Authorized actor (not a bot, not a scraper)
|
|
47
|
-
- **Principal:** Verified human behind this session
|
|
48
|
-
- **
|
|
53
|
+
- **Principal:** Verified human behind this session (Google or Apple SSO)
|
|
54
|
+
- **Assurance level:** `starter` / `regular` / `veteran` / `elite` based on verified trip history
|
|
49
55
|
- **Contact:** `agent_identity@payclaw.io` for merchant verification
|
|
50
56
|
|
|
51
57
|
The agent presents this disclosure to merchants. Merchants see a verified identity, not anonymous traffic.
|
|
@@ -53,20 +59,20 @@ The agent presents this disclosure to merchants. Merchants see a verified identi
|
|
|
53
59
|
## How It Works
|
|
54
60
|
|
|
55
61
|
```
|
|
56
|
-
1. Your agent calls payclaw_getAgentIdentity
|
|
57
|
-
2.
|
|
58
|
-
3.
|
|
59
|
-
4.
|
|
60
|
-
5.
|
|
62
|
+
1. Your agent calls payclaw_getAgentIdentity
|
|
63
|
+
2. No key? Device auth flow triggers — code + URL appear in terminal
|
|
64
|
+
3. You approve on your phone (Google or Apple, one tap)
|
|
65
|
+
4. Consent Key stored — agent is authorized
|
|
66
|
+
5. Every subsequent call uses the stored key automatically
|
|
61
67
|
```
|
|
62
68
|
|
|
63
|
-
No card is issued. No money moves. Badge is the identity layer — the
|
|
69
|
+
No card is issued. No money moves. Badge is the identity layer — the credential that lets authorized agents through while bot defenses stay intact.
|
|
64
70
|
|
|
65
71
|
## Tools
|
|
66
72
|
|
|
67
73
|
| Tool | Description |
|
|
68
74
|
|------|-------------|
|
|
69
|
-
| `payclaw_getAgentIdentity` | Declare identity, get verification token |
|
|
75
|
+
| `payclaw_getAgentIdentity` | Declare identity, get UCP-compatible verification token |
|
|
70
76
|
| `payclaw_reportBadgePresented` | Signal that you presented your Badge to a merchant |
|
|
71
77
|
|
|
72
78
|
## Need Payment Too?
|
|
@@ -74,7 +80,7 @@ No card is issued. No money moves. Badge is the identity layer — the skeleton
|
|
|
74
80
|
Badge is the base layer. For virtual Visa cards, use [@payclaw/mcp-server](https://www.npmjs.com/package/@payclaw/mcp-server) — which includes Badge automatically.
|
|
75
81
|
|
|
76
82
|
```bash
|
|
77
|
-
|
|
83
|
+
npx -y @payclaw/mcp-server
|
|
78
84
|
```
|
|
79
85
|
|
|
80
86
|
## KYA — Know Your Agent
|
|
@@ -82,14 +88,17 @@ clawhub install payclaw-io
|
|
|
82
88
|
PayClaw is KYA infrastructure. Every declaration creates a verified record of agentic commerce behavior — building the trust signal that merchants need to tell authorized agents from anonymous bots.
|
|
83
89
|
|
|
84
90
|
- [Trust & Verification](https://payclaw.io/trust) — The full trust architecture
|
|
85
|
-
- [
|
|
91
|
+
- [For Merchants](https://payclaw.io/merchants) — How merchant UCP integration works
|
|
92
|
+
- [UCP Extension Spec](https://github.com/payclaw/ucp-agent-badge) — `io.payclaw.common.identity` (MIT)
|
|
86
93
|
|
|
87
94
|
## Links
|
|
88
95
|
|
|
89
96
|
- **Website:** [payclaw.io](https://payclaw.io)
|
|
90
97
|
- **npm:** [@payclaw/badge](https://www.npmjs.com/package/@payclaw/badge)
|
|
98
|
+
- **UCP Extension:** [github.com/payclaw/ucp-agent-badge](https://github.com/payclaw/ucp-agent-badge)
|
|
91
99
|
- **ClawHub:** [payclaw-badge](https://clawhub.com/skills/payclaw-badge)
|
|
92
100
|
- **Trust:** [payclaw.io/trust](https://payclaw.io/trust)
|
|
101
|
+
- **Merchants:** [payclaw.io/merchants](https://payclaw.io/merchants)
|
|
93
102
|
- **Contact:** agent_identity@payclaw.io
|
|
94
103
|
|
|
95
104
|
---
|
package/package.json
CHANGED