Now in early access

The payment platform built for AI agents.

Give your AI agent a virtual card. It signs, pays, and manages spending — no human in the loop. Every transaction authorized by a signed PolicyWindow you control.

Invite-only early access Virtual Visa, USDT-funded MCP tool server + REST API
What it does

Payment infrastructure built for autonomous agents.

AI agent integration

One command to install: curl -fsSL https://klw.kleepay.ai/install.sh | sh. MCP native — works with Claude, OpenClaw, any MCP-compatible agent. Skill file at klw.kleepay.ai/skill.md — agents learn KleePay in seconds.

Cryptographic PolicyWindow signing

Every transaction requires an Ed25519-signed policy: amount ceiling, merchant domain, MCC category, time window. Agents can only spend what you authorize — not a cent more.

Virtual Visa cards

Instant virtual cards funded by USDT. Freeze and unfreeze per transaction. Each agent gets its own card — or share one with tight policy constraints. Works at 99% of global merchants.

How it works

Simple for you. Invisible to the agent.

01

Complete KYC

Verify your identity once. No credit check, no bank account. The process takes a few minutes and unlocks your account for card issuance and USDT deposits.

02

Load USDT, issue cards

Deposit USDT to fund your balance. Create virtual Visa cards and allocate spending to each agent workflow. Set per-card limits — amount, merchant whitelist, MCC category.

03

Agent executes, Local Wallet authorizes

The agent calls kleepay_pay via MCP. The local wallet daemon validates the policy, signs the transaction, and releases the card for exactly one purchase. Window closes automatically.

04

Full audit trail

Every authorization is logged with the signed policy that permitted it. Every settlement. Every freeze. When something goes wrong, you know exactly why it was allowed.

Security model

Default deny. Always.

Every card rejects every transaction by default. A payment goes through only when a signed, in-scope PolicyWindow permits it — and not a cent more.

KleePay
Ed25519 signatures on every transactionRFC 8037

The Local Wallet daemon holds your keys locally — they never leave your machine. Each PolicyWindow is signed before any charge is attempted. No signature, no payment.

Time-bound authorization windowsTTL enforced

A PolicyWindow expires in minutes. Compromised credentials go stale before they can be reused. Cards are frozen by default and only open for the duration of one transaction.

Per-transaction freeze / unfreezeDefault frozen

The Local Wallet unfreezes the card, the transaction goes through, the card refreezes. Even if a PAN is captured in transit, it cannot be reused outside the active window.

Merchant + MCC constraints

Policies bind to a specific merchant domain and MCC category. An agent authorized for vercel.com cannot spend at aws.amazon.com, even if both are SaaS.

For developers

Connect your agent in minutes.

MCP or REST — whichever fits your stack. The Local Wallet runs locally and handles all signing. Read the full agent integration guide.

MCPTool server — works with Claude, GPT, any MCP client
RESTDirect API — webhooks, idempotency, full audit log
A2AGoogle A2A compatible — coming soon
On the roadmap

ACP SharedPaymentToken · Visa TAP · Mastercard Agent Pay · x402 USDC — native protocol support added incrementally as the ecosystem matures.

klw.toml
# ~/.kleepay/klw.toml

[card.infra_agent]
card_id      = "card_7f3a9c2d"
max_amount   = 500.00    # USD per window
daily_limit  = 2000.00
ttl_minutes  = 15

[card.infra_agent.allowed]
merchants = ["vercel.com", "aws.amazon.com",
             "github.com", "planetscale.com"]
mcc       = ["5734", "7372"]  # software only
$ klw start
klw ready /tmp/kleepay.sock
MCP server port 3333
card_7f3a9c2d $2000.00 daily frozen
KleePay

Ready to give your agent a wallet?

Invite-only early access. No subscription — you pay only for what the agent loads.

No spam. We'll email when your access is ready.