How Spendkit works
Spendkit is a control panel for AI Agents that may spend from your wallet. It helps you set a rule for each Agent and see what each one spent.
Your USDG stays in the Payment Wallet you control until that wallet sends an approved payment.
Four things you will see
A named identity for an assistant that may ask to make payments. Its name and payment history help you tell it apart from your other Agents.
The wallet that holds the test USDG and pays transaction gas. It can be linked to several Agents.
One Agent's onchain rules: whether it is active, how much it may pay at once or in a UTC day, and any recipient restrictions.
The place to review requests and outcomes, including confirmed, denied, pending, and failed records.
What happens when an Agent wants to pay?
“May I pay this amount to this recipient?”
Spendkit checks the Agent's Policy and returns an answer for that exact request. If the answer is no, the flow stops.
The linked wallet sends a transaction. The Router checks the Policy again before USDG reaches the recipient.
You can see what the request became. A pending request and a confirmed payment are different states.
What the limits cover
The Router enforces an Agent's Policy for payments made through Spendkit. The local Runtime holds the Payment Wallet key for signing, so that Runtime and its key store must remain trusted: someone with that key can make a direct transfer outside the Router. Read the security boundary.