Consumer agent controls
Spend controls for personal assistants
Each user sets which merchants their assistant can use, how much, and when to ask.
Row L, two seats for Friday. That is $129, over the $100 you asked me to check with you on.
Ticketmaster
events · 2 tickets
one-time link · Telegram, WhatsApp, email, or your webhook
Cleared without asking
Blue Bottle Coffee
food · 8:02am
Target
shopping · yesterday
The dials you can hand your users
Each of these is set per user and checked at the payment. Expose as many as suit your product, from a single monthly cap to the full set.
Spend limits, per purchase and rolling
A ceiling on any single purchase, plus daily, weekly, and monthly budgets. A runaway loop or a misread instruction hits the cap, not the account balance.
Merchant and category rules
The user decides where the assistant can spend. Groceries and rides can be routine while gift cards, transfers, and unknown merchants stay off the table entirely.
Approval thresholds, and where the question lands
The user sets the amount that needs their approval. Above it, a signed one-time approve-or-decline link goes to Telegram, WhatsApp, Slack, email, or your own webhook, landing in a thread they already have open.
Guardrails the assistant can't talk its way past
Velocity limits, repeat-charge detection, and hard stops sit under the user-facing dials. They're enforced in the payment path, so a prompt injection that reaches the model still stops at the payment.
Demo
The assistant spends up to the ceiling its user set
Under $100 the purchase clears on its own. Above it, the assistant stops and a one-tap approval lands in the user's chat before anything is charged.
Rails
The user's rules, on the card they already carry
Controls aren't tied to one rail. In the connected-card pilot, your user links a card they already carry and the assistant spends under their rules, with the approvals and the record unchanged. The pilot is limited. Ask us.
Ask about the card pilotIn pilot
Connected cards. Conto does not store the card number and does not hand it to the agent.
On any rail
The rules, the approvals, and the record don't change with the rail.
Conto products behind assistant spend controls
Human review
Approvals
Send payments that need approval to a reviewer before money moves.
Explore productRuntime controls
Policy Engine
As the agent owner or budget holder, decide how much it can spend, who it can pay, and when it must ask. Conto checks your policy before execution.
Explore productFinancial visibility
Audit and Reconciliation
Give finance a record of each agent payment, from the initial request to the final result.
Explore productDemos with consumer-style spend
Personal Agent
Personal agents
The assistant in your texts, spending only where you allow
ExploreTravel Booking Agent
Travel & events
Delegated booking agents with hard mandate and price-drift controls
ExploreDispatch Agent
Delivery & gig work
Instant driver payouts with policy-controlled tips and surge
ExploreGuest Recovery Agent
Hospitality
Guest-service agents issue make-good credits inside a daily incident budget
Explore