Approve and auditevery agent move.
Finance and operations teams set limits, approve held actions with a passkey and export statements that verify offline.
- Category
- Operations
- Built with
- Human control plane, passkeys
- 4owner journeys that advance only on a verified receipt
- 3verification labels on every row, so nothing reads as settled by default
- 9notification classes across push, email and in-app
The problem
When agents move company money, someone has to answer for it. Most teams piece together approvals in chat, spend in spreadsheets and evidence from screenshots, then rebuild the story at month end.
How it works on Paxeer X
The human control plane gives owners one place to create agents, cap them, approve what they hold back and see what settled. Signing keys stay in the service’s key store. The browser never holds signing power.
- Create an agent with a name, a purpose and a monthly limit; it shows as active only when every setup receipt verifies
- Held actions arrive in an approval inbox with amount, counterparty, fee ceiling and budget remaining after
- Sensitive operations need a fresh passkey ceremony bound to that exact operation
- Export a CSV statement, or an evidence bundle with the receipt bytes behind each row
The outcome
The evidence bundle and its hash-chained audit log verify offline, without trusting the service that produced them. An auditor checks the record with a verifier. Nobody rebuilds the month from memory.
“A restriction the app enforces is labelled as such, so an owner is never told that a local rule is a protocol guarantee.”
Build the next one.
The limited beta is open to approved developers. Tell us what you are building and we will get you an allocation.