Asks before it acts
Payments, outside email and deletes wait for a person.
Approvals and governance
Agents stop before anything that sends, pays or deletes. You see the exact action and approve it with a deliberate hold. Big money needs a second person.
Book a callPayments, outside email and deletes wait for a person.
Above your threshold, a second owner or admin approves. Never the one who asked.
Requests, approvals and declines land in a log nobody can edit.
1.0Hold to approve
High-risk actions need a press and hold, with the action and amount in front of you. Lower-risk ones take a click.
An agent that needs you says so under its name, and what for, until you answer.
Refund the 37 customers who were charged twice?
stripe.refunds.createPress for 1.2 seconds, or hold Enter. Let go early and nothing runs.
Approve from the keyboard with the same deliberate hold.
The card can show the agent’s screen and the button it will press.
An unanswered request lapses instead of running late.
Declined actions never run, and the agent is told why.
2.0Policy
For each kind of action, choose: run, ask first, ask and hold, or never. Moving money always asks.
Run, ask first, ask and hold, or never, per kind of action.
Tighten or loosen one agent without touching the rest.
Payments and refunds can’t be set to run without asking.
New owners and admins become approvers automatically.
Ledger asks instead of holding; Scout never deletes. Each says what it replaces.
Every owner and admin, or only the people you pick.
An OK is a decision, not a click. You see the action, the amount and the account, then hold to say yes.
3.0Second approver
Payments over your threshold need a second OK. The person who asked can never give it.
Over €500, or whatever you set. Below it, one OK is enough.
Waiting approvals sit at the top of the admin overview.
Always on: you can’t approve what you asked for.
Needs a comment, is marked in the log and sent to approvers.
Select several requests and approve or decline them together.
Approvals, budget requests and app requests in one place.
4.0Standing grants
Let an agent do one safe thing without asking, up to a limit and an end date. Every use is counted.
€100 each, or no amount for actions that don’t move money.
Every grant expires; nothing is granted forever.
Uses are tallied and each one is in the audit log.
One click, and the next use asks again.
A request over a grant’s limit says so, right next to the amount.
Uses count toward the limit and the date. When either runs out, the agent asks again.
5.0Audit log
Requests, approvals, declines and bypasses are separate events. The log is hash-chained and signed hourly, so nobody can change it unnoticed.
Hash-chained and signed hourly. Verify it any time.
Every event names its actor, and who an agent works for.
Filter by category, person and time, then share the view.
CSV or JSON of the filtered view. The export is logged too.
Bring a real task. We’ll show an agent doing it on its own computer, in your apps, and asking before it acts.