io.github.payclaw/badge
Agents are not bots. Prove it. MCP-native identity declaration for authorized agents.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@payclaw/badgeclaude mcp add badge -e 'PAYCLAW_API_KEY=<your payclaw_api_key>' -e 'PAYCLAW_API_URL=<PAYCLAW_API_URL>' -- npx -y @payclaw/badge@0.4.0
{
"mcpServers": {
"badge": {
"command": "npx",
"args": [
"-y",
"@payclaw/badge@0.4.0"
],
"env": {
"PAYCLAW_API_KEY": "<your payclaw_api_key>",
"PAYCLAW_API_URL": "<PAYCLAW_API_URL>"
}
}
}
}
Variables d'environnement
PAYCLAW_API_KEYobligatoire secret Your PayClaw API key (get one at payclaw.io)PAYCLAW_API_URLPayClaw API URL (default: https://payclaw.io)
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Badge by kya labs
Persistent identity for AI agents across merchant sites. Badge gives agents a credential they carry on every request — merchants verify it, trust accumulates across visits, and agents that build history earn better treatment over time.
Framework-agnostic. Transport-agnostic. Zero runtime dependencies.
Badge SDK
The SDK is the primary integration surface. Three methods cover the full lifecycle:
import { Badge } from "@kyalabs/badge-sdk";
const badge = await Badge.init();
const runId = badge.startRun();
await badge.declareVisit({
merchant: "store.example.com",
runId,
url: "https://store.example.com/cart",
});
await badge.reportOutcome({
merchant: "store.example.com",
runId,
outcome: "not_denied",
});
No signup. No API key. Badge.init() issues a guest pass on first run and caches it to disk. Identity survives process restarts.
npm install @kyalabs/badge-sdk
What the SDK covers
- Identity model — three-tier ladder: guest pass (
gp_v1_*) → badge token (kya_*) → authenticated identity - Lifecycle tracking — declare visits, report outcomes, correlate with run IDs
- Offline resilience — never throws on network failure, deterministic fallback on every call
- UCP integration —
io.kyalabs.common.identityCredential Provider, published schemas, ES256-signed JWTs - Scoring — outcomes feed kyaScore (500–850), portable across merchants
Badge MCP Server
For MCP client users (Claude Desktop, Cursor, Windsurf), Badge also ships as an MCP tool server. The MCP server wraps the SDK — same identity model, same tokens, same scoring.
npx @kyalabs/badge
The SDK is the canonical integration path for platform builders and agent frameworks. The MCP server is a convenience wrapper for end users working within MCP clients.
Links
- Website: kyalabs.io
- Data practices: kyalabs.io/trust
- UCP extension spec: github.com/kyalabs/ucp-agent-badge
- Contact: agent_identity@kyalabs.io
License
MIT
Questions fréquentes
Qu'est-ce que io.github.payclaw/badge ?
Agents are not bots. Prove it. MCP-native identity declaration for authorized agents.
Comment installer io.github.payclaw/badge ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add badge -e 'PAYCLAW_API_KEY=<your payclaw_api_key>' -e 'PAYCLAW_API_URL=<PAYCLAW_API_URL>' -- npx -y @payclaw/badge@0.4.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.payclaw/badge ?
Oui. Il attend PAYCLAW_API_KEY, à renseigner dans sa configuration.
io.github.payclaw/badge est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.payclaw/badge ?
Il est publié par payclaw. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.