Payclaw

io.github.payclawPublished by GitHub account payclawv0.1.4Updated Oct 24, 2026

Virtual Visa cards for AI agents. JIT card issuance, human-approved, MCP-native.

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Payclaw (kya labs) lets an AI agent declare a verified identity to merchants and, with human approval, obtain a single-use virtual Visa card to check out.

What you can do
Declare the agent's identity to a merchant and receive a verification token plus next-step guidance, with an optional checkout patch for supporting merchants (Badge). Report whether the badge was presented and how the merchant responded, or that it was not presented. Declare a purchase intent and request a single-use virtual Visa card, then report the transaction outcome to close the audit trail (Spend). Optionally check back after a badge presentation to log merchant accept or deny results to a dashboard.
When to use it
Use it when an agent shops or checks out at online merchants that challenge automated traffic, or when you want agent purchases paid with an ephemeral card instead of exposing your real card details. The lighter badge-only package covers identity without payment.
Requirements
Runs locally over stdio via npx, so Node.js 20 or newer is needed. Badge works without an account; verified identity and card issuance need a PAYCLAW_API_KEY, with PAYCLAW_API_URL optionally overriding the default base URL. Card issuance requires human approval through MFA or a device flow. Network access is required for merchant and API calls.
Before you install
Spend issues real payment credentials: each card is single-use and locked to one merchant, but it still spends money and requires your explicit approval. The API key is a secret. The server records anonymous events, a local install ID, merchant and agent details, and for Spend a full transaction trail; a start-up ping can be disabled with KYA_PING. Review the provider's data practices before use.

Installation

In SourceWeft

  1. Open Payclaw in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

kya labs — Badge + Spend for AI Agents

Your agent isn't a bot. kya proves it — then lets it pay.

Your AI agent looks like a bot to every merchant on the internet. kya gives it two things:

Badge — Declares your agent as an authorized actor. The Universal Commerce Protocol "identity" token for a merchant handshake. Free. No card required.

Spend — Issues a single-use virtual Visa when your agent needs to pay. Human-approved. Self-destructs after use. Your real card never enters the chat.

If you're like 20% of Americans last year - you used an agent to shop. And you probably ran into a ton of login walls, workarounds, bumps?

