Your wallet remains the source
No deposit into Spendkit is needed. The bound payment wallet submits the transaction and pays gas; the Spendkit server does not receive its private key.
03 / Agent payments
Spendkit lets you give each AI agent a spending policy while keeping funds in a payment wallet you control. Set daily and per-payment limits; payments routed through Spendkit are checked against those rules on-chain.
Current demo: Paxos Test USDG on Arbitrum Sepolia. Spendkit does not hold funds or broadcast payments.
Give autonomy a boundary.
Why Spendkit
A wallet can hold funds, but it does not describe which agent may spend them or how much. Spendkit connects wallets, agents, and policies.
No deposit into Spendkit is needed. The bound payment wallet submits the transaction and pays gas; the Spendkit server does not receive its private key.
Give each agent its own daily and per-payment limits. Several agents can share a wallet without sharing a single spending policy.
The on-chain Router checks the active policy and exact authorization before a Spendkit payment can transfer funds.
The payment path
Give a compatible agent a way to request payment while keeping the decision and final enforcement separate.
Verify a wallet you control, create an agent, and set its daily and per-payment policy.
A compatible runtime connects with OAuth and MCP tools to read its policy and preview a proposed payment.
An allowed payment receives an exact, short-lived authorization. The wallet sends it through the Router, which checks the policy again.
The important details
Spendkit is designed for payments routed through its authorization and Router flow. Keeping an agent's wallet key secure still matters.