@payclaw/badge
Advanced tools
Prove your agent is an authorized actor, not a bot. MCP-native identity declaration for agent commerce.
Agents are not bots. Prove it.
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. Merchants let it through.
Add to your MCP client config:
{
"mcpServers": {
"payclaw-badge": {
"command": "npx",
"args": ["-y", "@payclaw/badge"],
"env": {
"PAYCLAW_API_KEY": "pk_your_key_here",
"PAYCLAW_API_URL": "https://payclaw.io"
}
}
}
}
Get your API key at payclaw.io. Five-minute setup.
Your agent is smart. It can browse, compare prices, build carts, find deals. But to every merchant on the internet, it looks identical to a scraper.
Merchants don't ask "is this agent helpful?" They ask "is this a bot?" And they block first, ask never.
Without Badge: Your agent hits a merchant → bot detection fires → blocked. Task fails. Your user is disappointed. The merchant lost a sale and doesn't know it.
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.
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.
Every time your agent calls payclaw_getAgentIdentity, it receives a verification token that declares:
[BROWSE] in V1)agent_identity@payclaw.io for merchant verificationThe agent presents this disclosure to merchants. Merchants see a verified identity, not anonymous traffic.
1. Your agent calls payclaw_getAgentIdentity before shopping
2. PayClaw issues an HMAC-SHA256 verification token
3. Agent presents the disclosure to merchants
4. PayClaw checks back: "Were you accepted or denied?"
5. Outcome recorded — your Verified Trips count goes up
No card is issued. No money moves. Badge is the identity layer — the skeleton key that lets authorized agents through while bot defenses stay intact.
| Tool | Description |
|---|---|
payclaw_getAgentIdentity | Declare identity, get verification token |
payclaw_reportBadgePresented | Signal that you presented your Badge to a merchant |
Badge is the base layer. For virtual Visa cards, use @payclaw/mcp-server — which includes Badge automatically.
clawhub install payclaw-io
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.
Agents are not bots. PayClaw proves it.
FAQs
Prove your agent is an authorized actor, not a bot. MCP-native identity declaration for agent commerce.
The npm package @payclaw/badge receives a total of 55 weekly downloads. As such, @payclaw/badge popularity was classified as not popular.
We found that @payclaw/badge demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
A new federal program will let vetted U.S. cybersecurity firms help investigate and disrupt foreign cybercrime groups under government direction.
Research
/Security News
The campaign amassed more than 75,000 installs by targeting Russian-speaking users seeking access to blocked services.
Company News
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.