So did we. So we created kya - the first MCP tool suite that works with the new Universal Commerce Protocol to easily handshake verified agents at supporting merchants (Shopify, Target, Walmart, Etsy... it's a lot). Badge for identity. Spend for payment.

🧪 Developer Sandbox is open. Real infrastructure, test money. Get sandbox access →

[npm version] [License: MIT]

[payclaw-mcp MCP server]

Quick Start

bash
npx @kyalabs/mcp-server

OR add to your MCP client config (Claude Desktop, Cursor, or any MCP client):

json
{  "mcpServers": {    "kyalabs": {      "command": "npx",      "args": ["@kyalabs/mcp-server"]    }  }}

That's it. Badge works immediately — no API key, no signup, no network calls on install.

The first time your agent calls kya_getAgentIdentity, it declares itself to the merchant and gets back a response with next_step guidance. One anonymous event is recorded. Your agent is now a declared, authorized actor.

Or install via ClawHub:

bash
clawhub install payclaw-io

Upgrade to verified mode + Spend

For cryptographic identity and virtual card issuance, add an API key:

json
"env": {  "KYA_API_KEY": "pk_live_your_key_here",  "KYA_API_URL": "https://www.kyalabs.io"}

Get your API key at kyalabs.io/signup. API keys don't expire.

Without an API key, Badge uses device auth when a merchant requires verified identity — your agent shows a code and URL, you approve on your phone. This only happens when a merchant asks for it. We never ask for it ourselves. Sign up + API key means 1. you dont have to use phone OAuth every time and 2. you can track your agentic shopping (custom avatars included)

Node version

kya MCP requires Node.js 20 or newer. Node 18 is end-of-life and unsupported.

If you see engine or compatibility errors: node -v — install Node 20+ from nodejs.org or nvm install 20

How Badge Works: Two Modes

Declared (default)

First time your agent goes to a merchant with Badge, Badge generates an anonymous install ID — a random UUID stored locally at ~/.kya/install_id. It has no connection to you, your device, or any personal information.

Your agent gets back a declaration and a next_step guiding it to report its badge presentation at the merchant.

This is the default mode. It's how Badge works out of the box, for every user, forever.

Verified (when merchant requires it)

When a merchant requires verified identity — their UCP manifest says required: true — your agent will ask you to approve a device flow. You visit a merchant-kya URL, enter the OAuth code from your agent, and prove you're a real person.

Badge issues a tokenized credential: an ES256-signed JWT, signed by kya's private key, verifiable locally by the merchant. Your agent is free to continue - no login, PII or anything needed.

Our Data Philosophy

WhenWhatWhy
On installNothingWe help agents shop. If they're not shopping, we don't need anything
On server startAnonymous ping — Badge version and MCP client name. No identifiers stored on your machineSo we know Badge is actively running. If this number ever diverges from active agents, it tells us something is broken in the pipeline — not something about you
On first shopping tripinstall_id (random UUID, stored locally at ~/.kya/install_id), merchant, agent_type, event_type, timestampMinimum viable signal to reduce agent friction at merchants
On verified identity+ hashed user token, intent scope (checkout, etc.)Only required where login is traditionally required (i.e. checkout) to prove there's a real person authorizing the agent's next step
On Spend (card issuance)+ full transaction trail: intent, amount, merchant, audit logCard network compliance, gated behind consent + MFA

The server start ping contains no persistent identifiers — a new random session ID is generated each time and never saved to disk. You can disable it entirely:

json
"env": { "KYA_PING": "false" }

The install_id is a file we wrote to your disk. You can delete it (rm ~/.kya/install_id) and get a new one.

Full data practices: kyalabs.io/trust

The Universal Commerce Protocol

Badge is a UCP (Universal Commerce Protocol) Credential Provider. Merchants who declare the kya identity extension signal to every UCP-compliant agent that authorized agents are preferred at their store.

When your agent encounters a UCP merchant with Badge installed, it presents a cryptographic badge automatically — no extra steps.

We believe the UCP is the future of commerce and are proud to support reduce friction for agents and users.

Without kya: Agent browses → bot detection fires → blocked. Even if it gets through, it can't check out without your real card number. You're stuck finishing manually.

With Badge: Agent declares itself as an authorized actor → merchants see a verified identity → agent gets through. No bypass. Just proof.

With Spend: Agent declares a purchase → you approve with a tap → kya issues a single-use virtual Visa locked to that merchant → agent checks out → card self-destructs. Your real card never enters the chat.

Your agent will recognize when it needs this. When it encounters a merchant that may challenge automated traffic, or when it's ready to check out, it tells you: "I need kya installed to complete this." You click Allow. Done.

Tools

See docs/tool-contract.md for the formal input/output contract.

ToolWhat It Does
kya_getAgentIdentityDeclare identity → get verification token + next_step guidance (Badge)
kya_reportBadgePresentedRecord that you presented your badge at a merchant
kya_reportBadgeOutcomeReport how the merchant responded (accepted, denied, inconclusive)
kya_reportBadgeNotPresentedReport that you did not present your badge (abandoned, merchant didn't ask)
kya_getCardDeclare purchase intent → get virtual Visa (Spend)
kya_reportPurchaseReport transaction outcome → close the audit trail

Every Badge tool call works immediately — no auth required. Events fire in both anonymous and verified modes.

Badge: Declare Identity

Agent → kya_getAgentIdentity({ merchantUrl })kya → browse_declared event fires automaticallykya → verification token + next_step + checkoutPatch (if merchant supports UCP)Agent → merges checkoutPatch into checkout payloadAgent → kya_reportBadgePresented({ merchantUrl, verification_token })Agent → kya_reportBadgeOutcome (accepted | denied | inconclusive)

Spend: Get a Card

Agent → kya_getCard (merchant, amount, description)User → approves via MFAkya → issues single-use virtual VisaAgent → uses card at checkoutAgent → kya_reportPurchase (closes audit trail)Card → self-destructs

One task. One approval. One card. Done.

Extended Auth (optional)

When enabled, kya checks back with your agent 7 seconds after each badge presentation to confirm whether the merchant accepted or denied. Results are logged to your dashboard so you can see when and which merchants are rejecting your agent.

json
"env": {  "KYA_EXTENDED_AUTH": "true"}

How Authorization Scales

ActionWhat Happens
BrowseBadge declaration — identity token issued
SearchBadge declaration — identity token issued
CheckoutBadge + Spend — MFA approval → single-use Visa issued

Browsing requires declaration. Spending money requires declaration + stated intent + explicit human approval + an ephemeral card that self-destructs after one use.

Why kya labs

Give Agent Your CardCrypto Walletkya
Agent identity declaredNoNoEvery session
Human approval per purchaseNoNoEvery purchase
Card credential lifespanPermanentPermanentSingle use
Works at existing merchantsYesNoYes — Visa rails
Your real card exposedYesN/ANever

Badge Only?

If you only need identity (no payment), use the lighter package:

bash
npx @kyalabs/badge

What's New (v2.3)

CapabilityDescription
assurance_levelEvery trip now carries a trust score (starter → elite) sourced from token introspection. Visible in your dashboard and included in all trip outcome events.
Merchant signal awarenesskya_getAgentIdentity now detects whether a merchant has active kya signal infrastructure (window.__kya_commerce, meta tags, llms.txt). Returned as merchant_signals in the identity result.
Anonymous-firstBadge works on install. No auth, no signup, no network on install. First kya_getAgentIdentity call fires browse_declared automatically.
Enrichment branchingAnonymous events fire without auth. Verified events include full user context. No silent gates.
next_step fieldEvery identity response includes guidance for the agent's next action. Spend-aware when virtual cards are available.

KYA — Know Your Agent

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

Links

Agents are not bots. kya labs proves it. Your real card never enters the chat.

Source: README.md at commit 97c8b2e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.4LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts