Software that spends.
Boundaries that hold.
Assistants and automations are starting to buy things: API credits, infrastructure, tools. KleePay is how they do it without holding your card, your keys, or your trust.
You write the policy
A budget, an allowlist, a per-transaction cap, an expiry. Plain rules, set once, changed anytime.
Software requests to spend
Each purchase needs a fresh authorization scoped to one merchant, one amount, one window.
KleePay enforces and records
Inside the rules, money moves. Outside them, it doesn’t. Either way you get the receipt.
Trust the boundary,
not the bot.
You never have to trust that software will behave. The card cannot exceed its budget, reach a merchant off the list, or spend after its window closes. Good behavior is structural.
Topping up credits
An assistant notices API credits running low and buys more, inside a $200 monthly budget.
allow: api.anthropic.com · $200/moExpenses on rails
Recurring vendor invoices settle themselves. Anything unusual routes to a human for approval.
recur: vendors · approve_over $500Workflows that pay
A pipeline spins up compute, pays for exactly what it used, and shuts down. No standing card on file.
authorize: $25 max · expires 15 min