Launching today
spendctl
Budgets, approvals and receipts for AI agents that pay
1 follower
Budgets, approvals and receipts for AI agents that pay
1 follower
AI agents can now pay per request (x402, Stripe MPP). spendctl decides whether they may: per-agent budgets, allowlists, human approvals and a receipt ledger, enforced in a sidecar you run, in front of the wallets you already have.
Free Options
Launch Team
Dropbox SignSimple, secure eSignatures for the way your team works.
Promoted
Hey Product Hunt, I'm the maker of spendctl.
I kept seeing the same pattern: agents that can pay for APIs on their own, guarded by a line in the prompt ("don't spend more than $5"). Prompts aren't spending controls, and the SDK guardrails live inside the same process as the agent.
spendctl moves the decision out: the agent asks, a sidecar with your policy answers. Over budget, a human approves in the CLI or Slack. Every payment lands in a ledger you can export for expenses. Signing happens in the sidecar you run, against a wallet you own (Coinbase CDP by default). We never hold keys or funds.
The Free tier is $0 with no card: 2 agents, every enforcement feature, a local sandbox. Pro ($29, founding $19) and Team ($249, founding $149) add shared policies, Slack approvals, exports and SSO on the hosted control plane, which is in development. Founding members lock the price for 12 months and get a full refund if GA slips.
Try it without keys or an account: npx spendctl init && npx spendctl mock && npx spendctl start. I'd love to hear which rule you wish it had.