An agent that spends —
inside hard limits.
Vesper proposes a payment, your control plane authorizes it against policy, and Circle settles it in USDC. Every step is logged. When Vesper tries to break a guard rail, it gets denied — and you can prove it.
Most agents can ask to spend. Vesper has to earn it.
Vesper isn't a wallet with an LLM bolted on. It's an agent that runs every proposed payment through the same authorization engine that governs your whole account — so autonomy never outruns accountability.
Proposes, never assumes
Vesper decides what it wants to buy and why, then submits a structured spend request. It cannot move money on its own.
Gated by your guard rails
Daily caps, per-transaction limits, blocked categories, and approval thresholds apply to Vesper exactly as they apply to any agent.
Settles in USDC
On approval, Vesper settles over Circle rails and reports the on-chain transaction back into the conversation. Testnet today.
Propose → authorize → settle.
Propose
Vesper submits an intent — amount, merchant, category, reason — through the authorize API.
Authorize
The policy engine evaluates identity, budget, and guard rails, then writes an append-only audit record.
Settle
On approve, Circle moves USDC and the transaction hash is pinned to the decision.
Watch an agent spend —
and get denied when it shouldn’t.
Vesper runs on testnet today. No real funds, no custody — just proof the controls work.