Controls, observes, and analyzes how AI agents behave when they move money.
Every payment an agent attempts is allowed, held for a person, or refused before it leaves, and there is a receipt either way. Works with any integration, and we add integrations on request. Built on CTRLRun, the open-source kernel.
| Agent | Rail | Payment | Rule | Decision |
|---|
What does your agent do with money?
Pay out
Money leaving your account
When an agent refunds a customer, pays a vendor or changes a subscription, that is your money going out. Every one is checked against your rules before it goes, and a person says yes above the line you set.
Agent wallet
Money your agent spends
When an agent pays for something itself, a USDC transfer on Coinbase or ten cents for one call, it spends only what you set aside, once, and never on a guess.
Pay in
Money arriving
When an agent captures a payment your customer authorised, or another agent pays you, it is recorded from day one. Limits are added once the traffic shows where they belong.
The model guesses.
ctrl payments does not.
No rule for it
The payment is refused. Silence is never permission.
refusedAmount changed after sign-off
The old approval is void. A person signs again.
refusedReply lost
No retry until it is reconciled. Nothing is paid twice on a guess.
pendingTransparent by design
The kernel that decides and refuses is CTRLRun, open source under Apache-2.0. The receipt format and the payment model are published. Run the verification yourself, on your machine, against our product.
Trust is something you verify, not something we ask for.
The finance lead approves exactly $2,000 from the tool they already use.
In the dashboard, in their own assistant, or in Slack. The approval is tied to that payment and that amount. Anything else needs a new yes.